EMS-3851 fixed in EMS 6.1.0 on Linux platform
Article ID: KB0094348
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Description:
Description:
=======================
We have addressed issue EMS-3851 in EMS 6.1.0:
EMS-3851: Fixed an issue that could cause the EMS server to crash when the client connected and disconnected frequently.
This issue was caused by a free memory read (FMR). These types of defects can exhibit different behavior depending on the pattern of memory allocations and deallocations which are highly dependent on threading. An FMR may cause no problem whatsoever if the deallocated memory has not been reallocated and the locations being accessed have not changed. An FMR can cause a crash if the freed memory has been changed and the accessing code expects to find a valid pointer there. An FMR can cause other undefined behaviors if the freed memory contains integer or Boolean values that are no longer valid.
Some customers have been impacted by this defect. In some cases, symptoms were that the server would not be able to accept new connections, while the existing ones would work fine. In other cases, the server would become un-responsive, or in some other cases, the server would crash. We have only noticed this issue on Linux platforms.
Environment:
=======================
EMS 6.0.0, EMS 6.0.1 server on Linux platforms
Resolution:
=========================
Upgrade to EMS 6.1.0.
If you cannot upgrade to EMS 6.1.0, please download EMS 6.0.1 hotfix from site <ftp://support-ftp.tibco.com>. Please use your support web login credentials and the hotfix tibems-6.0.1-linux26gl23_x86-hf03.tar.gz will be available at the following path <ftp://support-ftp.tibco.com/available_downloads/ActiveEnterprise/Messaging/EMS/6.0.1/Hotfix_3>
Description:
=======================
We have addressed issue EMS-3851 in EMS 6.1.0:
EMS-3851: Fixed an issue that could cause the EMS server to crash when the client connected and disconnected frequently.
This issue was caused by a free memory read (FMR). These types of defects can exhibit different behavior depending on the pattern of memory allocations and deallocations which are highly dependent on threading. An FMR may cause no problem whatsoever if the deallocated memory has not been reallocated and the locations being accessed have not changed. An FMR can cause a crash if the freed memory has been changed and the accessing code expects to find a valid pointer there. An FMR can cause other undefined behaviors if the freed memory contains integer or Boolean values that are no longer valid.
Some customers have been impacted by this defect. In some cases, symptoms were that the server would not be able to accept new connections, while the existing ones would work fine. In other cases, the server would become un-responsive, or in some other cases, the server would crash. We have only noticed this issue on Linux platforms.
Environment:
=======================
EMS 6.0.0, EMS 6.0.1 server on Linux platforms
Resolution:
=========================
Upgrade to EMS 6.1.0.
If you cannot upgrade to EMS 6.1.0, please download EMS 6.0.1 hotfix from site <ftp://support-ftp.tibco.com>. Please use your support web login credentials and the hotfix tibems-6.0.1-linux26gl23_x86-hf03.tar.gz will be available at the following path <ftp://support-ftp.tibco.com/available_downloads/ActiveEnterprise/Messaging/EMS/6.0.1/Hotfix_3>
Issue/Introduction
EMS-3851 fixed in EMS 6.1.0 on Linux platform
Feedback
Yes
No
Powered by
