Hi Mone,

We are currently testing with less load at the moment and are incrementally adding more on the live sites until we find the issue.

The ulimit values that were set are:
Code:
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 155648
max locked memory       (kbytes, -l) 32
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 10240
cpu time               (seconds, -t) unlimited
max user processes              (-u) 155648
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited
Do you see any problem with any of the other values (besides open files?).

In regards to clustering, the setup is as follows

Lightstreamer load balancer: port 80
Lightstreamer 1: port 8080
Lightstreamer 2: port 8080
Application (that updates both Lightstreamers data): connects directly to both Lightstreamers on port 8080, not through the load balancer.

The reason why the Lightstreamers are running on port 8080 was enforced by the operations team for security reasons. Should this have an effect on the error that we have seen?

Thanks!

CT