ISM stops sending events to ObjectServer

The issue that is occurs when the Bridge cannot cope with the number of events being sent through from the monitors. This behavior is most likely seen when there are too many events for the bridge to handle. The properties below allow buffering to be used to gather certain volume of events and then forward them to the ObjectServer, making this a more controlled process.

The QSize property is defined in the $OMNIHOME/monitors/solaris2/bridge.props.
The value below is 100Mb but we would recommend anywhere from 30Mb through to 100Mb. It is best to implement the lower value and then note how this performs, the reasons the range is high depends on how many alarms/how much data is being processed and as it can be appreciated this can vary from customer to customer.

QSize=102400000 (That is around 100 Mb).

This queue size data is also written to $OMNIHOME/var/sm_bridge.var as per in the props file.

Also Buffering and Buffering size should be set in
$OMNIHOME/monitors/solaris2/objectserver.props:

Buffering=1
BufferSize=100

The value of 1 enables the buffering functionality and the BufferSize dictates the number of events buffer which are stored in one go before being processed on to the ObjectServer. Again the value is detailed above as 100 but if you find that a higher value is required due to the amount of data then you can tweak this value up to 500.