powered by Jive Software

Disconnect Inquiry related to LDAP and debug.log

I’'m noticing the following behavior once every hour for each user having an active session to our Messenger server.

SNIPIT begin-------

2005.06.06 11:02:05 SSL Connect dc3b82[SSL_NULL_WITH_NULL_NULL: Socket[addr=/,port=3790,localport=5223]]

2005.06.06 11:02:05 Trying to find a user’'s DN based on their username. uid: joeuser, Base DN: o=clinic,c=us…

2005.06.06 11:02:05 Creating a DirContext in LdapManager.getContext()…

2005.06.06 11:02:05 Created hashtable with context values, attempting to create context…

2005.06.06 11:02:05 Logging off joeuser@im.a.loser.com/Pandion on org.jivesoftware.messenger.net.SocketConnection@c7057c

2005.06.06 11:02:05 … context created successfully, returning.

2005.06.06 11:02:05 Starting LDAP search…

2005.06.06 11:02:05 … search finished

SNIPIT end----

What is going on here? Is it a connection refresh of some sort? It may only occur when the user is in an idle state, but we haven’'t been using it much so users are almost always in an idle state.

I have have a secure stunnel port mapped to 5222 so we have the option of using GAIM which works great, but it also is happening to clients connecting through port 5223.

The server is working great. I just wondered if this is normal behavior.

This is having an effect on certain clients.

iChat will disconnect and not reconnect successfully a lot of the time. Pandion seems to reconnect fine unless I set the Conflict Policy to Never kick. Then it acts up and won’‘t even let me log in at times even though there isn’'t a resource conflict.

Anyone else seeing anything like this?

This is also a concern because it appears with a lot of users connected, this would create a lot of network traffic.

Also, an update…

I have updated to version 2.1.5 successfully and the hourly reconnects are still occuring.

Has this question already been answered/asked before?

Message was edited by:


Think I’‘ve answered my own question. Seems that we have some rule on our firewall to so a connection refresh for all TCP/IP sessions. It’‘s set to refresh any connection if it has been connected for an hour. Doesn’'t appear to be any relation to Jive Messenger at all.