We have an application running SpringBoot connecting to an MQ Queue Manager. Recently we had some kind of event occur that resulted in significantly degraded performance. The MQ team did not see anything in the logs on the server. In our client we saw multiple instances of the following but no detailed information indicating why the client was having an issue.
Rejecting received message because of the listener container having been stopped in the meantime:
JMSMessage class: jms_bytes
JMSType: null
JMSDeliveryMode: 2
JMSDeliveryDelay: 0
JMSDeliveryTime: 0
JMSExpiration: 0
JMSPriority: 0
JMSMessageID: ID:414d5120514d2e4b4c4f472e50524f44fc11ec63016ad623
JMSTimestamp: 1676416112950
JMSCorrelationID: ID:414d5120514d2e4b4c4f472e50524f44cb2420628ad4c628
JMSDestination: topic://MY/PROD/TOPIC
JMSReplyTo: null
JMSRedelivered: true
JMSXAppID: QM.PROD
JMSXDeliveryCount: 2
JMSXUserID: mqm
JMS_IBM_Character_Set: ISO-8859-1
JMS_IBM_Encoding: 546
JMS_IBM_Format:
JMS_IBM_MsgType: 8
JMS_IBM_PutApplType: 26
JMS_IBM_PutDate: 20230214
JMS_IBM_PutTime: 23083295
3c4e53313a536967526f757465207
I was able to track this to the AbstractMessageListenerContainer class.
What might have been helpful is to enable logging for IBM MQ client (9.1.0.5) but I could not find out how to get that working. Do you have anything you can point me to that will help me configure the IBM MQ client logging in the event his happens again?
Looking for message log files won't help. The incident was causing the k8s container to be declared unhealthy and repeatedly killed. There is no persistent storage to save the log files to.
------------------------------
Will Schneider
------------------------------