issue with network settings

Classic Servoy
1

Hi,

I am using the following network settings on my testserver and this works fine.

SocketFactory.useTwoWaySocket: true
SocketFactory.compress: true
SocketFactory.useSSL: false
SocketFactory.rmiServerFactory: com.servoy.j2db.server.rmi.tunnel.ServerTunnelRMISocketFactoryFactory

SocketFactory.tunnelConnectionMode: http&socket

I also have a profile :

Tunnel

system.property.SocketFactory.tunnelConnectionMode=http
system.property.com.sebster.tunnel.http.client.chunked=false
system.property.com.sebster.tunnel.http.client.closeRequestOnFlush=false

When I start the application server on my testserver (cmdbox) there are no errors

When I start the application server on my productionserver (cmdbox) it repeats the following error over and over :

Exception in thread "RMI TCP Connection(idle)" java.lang.IllegalStateException:
invalid command: 12
        at com.sebster.tunnel.impl.ad.run(ad.java:9)
        at java.lang.Thread.run(Unknown Source)

The testserver is a physical server, the production server is a virtual one ( Vmware )

Servoy version is 5.2.2

Any Ideas ??

Regards,

2

From the given information I have no idea what is actually going wrong. If the configurations are the same, it should not make any difference that one server is a VM running on vmware.

The error message suggests that the server is receiving incorrect data (incorrectly encapsulated)

3

One reason this might happen is if the client for some reason talks regular RMI while the server expects tunneled RMI.

A client java console log and the relevant piece of server log could be very useful here.

4

Sebastiaan,

Thanks for your response !!

Regarding your last remark

One reason this might happen is if the client for some reason talks regular RMI while the server expects tunneled RMI.

I do not start a client at all.
When I start the Servoy Server in a cmd/dos box, these errors start immediately in the
cmd/dos box.

Regards,

5

Hi,

It’s kind of strange: it seems something is trying to talk to the Servoy Server and repeatedly connecting to it on the RMI port. You could try do a wireshark dump and see what network traffic is causing this. You could also try running the socket tunnel on a different port, using the rmi start port property, to see if the same thing happens.