BusinessEvents engine continues picking messages from the EMS server after the Cache Server node is shutdown.
Article ID: KB0086552
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
Resolution:
Description:
===========
BusinessEvents engine continues picking messages from the EMS server after the Cache Server node is shutdown.
Environment:
===========
TIBCO BusinessEvents 5.x
All Operating Systems
Cause:
======
The first message will be picked but not acked, so all messages will continue to be in the EMS server when the quorum comes to be not met. Note the AckMode is EXPLICIT_CLIENT_ACKNOWLEDGE(TIBCO Proprietary).
Resolution:
========
This is expected behavior in BusinessEvents5.x. There are some differences in behavior between BusinessEvents5.x and BusinessEvents4.x.
In BusinessEvent5.x, if quorum is not met, the inference agent will still pick the first message but does not process it. Instead it will throw a AS_OPERATION_TIMEOUT exception. The message still resides in the EMS server until the quorum is reached and the message will then be processed in the correct manner.
In BusinessEvents4.x which is using coherence not Activespaces, if quorum is not met, it will not throw AS_OPERATION_TIMEOUT exception or any other exceptions.
Description:
===========
BusinessEvents engine continues picking messages from the EMS server after the Cache Server node is shutdown.
Environment:
===========
TIBCO BusinessEvents 5.x
All Operating Systems
Cause:
======
The first message will be picked but not acked, so all messages will continue to be in the EMS server when the quorum comes to be not met. Note the AckMode is EXPLICIT_CLIENT_ACKNOWLEDGE(TIBCO Proprietary).
Resolution:
========
This is expected behavior in BusinessEvents5.x. There are some differences in behavior between BusinessEvents5.x and BusinessEvents4.x.
In BusinessEvent5.x, if quorum is not met, the inference agent will still pick the first message but does not process it. Instead it will throw a AS_OPERATION_TIMEOUT exception. The message still resides in the EMS server until the quorum is reached and the message will then be processed in the correct manner.
In BusinessEvents4.x which is using coherence not Activespaces, if quorum is not met, it will not throw AS_OPERATION_TIMEOUT exception or any other exceptions.
Issue/Introduction
BusinessEvents engine continues picking messages from the EMS server after the Cache Server node is shutdown.
Feedback
Yes
No
Powered by
