Problems with Jabber

SunSunich wrote:

We have the same problem. Three people successfully logged in to
jabber service (openfire 3.4.3), after that they tried to send test
messages to each over. Two of us chat successfully, while third
couldn`t see anything, even when he disconnected and connected again.
After that we found that the first two developers who successfully
connect to each over first time, was unable to receive messages now.
Something strange happens, i`m trying to update openfire server.

Regarding this I created bug:
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/58841


Feel free to comment on this bug so we can get more ways to reproduce
this behavior.

--
Cheers, Johannes
Agile Planning Team

SunSunich wrote:

We have the same problem. Three people successfully logged in to
jabber service (openfire 3.4.3), after that they tried to send test
messages to each over. Two of us chat successfully, while third
couldn`t see anything, even when he disconnected and connected again.
After that we found that the first two developers who successfully
connect to each over first time, was unable to receive messages now.
Something strange happens, i`m trying to update openfire server.

Everyone.

As mentioned before, we are on it
(https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/58841).
So long, you should be able to work around this by setting a resource in
the Jabber preferences (Window > Preferences > Instant Message. Select a
Jabber account, select 'Edit', and enter a resource).



--
Cheers, Johannes
Agile Planning Team

i had the same problem.

My solution: copy username to resource and ensure that the same username exists in the jabber server

We are experiencing a scenario where a user could be logged into RTC using OpenFire for IM.. not close RTC but just Lock his PC.. return the next morning and experience similar issues. The user closes RTC and relaunches RTC on his workstation and sees everyone on the team as online but cannot chat with others. We performed a netstat on his PC and found many TCP - IM PORTS opened in connection to other team members PCs but the status was set to CLOSE_WAIT.. We would see multiple or Duplicate TCP - IM PORTS open to the same machine. When we rebooted his PC. We launched RTC , performed a netstat and found that the DUPLICATE TCP - IM PORTS had disappeared. IM then worked.