powered by Jive Software

S2S settings

Jive version 2.2.2. The problem is that s2s settings are “never close iddle connection” but server still close connections. S2S works, but when connection to server is close I had to wait about 30 sec. to receive message from account on my server to an account on another one ( I have account on one of public servers in Poland). After connections is made works in a blink of an eye.

In log I have info :

2005.11.22 15:47:41 org.jivesoftware.messenger.net.SocketReader.run(SocketReader.java:145) Connection closed before session established

Socket[addr=/62.87.130.210,port=15290,localport=5269]]

And when SSL is enabled:

2005.11.22 15:47:41 org.jivesoftware.messenger.net.SocketReader.run(SocketReader.java:145) Connection closed before session established

1ad093c[SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA: Socket[addr=/62.87.130.210,port=15290,localport=5223]]

Hey samson,

Remote servers can also close their connections to your server so even though you set “never close iddle connection” s2s connections can be closed by remote servers. BTW, the first log that you posted might be generated when the remote server did a dialback to your server to authenticate a connection. It is safe to ignore those entries in the logs. In a future version we might even not log them at all.

Regards,

– Gato