dwd has a new pull request with a patch that has worked well for me so far. Hopefully we can get this merged soon and have folks try again.
For those of you up for another round of testing, new builds are available with dwd’s recent pull request included. Please let us know how it goes!
Linux RPM
http://bamboo.igniterealtime.org/artifact/OPENFIRE-RB3/JOB1/build-8/Project-RPM- installer-files/openfire-3.10.1.rc-1.i38…
Solaris
http://bamboo.igniterealtime.org/artifact/OPENFIRE-SB3/JOB1/build-5/Project-Sola ris-distribution-files/JSopenfire-3.10.1…
Mac
http://bamboo.igniterealtime.org/browse/OPENFIRE-MB3-4/artifact/JOB1/Project-Mac -distribution-files/openfire.dmg
Debian
http://bamboo.igniterealtime.org/artifact/OPENFIRE-DB3/shared/build-4/Project-De bian-distribution-files/openfire_3.10.1_…
Windows
http://bamboo.igniterealtime.org/artifact/OPENFIRE-WB3/shared/build-5/Project-Wi ndows-distribution-files/openfire_3_10_1…
Generic ZIP
http://bamboo.igniterealtime.org/artifact/OPENFIRE-WB3/shared/build-5/Project-Wi ndows-distribution-files/openfire_3_10_1…
Don’t know about the CPU usage, but i still have login lockup issue with this build.
Still having issues.
2015.06.09 16:41:30 org.jivesoftware.openfire.nio.NIOConnection - Failed to deliver packet: all
2015.06.09 16:41:30 org.jivesoftware.openfire.session.LocalSession - Internal server error
java.lang.IllegalStateException: Connection closed
For those of you still holding out hope, perhaps a new discovery was just made
[OF-916] Deadlock with MINA sslFilter - Jive Software Open Source
dwd created a one line patch and hope springs eternal again! Hopefully we have new builds for folks soon or if you can please test out the patch, please do so!
Hi Daryl.
Do you think this fix will address the issues I am seeing with the
“org.jivesoftware.openfire.nio.NIOConnection - Failed to deliver packet” error?
Or is this not related at all.
thanks,
Geoff
Current indications are yes!
I sure hope it will be finally fixed and i won’t have to dive into this huge thread again…
OK, as soon as there is a new build I will deploy it.
thank you!!
Okay folks, hopefully this is the last iteration! Please test out these builds and report back results!
Linux RPM
http://bamboo.igniterealtime.org/artifact/OPENFIRE-RB3/JOB1/build-9/Project-RPM- installer-files/openfire-3.10.1.rc-1.i38…
Solaris
http://bamboo.igniterealtime.org/artifact/OPENFIRE-SB3/JOB1/build-6/Project-Sola ris-distribution-files/JSopenfire-3.10.1…
Mac
http://bamboo.igniterealtime.org/browse/OPENFIRE-MB3-5/artifact/JOB1/Project-Mac -distribution-files/openfire.dmg
Debian
http://bamboo.igniterealtime.org/artifact/OPENFIRE-DB3/shared/build-5/Project-De bian-distribution-files/openfire_3.10.1_…
Windows
http://bamboo.igniterealtime.org/artifact/OPENFIRE-WB3/shared/build-6/Project-Wi ndows-distribution-files/openfire_3_10_1…
Generic ZIP
http://bamboo.igniterealtime.org/artifact/OPENFIRE-WB3/shared/build-6/Project-Wi ndows-distribution-files/openfire_3_10_1…
Anyone successfully deploy the latest version?
Since I upgraded, no one can logon to the server.
Yes I’ve been testing it most of the afternoon and no longer have these issues. Everything seems to be working well now.
Geoff,
What is your authentication backend? From what version did you upgrade? Which client(s) are your users using? Does openfire log authentication failures?
Something seems to have happened to the SSL configuration across upgrades. I am using self-signed certificates. Once I deleted the certs and made TLS optional, the clients were able to connect properly over an unencrypted connection.
I will work on getting this sorted out.
thanks for asking!!
Geoff
I have no login issues with this build anymore.
Weird, since I upgraded the server I am getting these errors now:
2015.06.10 22:42:36 org.jivesoftware.openfire.net.SocketReader - Closing session due to incorrect hostname in stream header. Host: domain.local. Connection: org.jivesoftware.openfire.net.SocketConnection@61dc766e socket: Socket[addr=/192.168.1.1,port=49592,localport=5269] session: null
2015.06.10 22:42:36 org.jivesoftware.openfire.session.LocalOutgoingServerSession - Fail to connect to domain.local for app2.domain.local
2015.06.10 22:42:36 org.jivesoftware.openfire.net.SocketReader - Closing session due to incorrect hostname in stream header. Host: domain.local. Connection: org.jivesoftware.openfire.net.SocketConnection@4475862f socket: Socket[addr=/192.168.1.1,port=49593,localport=5269] session: null
The sanitized server name is: app2.domain.local
It is weird, that some users are still able to logon, but others are not.
Any ideas on this?
Whatever this is, it’s not a 100% CPU issue - could you open another thread.
Good news (I think!) I’m not seeing the spinning process with the latest RC-1 RPMs and I was able to log into the admin console using my LDAP username and password.
I’ll keep a close eye on it and let you know if I see the spinning manifest itself
Darn spoke too soon, checked it this morning and there’s a 100% CPU spinning process:
31696 daemon
20 0 18.7g 5.8g 13m R 100.4 18.6 996:54.88 java
31607 daemon
20 0 18.7g 5.8g 13m S 0.3 18.6 0:32.58 java
31663 daemon
20 0 18.7g 5.8g 13m S 0.3 18.6 0:10.39 java
1 root
20 0 19356 1552 1252 S 0.0 0.0 0:00.60 init
Thread dump via kill -3 attached with Garbage Collection stuff stripped out
Installed the fixed DEB yesterday morning, everything is running smoothe since then.