Update…
Here is some text from our error logs…
This is from the Debug logs… Notice the items in Bold[/b] If there is a better way to post code, please let me know…
2006.01.03 07:54:52 Connect Socket[addr=/163.252.29.48,port=4329,localport=5222]
2006.01.03 07:54:52 Logging off richardsong@link.sra.com/jwchat on org.jivesoftware.wildfire.net.SocketConnection@1c9e8e8 socket: Socket[addr=/163.252.29.48,port=4327,localport=5222] session: org.jivesoftware.wildfire.ClientSession@12961e6 status: -1 address: richardsong@link.sra.com/jwchat id: 5f0d06b6 presence:
2006.01.03 07:59:45 Trying to find a user’'s DN based on their username. sAMAccountName: Richardsong, Base DN: DC=gm,DC=sra,DC=com…
2006.01.03 07:59:45 Creating a DirContext in LdapManager.getContext()…
2006.01.03 07:59:45 Created hashtable with context values, attempting to create context…
2006.01.03 07:59:45 … context created successfully, returning.
2006.01.03 07:59:45 Starting LDAP search…
2006.01.03 07:59:45 … search finished
2006.01.03 07:59:45 In LdapManager.checkAuthentication(userDN, password), userDN is: CN=Richardson, Gary,OU=Galaxy,OU=SRA…
2006.01.03 07:59:45 Created context values, attempting to create context…
2006.01.03 07:59:45 … context created successfully, returning.
2006.01.03 08:01:57 Connect Socket[addr=/163.252.29.48,port=4353,localport=5222]
2006.01.03 08:01:58 Logging off richardsong@link.sra.com/jwchat on org.jivesoftware.wildfire.net.SocketConnection@40e46d socket: Socket[addr=/163.252.29.48,port=4338,localport=5222] session: org.jivesoftware.wildfire.ClientSession@171e404 status: -1 address: richardsong@link.sra.com/jwchat id: 128da157 presence:
[/b]
It appears to be logging him off, but he doesn’'t actually get logged out, he just gets set to unavailable. Once he changes his status back to Online, we can see him again…
Message was edited by:
jase700