Middleware News

List of processes and what they typically control for MQ: 1. RUNMQLSR - MQ TCP listener (multi-threaded) 2. AMQCLMAA - MQ TCP listener (single-threaded) 3. AMQRMPPA - Channel process pooling job 4. RUNMQCHI - MQ channel initiator 5. AMQCRSTA - MQ receiving MCA jobs 6. RUNMQCHL - MQ sending MCA jobs 7. AMQCRS6B - LU62 receiver channel 8. AMQPCSEA - MQ command server 9. RUNMQTRM - Application trigger monitor 10. RUNMQDLQ - Dead letter queue handler 11. AMQFCXBA - MQ Broker Worker Job 12. RUNMQBRK - MQ Broker Control Job 13. AMQZMUC0 - MQ Utility Manager 14. AMQZMUR0 - MQ Utility Manager 15. AMQZMGR0 - MQ Process Controller 16. AMQRRMFA - MQ cluster repository manager 17. AMQZDMAA - MQ deferred message manager 18. AMQALMPX - MQ Log Manager 19. AMQZFUMA - MQ Object Authority Manager 20. AMQZLAS0 - MQ Local Queue Manager agents 21. AMQZLAA0 - MQ Local Queue Manager agents 22. AMQZXMA0 - MQ Execution Controller

Your JMS application runs on IBM WebSphere® Application Server to connect to a WebSphere MQ messaging system receives an MQJMS2005 error with reason code 2059. Cause Reason code 2059 means that the queue manager is not available. The most likely cause of the problem is that the queue manager is not running or that the queue manager listener is not running. Another possible cause is that the queue manager name that is specified on the JMS connection factory is incorrect. Resolving the problem These are some steps to take to try to resolve the cause of the 2059 error. Confirm that the queue manager is up and running and that the listener is running Ensure that the queue manager is running. You can use the  dspmq  command to verify this. The status of the queue manager should be Running . Check the MQ FDC files in the  MQ_install_root /errors and  MQ_install_root /qmgrs/ queue_manager_name /errors directories to see what relevant error messages may be logged there.