Accept error on socket Lightstreamer HTTP Server java.io.IOException: Too many open f

mnenchev

Hi, am got some frustrating exception in the lightstreamer server:
May be this is because too many threads are started?
Please help.

25.Sep.09 19:08:39,550 <ERROR> Accept error on socket Lightstreamer HTTP Server
java.io.IOException: Too many open files
	at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
	at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:163)
	at com.lightstreamer.g.a.eb.i(eb.java)
	at com.lightstreamer.g.a.eb.c(eb.java)
	at com.lightstreamer.g.a.qb.run(qb.java)
25.Sep.09 19:08:39,551 <ERROR> Accept error on socket Lightstreamer HTTP Server
java.io.IOException: Too many open files
	at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
	at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:163)
	at com.lightstreamer.g.a.eb.i(eb.java)
	at com.lightstreamer.g.a.eb.c(eb.java)
	at com.lightstreamer.g.a.qb.run(qb.java)
25.Sep.09 19:08:39,551 <ERROR> Accept error on socket Lightstreamer HTTP Server
java.io.IOException: Too many open files
	at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
	at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:163)
	at com.lightstreamer.g.a.eb.i(eb.java)
	at com.lightstreamer.g.a.eb.c(eb.java)
	at com.lightstreamer.g.a.qb.run(qb.java)
25.Sep.09 19:08:39,551 <ERROR> Accept error on socket Lightstreamer HTTP Server
java.io.IOException: Too many open files
	at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
	at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:163)
	at com.lightstreamer.g.a.eb.i(eb.java)
	at com.lightstreamer.g.a.eb.c(eb.java)
	at com.lightstreamer.g.a.qb.run(qb.java)
25.Sep.09 19:08:39,551 <ERROR> Accept error on socket Lightstreamer HTTP Server
java.io.IOException: Too many open files
	at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
	at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:163)
	at com.lightstreamer.g.a.eb.i(eb.java)
	at com.lightstreamer.g.a.eb.c(eb.java)
	at com.lightstreamer.g.a.qb.run(qb.java)
25.Sep.09 19:08:39,551 <ERROR> Accept error on socket Lightstreamer HTTP Server
java.io.IOException: Too many open files
	at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
	at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:163)
	at com.lightstreamer.g.a.eb.i(eb.java)
	at com.lightstreamer.g.a.eb.c(eb.java)
	at com.lightstreamer.g.a.qb.run(qb.java)
25.Sep.09 19:08:39,551 <ERROR> Accept error on socket Lightstreamer HTTP Server
java.io.IOException: Too many open files
	at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
	at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:163)
	at com.lightstreamer.g.a.eb.i(eb.java)
	at com.lightstreamer.g.a.eb.c(eb.java)
	at com.lightstreamer.g.a.qb.run(qb.java)
25.Sep.09 19:08:39,551 <ERROR> Accept error on socket Lightstreamer HTTP Server
java.io.IOException: Too many open files
	at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
	at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:163)
	at com.lightstreamer.g.a.eb.i(eb.java)
	at com.lightstreamer.g.a.eb.c(eb.java)
	at com.lightstreamer.g.a.qb.run(qb.java)

Regards

Dario Crivelli

No, the message is related to too many sockets (hence streaming clients), not thread.
However, this is not a Lightstreamer limit, but rather a system limit that you can enlarge.
Assuming you are on Linux, use the ulimit command and increase the maximum number of open files (provided that your login user is allowed to do that).

Note that it is possible that the message is issued in a strict loop until a socket is available again.
This is an undesired side effect that will be solved on the next Server release.

mnenchev

Thanks for the response, i will do as suggested. I must note that, i use only one test client( every thing runs on a single machine) and should i get this error in that case?
Regards.

Dario Crivelli

If your client is a load test application that opens multiple streaming sessions at the same time, you can eventually get this error.

On the other hand, if your test client is a normal web page or application that uses a single streaming session, then there is something strange
and we should analyze the Server log to see if so many sessions have really been created.
By the way, which was the limit?