-
September 11th, 2007, 03:39 PM
#1
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.
-
September 11th, 2007, 05:28 PM
#2
This brings us back to this thread.
-
September 12th, 2007, 09:51 AM
#3
Originally Posted by
DarioCrivelli
Yes, I know it does.
My point was that the documentation I've seen, and messages in that thread, suggest that having an Adapter Proxy throw an error due to the Remote Adapter terminating would only cause the Lightstreamer server to also terminate if this was the only adapter running. The implication was that if there was more than one Adapter Proxy running then if just one of them went away then the rest would carry on running and so the Lightstreamer server would not shutdown. Have I interpreted the documentation incorrectly?
-
September 12th, 2007, 10:11 AM
#4
That was probably a misunderstanding. I confirm that the current implementation of the Proxy Adapter terminates the Server process upon Remote Adapter disconnection, irrespective of other Adapters still running.
This behavior will be probably changed in a future release of Lightstreamer (expected within a couple of months), where support for multiple Adapters accessed from the same session wil be added too.
-
September 12th, 2007, 10:55 AM
#5
Tony, sorry for the misunderstanding.
We found a sentence in that thread that could be interpreted as you did:
Note that, while on the Remote Adapter side there may be custom code to be preserved from a process close (as in your case), on the Server side, where the Proxy Adapter is running, this is not the case, unless other adapters are running.
I will fix it in that thread.
Could you find a similar ambiguity in our documentation too?
-
September 12th, 2007, 02:46 PM
#6
Originally Posted by
DarioCrivelli
Tony, sorry for the misunderstanding.
I will fix it in that thread.
Could you find a similar ambiguity in our documentation too?
I think so, however I've being reading so much documentation over the past few days that I'm not sure where it was I'll try to remember to append a message to this thread when I come across.
Slow response because I've now moved on to prototyping a simple web client.
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:46 PM.
Bookmarks