A defect correction provided in EMS 6.0 which is not mentioned in the EMS 6.0.0 release notes.
Article ID: KB0086160
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Description:
There is a defect correction provided in EMS 6.0 which is not mentioned in the EMS 6.0.0 release notes.
This defect was introduced in EMS 5.1.4 when an EMS topic route is defined. It also exists in EMS 5.1.5. During sending of protocol messages to a routed EMS server if the connection to that routed server is broken, an incorrect warning log statement can cause the EMS server to attempt to print a warning log message and crash the server.
The stack trace of the core for this issue is following:
============
=>[1] strncmp(0x1002a2f10, 0xffffffff7b9ff598, 0xffffffff7dda11e4, 0x10853796f, 0x0, 0x1002a2f0f), at 0xffffffff7dd39c70
[2] vsprintf(0x1003eda90, 0x1002a2ee0, 0xffffffff7b9ff590, 0x14106c, 0x140c08, 0xffffffff7dda508c), at 0xffffffff7dda54c0
[3] 0x10019cfc0(0x1, 0x0, 0x2bdc00, 0x1003f4dd0, 0x1003ee980, 0x1002a2ee0), at 0x10019cfc0
[4] _emsTrace(0x20, 0x1002a2ee0, 0x108537940, 0x0, 0x1, 0x100000000), at 0x10019d19c
[5] _emsdRoute_SendTopicInterestInfo(0x111184440, 0x3, 0x3c8c00, 0x1003c8c00, 0x0, 0x64), at 0x1000fbd28
[6] _emsdRoute_ProcessConfigTopics(0x1140fb810, 0x10f5ebcf0, 0x10b1894c0, 0x1003eda90, 0x1003c90d4, 0x2a2c00), at 0x10010136c
[7] _emsd_HandleMetaIOSuccess(0x108450530, 0x10fe9f4e0, 0x11390f728, 0x0, 0xffffffff7c801800, 0x6), at 0x1001094ec
[8] 0x100147874(0x11390f728, 0x10fe9f4e0, 0x0, 0x3d, 0x1, 0x10845ad90), at 0x100147874
[9] _emsdPhasedMsgList_CatchUpHereReal(0x108450530, 0x11390f728, 0x1d, 0x1c0, 0xffffffff7b9ffe74, 0x1003cb6c0), at 0x10014292c
[10] _emsd_StorageThread(0x27b000, 0x10027b000, 0x1002a52f0, 0x0, 0x1, 0x10027b030), at 0x100109810
=============
Environment:
= = = = = =
UNIX
Workaround:
= = = = = =
Since this issue is caused by a warning log statement. You could work around this issue by turning off warning trace option. What you need to do is to use "-WARN" in log_trace and console_trace configuration parameters in the main configuration file.
Symptoms:
Cause:
There is a defect correction provided in EMS 6.0 which is not mentioned in the EMS 6.0.0 release notes.
This defect was introduced in EMS 5.1.4 when an EMS topic route is defined. It also exists in EMS 5.1.5. During sending of protocol messages to a routed EMS server if the connection to that routed server is broken, an incorrect warning log statement can cause the EMS server to attempt to print a warning log message and crash the server.
The stack trace of the core for this issue is following:
============
=>[1] strncmp(0x1002a2f10, 0xffffffff7b9ff598, 0xffffffff7dda11e4, 0x10853796f, 0x0, 0x1002a2f0f), at 0xffffffff7dd39c70
[2] vsprintf(0x1003eda90, 0x1002a2ee0, 0xffffffff7b9ff590, 0x14106c, 0x140c08, 0xffffffff7dda508c), at 0xffffffff7dda54c0
[3] 0x10019cfc0(0x1, 0x0, 0x2bdc00, 0x1003f4dd0, 0x1003ee980, 0x1002a2ee0), at 0x10019cfc0
[4] _emsTrace(0x20, 0x1002a2ee0, 0x108537940, 0x0, 0x1, 0x100000000), at 0x10019d19c
[5] _emsdRoute_SendTopicInterestInfo(0x111184440, 0x3, 0x3c8c00, 0x1003c8c00, 0x0, 0x64), at 0x1000fbd28
[6] _emsdRoute_ProcessConfigTopics(0x1140fb810, 0x10f5ebcf0, 0x10b1894c0, 0x1003eda90, 0x1003c90d4, 0x2a2c00), at 0x10010136c
[7] _emsd_HandleMetaIOSuccess(0x108450530, 0x10fe9f4e0, 0x11390f728, 0x0, 0xffffffff7c801800, 0x6), at 0x1001094ec
[8] 0x100147874(0x11390f728, 0x10fe9f4e0, 0x0, 0x3d, 0x1, 0x10845ad90), at 0x100147874
[9] _emsdPhasedMsgList_CatchUpHereReal(0x108450530, 0x11390f728, 0x1d, 0x1c0, 0xffffffff7b9ffe74, 0x1003cb6c0), at 0x10014292c
[10] _emsd_StorageThread(0x27b000, 0x10027b000, 0x1002a52f0, 0x0, 0x1, 0x10027b030), at 0x100109810
=============
Environment:
= = = = = =
UNIX
Workaround:
= = = = = =
Since this issue is caused by a warning log statement. You could work around this issue by turning off warning trace option. What you need to do is to use "-WARN" in log_trace and console_trace configuration parameters in the main configuration file.
Symptoms:
Cause:
Issue/Introduction
A defect correction provided in EMS 6.0 which is not mentioned in the EMS 6.0.0 release notes.
Feedback
Yes
No
Powered by
