Page 1 of 1

SocketAcceptor

PostPosted: Thu Sep 23, 2010 10:17 am
by lesouef
from a given PC on a Lan, I get this error for all windows account except mine.
- security is disabled on servoy server
- my windows account is not domain admin, but lauches the servoy app from any machine on the LAN.
- other accounts: only a java client window opens, but times out saying it can't access network resources.
in the server log:
SocketAcceptor failure for socket: Socket[addr=/192.168.5.67,port=2874,localport=1099]

Re: SocketAcceptor

PostPosted: Thu Sep 23, 2010 1:03 pm
by Harjo
are you talking about connecting a smart client?

I have seen this also, one time, what we did, to completely uninstall java en install java again.
also delete all .servoy folder under every account.

and see what happens.

(btw also check, under java network settings: Direct Connection)

Re: SocketAcceptor

PostPosted: Thu Sep 23, 2010 3:53 pm
by lesouef
indeed... was the network settings. the company I am sweating for has 2 sites, 1 has a proxy, the other one does not. and they are interconnected via a private line, making this a single LAN.
when I connect to a remote PC on site 1(TSE), I keep the settings of a site2 account on a site 1 PC, which makes it work as I work for the proxyless site, and all settings are AD controlled. But all my users are on site1...
thanks mate.

Re: SocketAcceptor

PostPosted: Thu Sep 23, 2010 4:43 pm
by Harjo
wonderful! :-) welcome to the world of java/network connections ;-)

Re: SocketAcceptor

PostPosted: Fri Sep 24, 2010 10:51 am
by jcompagner
in 5.2 you can enable the tunnel in socket&http mode
if you do that then from one app server you should be able to target any client where ever they are.

by default it will connect then in socket mode, but on the admin pages you can make a profile so that some users can force to go over http
and you could even have all kind of different configurations for http per profile..

Re: SocketAcceptor

PostPosted: Fri Sep 24, 2010 1:31 pm
by ngervasi
Johan, how are things working in 4.1? Is it using sockets?
In a 4.1 server I'm having a lot of "Error flushing message buffer to client... java.rmi.ConnectException: Connection refused to host: 192.168.150.114; nested exception is: java.net.ConnectException: no multiplexer found for server..." errors from clients connecting from Citrix, they use direct connection in java settings.

Re: SocketAcceptor

PostPosted: Fri Sep 24, 2010 1:33 pm
by jcompagner
no 4.1.x doesn't have socket support for the tunnel code.

that error just means that the client is gone, and the server can't reach him anymore, that doesn't have to mean that there is a real error
Because i guess if i look at our crm server then we will get many of those errors on the server because i just close my laptop and let it suspend. So then the connection is suddenly broken.
but when i resume the client reconnects, but in the mean time the server could have tried to send me some messages..

Re: SocketAcceptor

PostPosted: Fri Sep 24, 2010 1:45 pm
by ngervasi
jcompagner wrote:that error just means that the client is gone, and the server can't reach him anymore, that doesn't have to mean that there is a real error
Because i guess if i look at our crm server then we will get many of those errors on the server because i just close my laptop and let it suspend. So then the connection is suddenly broken.
but when i resume the client reconnects, but in the mean time the server could have tried to send me some messages..


I know this but I have just too many of them and many times they happen while the users are working, the weird thing is that the Citrix server is sitting next to the servoy server and they are both connected to the same switch. Could it be something related to how Citrix works?
BTW, it would be helpful to log those errors on a separate category because it's becoming very difficult to find important entry logs scattered between them, for now we only have 25 users connecting so I can't imagine when we will have 100.

Re: SocketAcceptor

PostPosted: Fri Sep 24, 2010 2:07 pm
by jcompagner
if there is really not a disconnect at all from the client

Then there has to be something in the middle that terminates the connection.
What does the client gets? constantly a "disconnect" dialog for a few moments? and then it reconnects?

the thing is that most server side errors are not important at all. For disconnects it really it is better to get the client error. Because there something went wrong.
Why does the client disconnect, how does it disconnect, what is there the error.

Re: SocketAcceptor

PostPosted: Fri Sep 24, 2010 3:02 pm
by ngervasi
I will investigate a bit more and ask the users.

Re: SocketAcceptor

PostPosted: Fri Sep 24, 2010 3:27 pm
by lesouef
Johann,
back to the 1st remark to me, I was using socket only (I use http on public liones only). What is the best? fastest if any difference? now with the proxy disabled for java, I can choose.
and do I get any speed advantage if I disable the tunnel mode when having no FW in between client and server? so far I can't see any difference.

Re: SocketAcceptor

PostPosted: Fri Sep 24, 2010 5:51 pm
by jcompagner
socket should be somewhat faster, because that's just plain bytes without tunneling it over another protocol (http)

there shouldn't be much difference between the tunnel with socket mode or the 2 way mode