Occassional LS Server not starting properly

just_opposite

hi,

Occassionally, upon server startup, the log file indicated the DataAdapters were loaded but the server will not log the following messages which eventually leads to an indication that it's listening on the assigned port 8080. Has anyone out there experience the same kind of issue? Any suggestions on what could've gone wrong?

We are using Lightstreamer Moderato 5.1.1

11.Dec.13 12:26:35,565 < INFO> Selector pool size set by default at 4.
11.Dec.13 12:26:35,588 < INFO> Created selector thread: NIO TLS/SSL HANDSHAKE SELECTOR 1.
11.Dec.13 12:26:35,588 < INFO> Created selector thread: NIO TLS/SSL HANDSHAKE SELECTOR 2.
11.Dec.13 12:26:35,589 < INFO> Created selector thread: NIO TLS/SSL HANDSHAKE SELECTOR 3.
11.Dec.13 12:26:35,589 < INFO> Created selector thread: NIO TLS/SSL HANDSHAKE SELECTOR 4.
11.Dec.13 12:26:35,596 < INFO> Created selector thread: NIO TLS/SSL HANDSHAKE SELECTOR 1.
11.Dec.13 12:26:35,597 < INFO> Created selector thread: NIO TLS/SSL HANDSHAKE SELECTOR 2.
11.Dec.13 12:26:35,597 < INFO> Created selector thread: NIO TLS/SSL HANDSHAKE SELECTOR 3.
11.Dec.13 12:26:35,598 < INFO> Created selector thread: NIO TLS/SSL HANDSHAKE SELECTOR 4.
11.Dec.13 12:26:35,608 < INFO> Created selector thread: NIO WRITE SELECTOR 1.
11.Dec.13 12:26:35,609 < INFO> Created selector thread: NIO WRITE SELECTOR 2.
11.Dec.13 12:26:35,609 < INFO> Created selector thread: NIO WRITE SELECTOR 3.
11.Dec.13 12:26:35,610 < INFO> Created selector thread: NIO WRITE SELECTOR 4.
11.Dec.13 12:26:35,617 < INFO> Created selector thread: NIO READ SELECTOR 1.
11.Dec.13 12:26:35,617 < INFO> Created selector thread: NIO READ SELECTOR 2.
11.Dec.13 12:26:35,618 < INFO> Created selector thread: NIO READ SELECTOR 3.
11.Dec.13 12:26:35,618 < INFO> Created selector thread: NIO READ SELECTOR 4.
11.Dec.13 12:26:35,619 < INFO> Created selector thread: NIO CHECK SELECTOR 1.
11.Dec.13 12:26:35,620 < INFO> Created selector thread: NIO CHECK SELECTOR 2.
11.Dec.13 12:26:35,620 < INFO> Created selector thread: NIO CHECK SELECTOR 3.
11.Dec.13 12:26:35,621 < INFO> Created selector thread: NIO CHECK SELECTOR 4.
11.Dec.13 12:26:35,622 < INFO> Created selector thread: NIO WRITE SELECTOR 1.
11.Dec.13 12:26:35,622 < INFO> Created selector thread: NIO WRITE SELECTOR 2.
11.Dec.13 12:26:35,622 < INFO> Created selector thread: NIO WRITE SELECTOR 3.
11.Dec.13 12:26:35,623 < INFO> Created selector thread: NIO WRITE SELECTOR 4.
11.Dec.13 12:26:35,623 < INFO> Created selector thread: NIO READ SELECTOR 1.
11.Dec.13 12:26:35,624 < INFO> Created selector thread: NIO READ SELECTOR 2.
11.Dec.13 12:26:35,624 < INFO> Created selector thread: NIO READ SELECTOR 3.
11.Dec.13 12:26:35,624 < INFO> Created selector thread: NIO READ SELECTOR 4.
11.Dec.13 12:26:35,625 < INFO> Created selector thread: NIO CHECK SELECTOR 1.
11.Dec.13 12:26:35,625 < INFO> Created selector thread: NIO CHECK SELECTOR 2.
11.Dec.13 12:26:35,626 < INFO> Created selector thread: NIO CHECK SELECTOR 3.
11.Dec.13 12:26:35,626 < INFO> Created selector thread: NIO CHECK SELECTOR 4.
11.Dec.13 12:26:35,740 < INFO> Events pool size set by default at 4.
11.Dec.13 12:26:35,757 < INFO> Pump pool size set by default at 4.
11.Dec.13 12:26:35,771 < INFO> Lightstreamer on Java Virtual Machine: Oracle Corporation, Oracle JRockit(R), R28.0.1-21-133393-1.6.0_20-20100512-2126-linux-x86_64, 1.6.0_20-b02 on Linux
11.Dec.13 12:26:35,771 < INFO> Lightstreamer Server 5.1.1 build 1623.2 starting...
11.Dec.13 12:26:35,805 < INFO> Server "Lightstreamer HTTP Server" listening to *:8080 ...

Thanks
Edward

marco.testa

Hi Edward,

When you experience the lack of the log messages, is the server actually running correctly? I mean: the only problem is you don't see the log messages, or the server or one of the adapters is not working properly?
In any case: please, set the log level of the LightstreamerLogger.init to DEBUG and send us [support@lightstreamer.com] the log file.

thanks
Marco

just_opposite

Marco,

Thank you for your reply, we will set the log level of the LightstreamerLogger.init to DEBUG and look for the occurrance.

To clarify my previous post, let me re-describe the problem. The client code has been configured to re-subscribe periodically with new item list which it expects to get realtime updates. We've noticed that on several occassions after Lightstreamer server restarts, the client re-subscription would cease to function. Tracing through the logs we've noticed that the adapter code continues to function without any issue (eg. logging with respect to it's operations), however the client subscription had not occurred since the restart of the server. The log messags that was posted previously represents what we saw in a successful restart, however in the scenario that I've just described above, those log messages were missing. In every instances we do see the following log messages which indicates our adapters are working fine.

< INFO> Finished loading Metadata Adapter ...
< INFO> Finished loading Data Adapter ...

Additionally, without restarting the client, when Lightstreamer server restarts the client subscription would resume. It seems there exists a server issue.

Our current way of resolving this issue is to simply restart the Lightstreamer server.

Thanks
Edward

marco.testa

Hi Edward,

I presume you have more than one adapter, and my suspect is that not all the adapters are actually correctly initialized.
Could be that not for all the adapters the log message "< INFO> Finished loading Data Adapter ADAPTER_NAME" is actually printed?
Anyway, with the LightstreamerLogger.init set to DEBUG we will have a more clear picture about what actually is going wrong during the initialization, and when.
So, as soon as you have reproduced the issue, please send us the log file and we will look at it.

regards,
Marco