A fix is available
APAR status
Closed as program error.
Error description
Listener process hangs on startup for 5 minutes then gives an fdc with the following information: Probe Id :- RM264002 Component :- rfxConnectCache Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. Comment1 :- Gave up waiting for cache to be initialized Comment2 :- Tried 300 times at 1 second intervals . This is in a clustered environment and the clsuter channels are in retry mode at the time of the problem.
Local fix
Problem summary
The Channel Server calls rriCheckChannels on startup and because there are cluster sender channels in the retry list, the Channel Server attempts to connect to the cache. At the same time the repman is trying to get a channel status from the Channel server, so the cache has not yet been created. The Channel server calls rfxConnectCache which will loop for 5 mins attempting to connect to the cache, without responding to the repman process so both are in a deadlock.
Problem conclusion
Remove the channel server wait on cluster cache operations during queue manager startup
Temporary fix
Terminate the primary channel server process
Comments
APAR Information
APAR number
IC83228
Reported component name
WEBS MQ NSS ITA
Reported component ID
5724A3902
Reported release
531
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-05-08
Closed date
2012-05-08
Last modified date
2012-05-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
WEBS MQ NSS ITA
Fixed component ID
5724A3902
Applicable component levels
R531 PSY
UP
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.3.1"}]
Document Information
Modified date:
19 September 2021