APAR status
Closed as program error.
Error description
When using MQ as the JMS provider, CRUD operations may delay for the MQ timeout period (as specified in the "Queue connection factories -> MQSRTextSearchConnectionFactory" details panel in the WebSphere Application Server admin console) before succeeding.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of WebSphere Service Registry and Repository Server Version 7.5.0 **************************************************************** PROBLEM SUMMARY: When using WebSphere MQ as the JMS provider, because JMS connections are not being closed properly new requests for connections which can result from any Create, Retrieve, Update or Delete operation are delayed until one of the used connections times out and is replaced in the connection pool.
Problem conclusion
The code was changed to close connections correctly. This fix is targeted for WSRR V7.5.0.3.
Temporary fix
Comments
APAR Information
APAR number
IV14291
Reported component name
SERVICE REGISTR
Reported component ID
5724N7200
Reported release
750
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-01-30
Closed date
2013-02-01
Last modified date
2013-02-01
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
SERVICE REGISTR
Fixed component ID
5724N7200
Applicable component levels
R750 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSWLGF","label":"WebSphere Service Registry and Repository"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
01 February 2013