craigtype3
I have written a .Net adaptor on my Windows PC, and I'm running it in a linux environment (Ubuntu Intrepid Ibex) using Mono. The adaptor is very simple, it queries a database and sends a message out to Lightstreamer.
In Windows if I start the adaptor and Lightstreamer the two are able to talk to each other and message sending seems to work fine. However under Linux Lightstreamer will crash apparently after establishing a connection with the adaptor. The adaptor seems to be working just fine.
Any suggestions would be appreciated.
Thanks,
Craig
The stack trace is as follows:
02.Jul.09 11:29:56,603 < INFO> Lightstreamer Server 3.5 build 1428.4 starting...
02.Jul.09 11:29:56,631 < INFO> Server "Lightstreamer HTTP Server" listening to *:8080 ...
02.Jul.09 11:29:58,510 <FATAL> I/O Exception caught while reading/writing from/to streams: null, aborting...
java.io.EOFException
at com.lightstreamer.adapters.remote.request_reply.NotifyReceiver.run(NotifyReceiver.java:80)
02.Jul.09 11:29:58,606 <FATAL> I/O Exception caught while reading/writing from/to streams: null, aborting...
java.io.EOFException
at com.lightstreamer.adapters.remote.request_reply.NotifyReceiver.run(NotifyReceiver.java:80)
02.Jul.09 11:29:58,607 <FATAL> I/O Exception caught while reading/writing from/to streams: null, aborting...
java.io.EOFException
at com.lightstreamer.adapters.remote.request_reply.NotifyReceiver.run(NotifyReceiver.java:80)
02.Jul.09 11:29:58,608 <ERROR> Failure invoked by Data Adapter
java.io.EOFException
at com.lightstreamer.adapters.remote.request_reply.NotifyReceiver.run(NotifyReceiver.java:80)
02.Jul.09 11:29:58,609 <FATAL> Failure in a Data Adapter
02.Jul.09 11:29:58,609 < INFO> Exiting.....
02.Jul.09 11:29:58,610 <ERROR> Failure invoked by Data Adapter
java.io.EOFException
at com.lightstreamer.adapters.remote.request_reply.NotifyReceiver.run(NotifyReceiver.java:80)
02.Jul.09 11:29:58,610 <FATAL> Failure in a Data Adapter
02.Jul.09 11:29:58,610 < INFO> Exiting.....
Dario Crivelli
The log from Lightstreamer Server indicates that the Remote Server process (which runs the Remote Adapter) closes first.
Can you see the Remote Server process still alive after the Server crash? This would be strange as well; at least, the Remote Server should notice the connection break.
