APAR status
Closed as program error.
Error description
When the same Queue Manager Object is used for both the frontside and backside service with Unit of Work enabled and the "Transactional=true;sync=true" tag in the backend MQ URL, the connection will leak and the message will be uncommitted in the GET queue.
Local fix
By using two separate instances of the MQ Queue Manager Object, the connections are managed and this problem does not occur. Further, if "sync=true" is only used in the MQ URL tag, this problem is not visible even if one instance of Queue Manager Object is used for both frontside and backside service.
Problem summary
MQ connection leak happens under load when front side handler and backend URL use the same connection with "Unit of Work" enabled.
Problem conclusion
This change will be in 3.7.3.9.
Temporary fix
Comments
APAR Information
APAR number
IC65901
Reported component name
DATAPOWER
Reported component ID
DP1234567
Reported release
373
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-01-27
Closed date
2010-02-15
Last modified date
2010-04-08
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DATAPOWER
Fixed component ID
DP1234567
Applicable component levels
R373 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS9H2Y","label":"IBM DataPower Gateway"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.7.3","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
11 February 2022