-
September 21st, 2009, 10:30 AM
#1
Hi Alessandro,
I believe we using Option 1.A.1 - all requests go through the load balancer IP address, as both Lightstreamers cannot be reached via public IP. The load balancer routes the requests to the Lightstreamer boxes.
The application which updates data to both Lightstreamers connect directly to each Lightstreamer box (as the application and both Lightstreamers are internal).
The version of Lightstreamer we are using is Lightstreamer we are using is 3.5 build 1428.4 (Allegro).
Thanks,
CT
-
September 21st, 2009, 11:06 AM
#2
Hi Claire,
Thanks for your clarifications.
So this seems to be a very simple clustering scenario, where the request dispatching is fully delegated to the load balancer. Is it possible that the balancer fails to guarantee stickiness based on IP address (perhaps the client IP addresses are changeable)?
We could understand this by comparing the logs for both the servers, to see if a session originated in one server is wrongly bound to the other server on subsequent requests.
Please contact support@lightstreamer.com.
Cheers,
Alessandro
Similar Threads
-
By riwang in forum Client SDKs
Replies: 9
Last Post: August 16th, 2017, 08:39 AM
-
By Mone in forum Client SDKs
Replies: 0
Last Post: February 21st, 2011, 04:16 PM
-
By igindex in forum Client SDKs
Replies: 6
Last Post: March 5th, 2008, 05:06 PM
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 10:13 AM.
Bookmarks