| Author |
Message
|
| shilpa.sabade |
 Posted: Thu Jul 21, 2011 10:20 am Post subject: Application fails with JMSWMQ2007: Failed to send a message |
 |
|
Voyager
Joined: 23 Feb 2011
Posts: 76
|
we recently installed a new reporting system. This app connects to MQ via JMS Binds. App is deployed in WAS.
MQ is v7013
WAS is v7009
App is failing wth :
RgBean W com.
ERROR: Fatal Exception while generating
Report : Error occurred while putting the message in theRequestQueuecom.
ibm.msg.client.jms.DetailedResourceAllocationException: JMSWMQ2007:
Failed to send a message to destination 'VRSQueue'. JMS attempted to
perform an MQPUT or MQPUT1; however WebSphere MQ reported an error. Use
the linked exception to determine the cause of this error.
com.vermilionsoftware.vrs.common.
exception.VermilionFatalException: Fatal Exception while generating
Report : Error occurred while putting the message in theRequestQueuecom.
ibm.msg.client.jms.DetailedResourceAllocationException: JMSWMQ2007:
Failed to send a message to destination 'VRSQueue'. JMS attempted to
perform an MQPUT or MQPUT1; however WebSphere MQ reported an error. Use
the linked exception to determine the cause of this error.
There is a FDC generated , which has details like :
and also the FDC shows this:
| Probe Id :- JM044008
|
| Application Name :- MQM
|
| Component :- Java_com_ibm_mq_jmqi_local_internal_base
|
| SCCS Info :- com.ibm.mq.jmqi.local/src/native/trace.c,
1.20.2.1 |
....................
| Probe Type :- INCORROUT
|
| Probe Severity :- 4
|
| Probe Description :- AMQ6125: An internal WebSphere MQ error has
occurred. |
| FDCSequenceNumber :- 0
|
| Comment1 :- buffer is null
I took MQ trace , which shows :
Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed
with compcode '2' ('MQCC_FAILED') reason '2071'
('MQRC_STORAGE_NOT_AVAILABLE').
Memory on server is checked , its not shooting up. There is enough memory .
ulimit is set to Unlimited .
any idea what is going wrong here ? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Jul 21, 2011 10:35 am Post subject: Re: Application fails with JMSWMQ2007: Failed to send a mess |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shilpa.sabade wrote: |
I took MQ trace , which shows :
Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed
with compcode '2' ('MQCC_FAILED') reason '2071'
('MQRC_STORAGE_NOT_AVAILABLE'). |
You could have got the same information with a lot less trouble if you'd followed the suggestion:
| shilpa.sabade wrote: |
| Use the linked exception to determine the cause of this error. |
Also:
| shilpa.sabade wrote: |
| Memory on server is checked , its not shooting up. There is enough memory . |
Was this true at the time of the abend? Did you take this MQ trace under the same circumstances, i.e. is it repeatable and if so what are the conditions under which this occurs?
What does this system report? Is it home grown and written in Java?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shilpa.sabade |
| Posted: Thu Jul 21, 2011 10:50 am Post subject: |
|
|
Voyager
Joined: 23 Feb 2011
Posts: 76
|
Vitor -- Which suggestion ?
Trace has captured issue .
Application is written in Java and deployed in WAS. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jul 21, 2011 11:51 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| shilpa.sabade wrote: |
Vitor -- Which suggestion ?
Trace has captured issue .
Application is written in Java and deployed in WAS. |
2071 0x00000817 MQRC_STORAGE_NOT_AVAILABLE
does not apply to memory only.
It could be that you do not have enough physical storage for the queue on the file system, or not enough FS space to allocate more logs etc...
Anyways and due to the multiple fixes in JMS I would suggest you move to WMQ V7.0.1.5
And check the sizing of those file systems.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jul 21, 2011 12:09 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shilpa.sabade wrote: |
| Vitor -- Which suggestion ? |
The one in the original message message - to use the linked exception. Saves running a trace. As well as being exactly the error that occured at that exact time.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shilpa.sabade |
| Posted: Wed Feb 15, 2012 12:10 pm Post subject: |
|
|
Voyager
Joined: 23 Feb 2011
Posts: 76
|
Product support gave following details :
The FDC that is generated indicates that a call to malloc(), made as
part of an MQPUT operation, has failed. There are two possible reasons
for this failure:
-There is not enough storage available on the system to complete the
malloc() request.
-The malloc() call is being made with a zero sized buffer
The FDC caused other errors seen in WAS logs and traces.
The FDC caused other errors seen in WAS logs and traces.
This has a close match to following:
1. 5027.prb - The PRB was created while the customer had previously
reported this issue in the older PMR. The older PMR 33966.082.000 is
closed. The PRB delivered a diagnostic change.
2. PM32094 - This APAR corrected an issue that's similar to this on z/OS
platform. But the change made may apply to all the platform. Please
verify.
One of the approaches would be deliver the iFix for PM32094 on the AIX
platform that customer is using. This will help us further narrow down
the issue.
Following ifix is installed . Now app is working fine .
BINARY:
http://l3.hursley.ibm.com/ftp/fix/WSMQ70/AIXPPC64/7.0.1.3-WS-MQ-AIXPPC64
-LAPM32094-39242.tar.Z
Fix name: 7.0.1.3-WS-MQ-AIXPPC64-LAPM32094-39242
Build number: 39221
Product: WebSphere MQ V7.0.1 (WS-MQ)
Platform: AIX (AIXPPC64)
Maintenance level: 7.0.1.3 *** ONLY APPLY THIS FIX TO A 7.0.1.3
INSTALLATION ***
Date: July 22, 2011
Created for PMR: 92081,082,000
Description:
------------
Interim fix for APAR PM32094:
Package contents:
-----------------
Filename Description - see "Instructions"
below
------------------------------------------------------------------------
-
README.txt This Readme file
java/lib/libmqjbnd.so LIBRARY
java/lib/libmqjexitstub02.so LIBRARY
java/lib64/libmqjbnd.so LIBRARY
java/lib64/libmqjexitstub02.so LIBRARY |
|
| Back to top |
|
|
| techno_123 |
| Posted: Mon Dec 03, 2012 4:36 am Post subject: ('MQCC_FAILED') reason '2071' ('MQRC_STORAGE_NOT_AVAILABLE') |
|
|
Newbie
Joined: 03 Dec 2012
Posts: 2
|
Hi ,
we recently installed a new reporting engine. This app connects to MQ 7.0.1.4 via JMS Binds. App is deployed in WAS 6.1.0.29
.
We are reciving following exception:
The exception which was received is com.ibm.msg.client.jms.DetailedResourceAllocationException: JMSWMQ2007: Failed to send a message to destination 'ENGINE_REPLY_QUEUE'. JMS attempted to perform an MQPUT or MQPUT1; however WebSphere MQ reported an error. Use the linked exception to determine the cause of this error.:com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2071' ('MQRC_STORAGE_NOT_AVAILABLE').
Following is the FFDC log from WMQ 7.0.1.14 on Windows
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Mon December 03 2012 14:34:10 India Standard Time |
| UTC Time :- 1354525450.291000 |
| UTC Time Offset :- 330 ((UNKNWOWN) |
| Host Name :- |
| Operating System :- Windows XP, Build 3790: SP2 |
| PIDS :- 5724H7220 |
| LVLS :- 7.0.1.4 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- JM044008 |
| Application Name :- MQM |
| Component :- Java_com_ibm_mq_jmqi_local_internal_base |
| SCCS Info :- com.ibm.mq.jmqi.local/src/native/trace.c, 1.20.2.1 |
| Line Number :- 554 |
| Build Date :- Jan 14 2011 |
| CMVC level :- p701-104-110114 |
| Build Type :- IKAP - (Production) |
| UserID :- cincom |
|
| Addressing mode :- 32-bit |
| Process :- 00004048 |
| Thread :- 00000168 |
| QueueManager :- INIVN01D |
| UserApp :- TRUE |
| ConnId(1) IPCC :- 360 |
| Last HQC :- 1.0.0-83008 |
| Last HSHMEMB :- 0.0.0-0 |
| Major Errorcode :- OK |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 4 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Comment1 :- buffer is null |
I gues this issue is related to PM32094 .
Can anyone let me know if this is fixed for MQ 7.0.1.5 or 7.0.1.6 on Windows
Thanks-| |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Mon Dec 03, 2012 6:10 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| rekarm01 |
| Posted: Tue Dec 04, 2012 1:49 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| lancelotlinc wrote: |
| WAS 6 is end of life. Upgrade. |
WAS 6.0 is "end of life". WAS 6.1 is not. |
|
| Back to top |
|
|
|
|
