Error getQueueName in the log

Document ID : KB000045187
Last Modified Date : 14/02/2018
Show Technical Document Details

Symptoms: 

Seeing below error several times in my MQ Agent log:

[WARN] [IntroscopeAgent.MQNameFormatter] CAMQ7QueueSender:getQueueName:Exception:null
[WARN] [IntroscopeAgent.MQNameFormatter] CAMQ7QueueSender:getQueueName:Exception:null
[WARN] [IntroscopeAgent.MQNameFormatter] CAMQ7QueueSender:getQueueName:Exception:null

 

Environment:  

Introscope MQ Agent from 9.5x to 10x

 

Cause: 

With regards to the warning message you observed in the logs, this particular warning is repeating because, MQPP is trying to connect to the queue manager at localhost while trying to find out the queue type, which is throwing RC 2059 errors. RC 2059 means that the queue manager is not available to connect.

 

Workaround:

1. If only the normal MQ Appsetup is in use, then this could indicate a problem with the configuration.  You will need to check if the queue manager that the app is trying to connect is up and running or not.

2. The use of High Availability or Fail Over mechanism feature in MQ. As we do not support this feature as yet, MQPP could not handle the process of failing over/connecting to the secondary server, hence throwing RC 2059 error which subsequently followed by the above warning message.

If this is caused by HA which we currently does not support, you can either ignore this warning, or turn off the following entry in webspheremq.pbd file, in which MQPP is trying to connect to the MQ QM, to eliminate the warning:

#TurnOn:MQJMSmqQueueSender


After commenting out the above, a restart is needed.

Additional Information:

Please note that few metrics will be missing as a result of turning off the above tracer. If you do not want to miss any metrics, then ignoring the warning messages will be the other alternative.