What do the RtcOps codes in TIBCO BusinessEvents (BE) log mean when turning on the engine debug trace?
Article ID: KB0092380
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
Resolution:
When BE engine debug trace role is enabled, you can see something like the following in the engine log file:
RTC Operations: [Object=be.gen.Framework.Events.COMRootEvent@id=6, RtcOps=101]
The RpcOps codes are for BE internal use of tracking object status in current rule evaluation cycle (RTC). Here are some commonly used RpcOps codes for event objects and/or concept/stateMachine/state instances:
RpcOps=1: asserted in the current RTC.
RpcOps=11: asserted and modified in the current RTC.
RpcOps=101: asserted and deleted in the same RTC.
RpcOps=100000: event is scheduled. Currently it’s not used for concept.
When BE engine debug trace role is enabled, you can see something like the following in the engine log file:
RTC Operations: [Object=be.gen.Framework.Events.COMRootEvent@id=6, RtcOps=101]
The RpcOps codes are for BE internal use of tracking object status in current rule evaluation cycle (RTC). Here are some commonly used RpcOps codes for event objects and/or concept/stateMachine/state instances:
RpcOps=1: asserted in the current RTC.
RpcOps=11: asserted and modified in the current RTC.
RpcOps=101: asserted and deleted in the same RTC.
RpcOps=100000: event is scheduled. Currently it’s not used for concept.
Issue/Introduction
What do the RtcOps codes in TIBCO BusinessEvents (BE) log mean when turning on the engine debug trace?
Feedback
Yes
No
Powered by
