Scheduler with events on local channel does not work.
Article ID: KB0092792
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
Description:
Symptoms:
Cause:
Any member with scheduler enabled can become a scheduler in the cluster, so the Cache Server might become the cluster scheduler. The Cache Server does not have local destination enabled and it does not have any rule engine working threads work for the destination. When the Cache Server becomes scheduler of the cluster, it will schedule the event and sends events to a local destination which will not be sent to any other inference engines.
One cache engine and two inference engines sharing the same EAR/CDD. A scheduler is defined and has an event scheduled with this scheduler. The event has local destination as default destination.
Symptoms:
Application started, Scheduler is created and event is scheduled but no rules are triggered by the scheduled event.
Cause:
Any member with scheduler enabled can become a scheduler in the cluster, so the Cache Server might become the cluster scheduler. The Cache Server does not have local destination enabled and it does not have any rule engine working threads work for the destination. When the Cache Server becomes scheduler of the cluster, it will schedule the event and sends events to a local destination which will not be sent to any other inference engines.
Issue/Introduction
Scheduler with events on local channel does not work.
Resolution
1). To make sure Cache Server does not become the scheduler in the cluster, disable the scheduler from the cache node. To disable, set the following property on the cache agent class to false:
be.engine.cluster.scheduler=false
2). You could also change the default destination of the schedule event from a local destination to some other types of destination, e.g. JMS destination and have the cache agent act as a cluster scheduler.Feedback
Yes
No
Powered by
