Why are we seeing OutOfMemory exceptions in our log?
Lightstreamer Server keeps the current field state for all active sessions in memory. This allows for reduction of the outbound data flow, as unchanged fields are not sent, but at the expense of some memory. This memory usage grows with: – the number of active sessions – the number of items subscribed to by each session – the number of fields subscribed to for each item – the buffer size (for DISTINCT mode subscriptions) – the number of active keys (for COMMAND mode subscriptions) However, the allocation of field values is not duplicated for all sessions which subscribe to the same item. In some installations it could be necessary to increase the heap size of the JVM used by Lightstreamer Server. The memory setting can be made in LS.sh, where the command line arguments for the Server Virtual Machine are specified. The -Xmx argument sets the maximum memory. Note that the memory allocation described above is not permanent, but it is often not transient as well, hence you should carefully
