Could you please check if your application always closes the active client sessions, i.e.
the method org.basex.server.Session.close() is called?

Regards,
Dimitar

On May 11, 2012, at 10:59 AM, Andreas Rulle wrote:

Hello BaseX-Experts!

Let me first thank you who drive this fantastic BaseX project!

For the use of BaseX as a backend to a soap-webservice project we have seen
very encouraging load test results.

On the systems that is intended to become productive very soon we see on a daily basis
(on two database engines behind a load balancer) the following messages that terminate
the execution of the Basex-server.

Improper use? Potential bug? Your feedback is welcome:
Contact: basex-talk@mailman.uni-konstanz.de Version:
BaseX 7.2 Java: Sun  Microsystems Inc., 1.6.0_20 OS: Linux, amd64
Stack Trace: java.net.SocketException: Too many open files
java.net.PlainSocketImpl.socketAccept(Native Method) java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:375)
java.net.ServerSocket.implAccept(ServerSocket.java:470)
java.net.ServerSocket.accept(ServerSocket.java:438)
org.basex.BaseXServer.run(BaseXServer.java:164)
java.lang.Thread.run(Thread.java:636)

The error message occurs when there are no client requests to the server.
The load balancer might do some pinging.

Any feedback and hint to this message is highly welcome!

With best regards,

Andreas

--
Nexoma GmbH
Theodorus Weg 7
59755 Arnsberg

Geschäftsführer: Guido Sauerland
Sitz der Gesellschaft: Arnsberg
Registergericht: Arnsberg, HRB 9365

_______________________________________________
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk