When trying to send a scheduled event, getting exception saying destination URL is not valid but local destination is valid.
Article ID: KB0087616
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
Resolution:
Abstract:
==========
Error when using local channel destination to schedule EVENT.
Description:
============
You might use the event scheduler functions instead of a time event in the following cases:
If you need to send any event on a schedule, you must use the scheduler. If you schedule a memory-only simple event, the schedule is persisted. If you schedule a memory only time event (using the time event's function, not the scheduler functions) then the schedule is not persisted.
If you need to create many, perhaps thousands of schedules at one time, performance may be better using the event scheduler functions.
Because schedule management and event sending can be handled by a cache server, fewer resources in the inference agents are required compared to time events. Additionally, with backing store enabled the schedules are only loaded into memory a batch at a time which reduces the total memory requirement compared to time events.
The common practice is to use simple events configured to use an EMS destination to schedule EVENTs. The solution to use EMS destination enables multiple schedulers in the cluster thus making it a scalable solution. But, there could be customer scenarios where they would like only one agent in their cluster scheduling an EVENT and do not want to send a message outside the engine just to schedule an EVENT. They are reluctant to code a process to schedule an event and to only send the event to the one processing unit.
When you use a local destination to schedule an EVENT and do not designate a specific agent as a scheduler, then you will run into issues.
Environment:
===========
All Operating Systems supported for TIBCO Business Events.
Symptoms:
========
EVENT is not scheduled as expected.
Cause:
=====
Not marking a specific agent as designated scheduler and marking all other agents as non-schedulers.
Resolution:
==========
When using Local Channel Destination to schedule EVENTs:
The cluster scheduler has to be enabled to run on the same engine where the Local channel is configured as an input destination (and disabled for others).
The property below needs to be set to TRUE for the one engine which needs to act as scheduler and should be set to false in all other engines.
<property name="be.engine.cluster.scheduler" value="true"/>
Attachments:
===========
Sample CDD is attached
References:
==========
SR_ID : 1-FJLAFV
Abstract:
==========
Error when using local channel destination to schedule EVENT.
Description:
============
You might use the event scheduler functions instead of a time event in the following cases:
If you need to send any event on a schedule, you must use the scheduler. If you schedule a memory-only simple event, the schedule is persisted. If you schedule a memory only time event (using the time event's function, not the scheduler functions) then the schedule is not persisted.
If you need to create many, perhaps thousands of schedules at one time, performance may be better using the event scheduler functions.
Because schedule management and event sending can be handled by a cache server, fewer resources in the inference agents are required compared to time events. Additionally, with backing store enabled the schedules are only loaded into memory a batch at a time which reduces the total memory requirement compared to time events.
The common practice is to use simple events configured to use an EMS destination to schedule EVENTs. The solution to use EMS destination enables multiple schedulers in the cluster thus making it a scalable solution. But, there could be customer scenarios where they would like only one agent in their cluster scheduling an EVENT and do not want to send a message outside the engine just to schedule an EVENT. They are reluctant to code a process to schedule an event and to only send the event to the one processing unit.
When you use a local destination to schedule an EVENT and do not designate a specific agent as a scheduler, then you will run into issues.
Environment:
===========
All Operating Systems supported for TIBCO Business Events.
Symptoms:
========
EVENT is not scheduled as expected.
Cause:
=====
Not marking a specific agent as designated scheduler and marking all other agents as non-schedulers.
Resolution:
==========
When using Local Channel Destination to schedule EVENTs:
The cluster scheduler has to be enabled to run on the same engine where the Local channel is configured as an input destination (and disabled for others).
The property below needs to be set to TRUE for the one engine which needs to act as scheduler and should be set to false in all other engines.
<property name="be.engine.cluster.scheduler" value="true"/>
Attachments:
===========
Sample CDD is attached
References:
==========
SR_ID : 1-FJLAFV
Issue/Introduction
When trying to send a scheduled event, getting exception saying destination URL is not valid but local destination is valid.
Attachments
Feedback
Yes
No
Powered by
