I’'ve installed jive and configured to authenticate using AD(LDAP). It worked for 2 days but now when I try to log using Padion it stays trying to connect without any response.
This error occur only for some users, other still can connect correctly.
When I go to web administration tool the user that stays trying to connect appears online.
I’‘ve tryed to install Exodus to test if the error was a bug in Pandion but in Exodus the problematic users don’'t connect to.
When using Exodus, could you press F12 to open the debugger window and tell us which are the received and sent XML packets? Are other users still able to log in? Which operating system are you using? I may ask you to obtain a thread dump of the server. Let us know if you need help getting that information.
When I digit the wrong password in pandion the Jive responds that the password is invalid.
But with the right password it st waiting a response.
I’‘ve use ethereal to see the packets and i’'ve seen many packets with TCP checksum incorrect.
I think it is not network because every other application is working well. I use the ssh to administer the server where jive is installed and it funcitons well.
In order to get a thread dump you will need to execute a kill -3 . Could you send me your dump by email so I can check it. Remember to generate the thread dump when clients cannot connect to the server. The dump should be generated in the nohup file or in the stdout file.
Could you try using url=http://www.jivesoftware.org/builds/messenger/dailybuilds/jive_messenger_2005 -05-22.tar.gzthis nightly build[/url]? I assume that you are using JM 2.1.3 and many problems have been fixed since that version.
nohup.out can be in jive_messenger installation directory or in jive_messenger/bin… cant remember, that’‘s if you areusing it with root, and in /home/jive if launching it with jive user. My linux server is at work so i cant guarantee i’'m 100% right, but you cant figure it out by yourself;)
But, if you are using 2.1.3 please do upgrade before going further, i had such strange disconnections with 2.1.3 too. Now with 2.1.4 n.build this problem seems to dissapear.
I see 3 thread dumps in the file that you sent me. The first dump shows that there were 3 connected users with no problems. The second dump shows 4 connected users with no problems and a 5th user waiting for LDAP to answer. The last dump shows only 1 connected user (with no problems).
So I assume that the problem was captured with the second thread dump. Since a thread dump is just a snapshot of the JVM in a moment I’'m not sure how the “waiting for LDAP to answer” situation evolved. It would be great if you can take two snapshots (i.e. thread dumps) with a couple of minutes between them when a user is waiting forever so we can see how the situation evolved. If nothing has changed (i.e. Jive Messenger keeps waiting for LDAP to answer) then we will have to check the status of the TCP connection between Messenger and the LDAP server. If the connection seems ok then you will have to check the LDAP server status to figure out why nothing is being returned.
Anyway, I will check if we can specify a read timeout so if nothing is received from the LDAP server then a SocketException will be thrown.
When Pandion waits for a response and I enter the Web Administration Tool in the sessions page I see the client as online. So, the authentication is ok.
But Pandion receives no response.
I think that the wait state you see in the second dump was because this dump i’'ve created just after clicking in the reconnect button of Pandion.
According to the Pandion traffic I see that Pandion sent a packet to the server asking for the user roster and the server never replied (see id=“sd10”). Could you check all the log files. Maybe we could find that a packet was dropped or some other error.