Hi!
In my organization we’re facing a problem where the client sessions are disconnecting with no reason. I’ve tried to increase resources in my VM, update Openfire version and the same error shows up. If someone gets disconnection the status in PSI stays Online and he can receive any message unless that he changes the status to offline and online again.
Here are some info:
OPENFIRE_OPTS="-Xms256m -Xmx3072m"
Openfire 4.3.0
CentOS 7
Error Log:
2019.04.12 12:03:59 WARN [socket_c2s-thread-11]: org.jivesoftware.openfire.nio.ConnectionHandler - Closing connection due to exception in session: (0x000000CE: nio socket, server, /192.168.13.154:57142 => 0.0.0.0/0.0.0.0:5222)
When someone gets disconnected, what it shows for this user in Admin Console? Is it still showing on Sessions page? Is it showing as online on Users page? You should update to 4.3.2, there were a few bugs fixed that could be related and needed to make a change if your issue is what i think (Stream Management related).
In the admin console it shows that the user is Online.
I had the same issue in the 3.9.3 version and the update to 4.3 the issue had gone. There is a note in the patch note of 4.3 that this issue was solved.
You can try adding a system property stream.management.active with a value false. This will disable SM, which tries to keep sessions for disconnected users online, so they don’t have to reconnect (good for mobile users). Then see if that changes anything about your issue.
@wroot, I don’t know why but only OpenFire users complaining about this problem and disabling SM on client side is always a solution.
Is it some problem with SM in OpenFire?
@wroot i know this thread has been closed but since i am facing the same issue posting it here rather then creating new thread.
I am facing the same issue i am using server version 4.4.1 and it showing me online on user page but on session summary there are nothing so what should i do as i am already on the latest version.
I was using openfire - 4.1.3 and every thing was fine but updated after checking lot’s of optimization but stuck here.
Anyway to resolve this issue i have disable the SM but i am not sure is it going to help or not i will check for next couple of days and update again.
I don’t think restart is needed, but you can restart to be sure. As i’ve said, if you still get the issue, this is probably not related to SM and you should post a new thread, maybe provide logs.
I don’t think you have to disable it on the client side if server has it disabled.