If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Adapter ports not up

Hi guys,

We are having a weird issue with adapter ports on our Lightstreamer server.

Basically we have setup a data adapter running on "request_reply_port" 9000 & "notify_port" 9001. When we first start up the server, we could see the ports being open. But after our client side code (j2ee) making a connection request, the server would stop listening to those ports.
This suddenly started happening today. And we could find no error message in lightstreamer logs.

Could it be that if more than one connection attempts are being made to the server at one time, it brings down the ports?
We might have more than one threads trying to connect to those ports at the same.

Sorry about the massive log file. Please see the attached a much smaller version.

I had another look in the log. I found some interesting error message right after the server restarted. This is also when another server responsible for updating data started making multiple connection attempts to LS server. And I started seeing this error message popping up.

A
are you on windows or linux? The last time I've seen a "Accept error on socket Lightstreamer HTTP Server" error was on a linux machine: an ineffective ulimit call led to the exhaustion of the number of open files (sockets are considered as open files on the system configurations). What is strange is that the exception associated with the error is not logged as I would expect. (you can check the limits on a linux machine calling ulimit -a ). Also windows probably has a limit somewhere (register?).

B

Could it be that if more than one connection attempts are being made to the server at one time, it brings down the ports?

I'm not sure about this. The proxy data adapter expects one connection (per port) only for sure, but I don't think it will close everything down if a second request arrives. Unfortunately the guy who wrote the remote adapter is out of office until the the 9th of august. I may check the sources for confirmation in case A does not explain the issue.
Btw did you implemet the ARI protocol or did you use our .NET remote adapters?

On point B, I confirm that the Proxy Adapter on the Server opens each of the configured ports to accept a single connection, then it stops accepting connections on the port.
Multiple remote counterparts talking to the same Proxy Adapter are not supported.
In case of a Robust Proxy Adapter, when a recovery is needed, the ports are reopened.