| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| JMS connection - Asysnchrnous state suspended |
« View previous topic :: View next topic » |
| Author |
Message
|
| lemmeno |
 Posted: Tue Aug 20, 2013 8:44 am Post subject: JMS connection - Asysnchrnous state suspended |
 |
|
Newbie
Joined: 15 Mar 2007
Posts: 2
|
Hi,
We are currently facing an issue where our psft application is unable to read messages from a queue, despite being able to connect to the queue. When looked at the queue status, I see three connections from the application, but their Asynchronous state is set to 'Suspended'.
I did some research around this issue, and found the MQ version should be at 7.0.1.5. Our version of MQ is at a higher level, MQ 7.0.1.7.
I understand this happens when multiple connections try to retrieve msgs from a queue and application side buffer is grown, but the consumer is not
re-enabled; therefore, not receiving any further messages. We do not want to restarting the application during the day and so were wondering if you guys could point us if something else could be done to fix the problem.
Appreciate your time. |
|
| Back to top |
|
 |
| JosephGramig |
| Posted: Tue Aug 20, 2013 11:01 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
| First, the latest maintenance is 7.0.1.10 and you should apply that and come back if your problem is not fixed. Ensure the client is also up to date if it isn't on the same box. Ensure you are not repackaging WMQ JAR files and redeploying them. Use a legitimate install of Server or Client. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Aug 20, 2013 11:14 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| And then review the behavior of JMS Message Consumers under poison message scenarios. |
|
| Back to top |
|
|
| raanbala1 |
| Posted: Mon Feb 17, 2014 2:44 am Post subject: |
|
|
Newbie
Joined: 17 Feb 2014
Posts: 1
|
Hi Guys,
I also face the same kind of issue : application is unable to read messages from a queue, despite being able to connect to the queue. When looked at the queue status, I see three connections from the application, but their Asynchronous state is set to 'Suspended'.
we have MQ on z/OS; version: 7.0.1 and its JMS application on version 7.0.1.1
ST.MFManifest-Version: 1.0
Ant-Version: Apache Ant 1.7.0
Created-By: 1.4.2 (IBM Corporation)
Copyright-Notice: Licensed Materials - Property of IBM 5724-H72,
5655-R36, 5724-L26, 5655-L82 (c) Copyright IBM Corp. 2008 A
ll Rights Reserved. US Government Users Restricted Rights -
Use,duplication or disclosure restricted by GSA ADP Schedule
Contract with IBM Corp.
Sealed: false
Specification-Title: Java Message Service
Specification-Version: 1.1
Specification-Vendor: Sun Microsystems, Inc.
Implementation-Title: WebSphere MQ classes for Java Message Service
Implementation-Version: 7.0.1.1 |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Feb 17, 2014 7:53 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Distributed GA for 7.0.1 was 7.0.1.3 and there were a lot of fixes in JMS up until 7.0.1.5... I believe the latest is 7.0.1.10 or thereabouts. Don't know what the latest version is for zOS but you would be wise to upgrade and check if the behavior you see is still true. If it is, open a PMR. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Wed Feb 19, 2014 5:13 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
A consumer on the server can become suspended for all sorts of reasons and isn't itself necessarily a cause for concern.
For example, over a client when using read ahead the consumer will suspend itself if it has sent the full quota to the client and will then wait for the client to request more messages. This is to prevent the server from swamping the client with more messages than it can process.
If you find that messages are not being processed in your Application server then I would look more closely at whether the Activation Port/Listeners etc are running and whether the MDBs are enabled etc. If all looks good then perhaps it's time for a call to service, however just simply seeing the consumers marked as suspended is no cause for alarm.
Regards,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
