-
September 11th, 2007, 03:39 PM
#6
Originally Posted by
DarioCrivelli
Tony,
If you follow this process, do you still encounter any problem?
Dario
OK, I've changed the very naive "proof of concept" test apps I was using to be better behaved and I get much better results now. SO: I start my Lightstreamer server with two Adapter Proxies configured and I see it listening on the port for the first of them. Now I start the app which is the Remote Server for this adapter and I see the data and metadata send/receive/notify processes start up AND I see from netstat that there is now a listening socket for the second adapter. Start the Remote Server app for this one and its data and metadata send/receive/notify processes start up too. Also the HTTP server process now starts listening on port 8080. I can now start up apps which connect as clients which subscribe to theses two adapters and this also works.
Only problem I now have is that if I close down one of my Remote Server apps then the associated Adapter Proxy also fails, due to stream i/o error. I was expecting this. However, the failure in this adapter also causes the whole Lightstreamer server to stop. From what I had read I was expecting the Lightstreamer to continue running because it still has an Adapter Proxy correctly connected to a Remote Server which is active.
Similar Threads
-
By odeheurles in forum Adapter SDKs
Replies: 6
Last Post: January 26th, 2015, 09:50 AM
-
By sjohn in forum Client SDKs
Replies: 11
Last Post: January 23rd, 2015, 11:22 AM
-
By Pradeep Chahal in forum Adapter SDKs
Replies: 1
Last Post: April 26th, 2010, 02:50 PM
-
By rd2008 in forum Client SDKs
Replies: 2
Last Post: January 7th, 2009, 02:28 PM
-
By Waddy in forum General
Replies: 2
Last Post: March 16th, 2007, 06:06 AM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 08:15 PM.
Bookmarks