After upgrading from EMS 5.x to 6.0 onwards, create route failure is seen if incoming_topic or its parent does not exist in the EMS server.
Article ID: KB0093339
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Description:
After upgrade from 5.x to 6.0 onwards, create route failure is seen if incoming_topic or its parent does exist in the EMS server.
Symptoms:
N/A
Cause:
Since EMS 6.0, the server enforces creating the incoming topic when creating a route. This is a change that has been introduced during code refactoring in EMS 6.0.0. Do not use the addprop command as it can cause inconsistency between the runtime and config file due to this change.
After upgrade from 5.x to 6.0 onwards, create route failure is seen if incoming_topic or its parent does exist in the EMS server.
Symptoms:
N/A
Cause:
Since EMS 6.0, the server enforces creating the incoming topic when creating a route. This is a change that has been introduced during code refactoring in EMS 6.0.0. Do not use the addprop command as it can cause inconsistency between the runtime and config file due to this change.
Issue/Introduction
After upgrading from EMS 5.x to 6.0 onwards, create route failure is seen if incoming_topic or its parent does not exist in the EMS server.
Resolution
EMS Engineering has decided to revert to the 5.1.5 behavior. The following JIRA issue has been logged which will be addressed in a future release:
Before this fix is implemented, you need to make sure the incoming_topic exists before creating the route. Make sure that the g_topic exists before creating the route.
EMS-6201 - Failed to create the route if incoming_topic or its parent doesn't exist in the EMS server since EMS 6.0.
Before this fix is implemented, you need to make sure the incoming_topic exists before creating the route. Make sure that the g_topic exists before creating the route.
Feedback
Yes
No
Powered by
