| Author |
Message
|
| abd.wsu |
 Posted: Mon Aug 01, 2016 8:32 am Post subject: Tomcat app stops picking messages |
 |
|
Acolyte
Joined: 12 Sep 2012
Posts: 65
|
I have a peculiar issue where a tomcat application running on OpenStack is connecting to our MQ7504 Queue manager running on RHEL6.
The connection is fine, i see the channel running and IPPROCS on the queue to pick up messages.
However, at 1.00 AM on random days, the application simply stops picking up messages. The app team confirmed that there is batch that puts more messages on the queue at 1.00 AM everyday, but the no. of messages is only around 100. The size of the messages is not big either. Only upto a 1000 bytes.
The messages are good. No backout count.
The only way to resolve this has been to restart the jvm. There is literally no error recorded in the MQ logs, no fdcs cut or anything. The channel keeps running, the IPPROCS stay connected. Just not picking the messages.
The app team confirmed that they don't see any errors in their logs either.
Have any of you come across a similar issue before? I copied the messages and tried to recreate this in a different environment, but the issue didn't happen. I want to run traces but since it is random i am really sure.
Any clues? |
|
| Back to top |
|
 |
| PaulClarke |
| Posted: Mon Aug 01, 2016 10:55 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
The Channel may be running but have you tried to detect what it is doing ? On the Queue Manager what is the SUBSTATE value of the SVRCONN channel status? ie. is the client really in a GET call ?
Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| sselva86 |
| Posted: Mon Aug 01, 2016 9:11 pm Post subject: |
|
|
Novice
Joined: 25 Oct 2010
Posts: 17
|
If the channel is running its worth to check Number of Bytes Sent (NUMBYTES) on that particular channel it should get increase if messages are processing .
Does the channel is having batch size mentioned . may be end of batch notification which says the batch has been completed may not be sent to source due to network problems . |
|
| Back to top |
|
|
| abd.wsu |
| Posted: Wed Aug 24, 2016 5:35 pm Post subject: |
|
|
Acolyte
Joined: 12 Sep 2012
Posts: 65
|
| I opened a PMR with IBM. They said the issue could be with some outdated client jar files being used by the application. We have updated the jars. Let's see. |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Aug 24, 2016 11:08 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
Look at the remote client version on the channel status for the connection.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
|
|
