Fixes are available
APAR status
Closed as program error.
Error description
This affects modules with a JMS import binding where the response timeout specified, on the SCA reference wired to the JMS import, has been reached before a response is received. The callback message is expired and processed but an extraneous callback message is sent to the callback destination. The expiration time of the message is set to 0, which indicates the message will never expire. This APAR prevents these unnecessary callback messages being sent when processing an expiry message.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of WebSphere Enterprise Service Bus * * and WebSphere Process Server v7 who use * * JMS bindings. * **************************************************************** * PROBLEM DESCRIPTION: If the response timeout that is * * specified on an SCA reference that * * has a JMS Import wired to it * * elapses before a response is * * received, the callback message for * * that response will be expired. This * * will then be processed. * * An extraneous callback message is * * then sent to the callback * * destination, which is set to never * * expire. * **************************************************************** * RECOMMENDATION: * **************************************************************** The response timeout in an SCA reference can be used to control the expiration time of JMS messages sent to a JMS Import wired to that reference. When a message is sent through that Import, a callback message is placed on a callback destination. If the expiration time elapses before a response is received, this callback message will be expired. Processing this expired callback message caused a callback message with an expiration time of 0 (which means it does not expire) to be then sent to the callback destination. This APAR prevents these unnecessary callback messages being sent when processing an expiry message.
Problem conclusion
The code was modified such that unnecessary, unexpiring callback messages are not sent to the callback destination when processing an expiry message There are no known side effects associated with this fix. There is no known alternative workaround should you encounter this problem. This code fix was targeted to be included in the following fix packs: 7.0.0 Fix Pack 3 (v7.0.0.3)
Temporary fix
Comments
APAR Information
APAR number
IC68262
Reported component name
WEB ESB FOR WIN
Reported component ID
5724I8200
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-04-30
Closed date
2010-05-28
Last modified date
2010-05-28
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
WEB ESB FOR WIN
Fixed component ID
5724I8200
Applicable component levels
R100 PSN
UP
R200 PSN
UP
R300 PSN
UP
R612 PSN
UP
R620 PSN
UP
R700 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7J6S","label":"WebSphere Enterprise Service Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
30 March 2023