Hi there,
i guess the problem is that the load balancer is just sending a message over the socket connection to the BaseX server, which does not correspond to the BaseX client-server protocol. So the client thread on the BaseX server side is waiting for the credentials in the appropriate form.
The keepalive property does not work in this case, cause there is no "real" BaseX server-client connection to close in this moment. The BaseX server is not able to close the connection to the client cause the client thread on the server side is still in the reading loop for the incoming credentials.
Regards, Andreas
Am 14.05.2012 um 17:35 schrieb Dimitar Popov:
On May 14, 2012, at 3:22 PM, Andreas Rulle wrote:
- The tcpdump - viewed with wireshark - shows that the healthy check of the load balancer - mon and ldirectoryd do the same - sends a RST (Connection reset) message TCP to the BaseX database.
Each RST message from the mon or ldirectord seem to lead to a new socket that remains open ...
Any chance to take a look at that TCP dump?
Regards, Dimitar _______________________________________________ BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk