Your WebSphere MQ command server failed with error message AMQ8504 in the queue manager error logs and with FDC files generated for the amqpcsea process.
In the queue manager error log you see the following messages:
AMQ8504: Command server MQINQ failed with reason code 2009.
EXPLANATION: An MQINQ request by the command server, for the WebSphere MQ queue
SYSTEM.ADMIN.COMMAND.QUEUE failed with reason code 2009.
AMQ5025: The command server has ended. ProcessId(14615006).
EXPLANATION: The command server process has ended.
There are FFST entries generated for the command server process, amqpcsea:
amqpcsea 14615006 1 XC332056 xlsWaitEvent xecL_E_INTERRUPT OK
amqpcsea 14615006 1 XC332035 xlsWaitEvent STOP OK
The first FDC indicates that the command server process was woken from xlsWaitEvent without an appropriate post operation by another thread. The command server wait code finds itself in an unexpected state and attempts to reset and try the wait again.
The second FDC indicates that the second wait also failed due to an unexpected state.
The original problem was due to a synchronization issue in the xlsWaitEvent code. This caused the XC332056 xlsWaitEvent FDC. The FDC XC332056 xlsWaitEvent could in theory hit any of the WMQ
processes and application processes could not be isolated to the command server.
Resolving the problem
This issue was determined to be a defect in the WMQ code and is being address via APAR IV27982. The work around to this problem is to restart your command server.
WebSphere MQ WMQ