Tigase failed with error: Infinite loop detected in write(buff) TLS code

Keren Meir
Added over 5 years ago


I installed Tigase XMPP server on ec2 instance (debian), when i'm trying to register the admin user via psi I got this error:

Infinite loop detected in write(buff) TLS code, tlsWrapper.getStatus(): NEED_READ

I read and didn't understand what solve his problem.

These are the details:

  1. Operating system you use - +Debian+

  2. Hardware you use, CPU, RAM - +Amazon EC2 with m1.large instance+

  3. Have you configured the OS properly for high load system? - +Start the tigase with ulimit -n (configuring it for more open files)+

  4. Do you use any kind of firewalling in the OS kernel? - +Don't know+

  5. Do you experience the problem from the very beginning or it just started suddenly at some point? Can you think of anything you could have changed which could trigger the problem? - +I experience the problem from the first user register. (there are 0 connection on the server)+

  6. What clients do you use? Standalone, web client? - +psi+

  7. What is the traffic on your system? Number of online users, average new user connections per second? Number of packets (presence, messages) going through the system per second? - +0 user connected. nothing else is running on this machine (this is an XMPP dedicated machine)+

  8. What are the memory settings for JVM - +Don't know+

  9. What is the CPU and RAM usage on your installation? - +I don't know if that's what you mean but when the tigase is running: CPU= 0.3 MEMORY=2.3+

  10. Do you experience packet queues grow on your system, are there any packet loss, queues overflow - +no+

  11. Do you use any custom code, plugins, and have checked performance on these plugins? Maybe the cause bottlenecks - +no+

Any idea?

Replies (3)


Added by Artur Hefczyc TigaseTeam over 5 years ago

The most important questions are:

  1. What Tigase server version do you use?

  2. What Java version do you use?

You should use the most recent stable version of the Tigase server or some recent beta from development line. As for Java I recommend the last update of Java6 from Oracle.

I suppose on Debian OpenJdk 7 might be a default one, and we have had some problems with it in the past.

Added by Keren Meir over 5 years ago

I used:

Debian Wheezy (7.1)

Java 7

Tigase 5.1.5

now I change it to:

Debian squeeze (6.0.7)

Java 6

Tigase 5.1.5

and it works!

Thank you.

Added by Andrzej Wójcik IoT 1 CloudTigaseTeam over 5 years ago

If I remember correctly we solved this issue by adding additional configuration paramter to Tigase XMPP Server.

If you would like to still use Java 7, you should add line containing --tls-jdk-nss-bug-workaround-active=true to etc/ file, a workaround for using new TLS/SSL implementation in Java 7 and not fully compatible SSL/TLS libraries on client side would be activated then.