| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQRC_CALL_IN_PROGRESS |
« View previous topic :: View next topic » |
| Author |
Message
|
| mahesh |
 Posted: Wed Sep 17, 2008 2:12 am Post subject: MQRC_CALL_IN_PROGRESS |
 |
|
Newbie
Joined: 19 Aug 2008
Posts: 4
|
Hi,
I am using wmq 6.0.2.3, i have configured a setup like - a java process(program) monitoring the local queue ,when every a messages comes into the queue that java process get the message from the queue and process the message.this entire process is captured by log files.
when ever other people logon to the server, java process is ending automatically.and the following fdc is creating in wmq/erros. please help me.
thanks.
FDC
---------------------------------------------------------------
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Mon September 08 07:34:26 GMT Daylight Time 2008 |
| Host Name :- BRESACAS001 (Windows 2000, Build 2195: Service Pack 4) |
| PIDS :- 5724H7200 |
| LVLS :- 6.0.2.3 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- JD514000 |
| Application Name :- MQM |
| Component :- DmQueueManager.onError |
| SCCS Info :- lib/cs/amqxeida.c, 1.52.1.21 |
| Line Number :- 3453 |
| Build Date :- Jan 23 2008 |
| CMVC level :- p600-203-080123 |
| Build Type :- IKAP - (Production) |
| UserID :- TH76612N |
| Process Name :- E:\Program Files\IBM\Eclipse SDK30\eclipse\jre\bin |
| \javaw.exe |
| Addressing mode :- 32-bit |
| Process :- 00006568 |
| Thread :- 00000008 |
| Major Errorcode :- MQRC_CALL_IN_PROGRESS |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ08AB |
| Probe Severity :- 4 |
| Probe Description :- AMQ6090: WebSphere MQ was unable to display an error |
| message 8AB. |
| FDCSequenceNumber :- 0 |
| Comment1 :- MQJE001: Completion Code 2, Reason 2219 |
| |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
xcsFFST
MQM Trace History
---{ xcsAquireThread
Data: 0x00000006
---} xcsReleaseThread rc=OK
---{ xcsReleaseThreadMutexSem
---} xcsReleaseThreadMutexSem rc=OK
---{ xcsRequestThreadMutexSem
---} xcsRequestThreadMutexSem rc=OK
---{ xcsReleaseThreadMutexSem
---} xcsReleaseThreadMutexSem rc=OK
--} zutReleaseSharedPCD rc=OK
-} zstMQGET rc=OK
} MQGET rc=OK
{ MQGET
-{ zstMQGET
--{ zutAquireSharedPCD
---{ xcsRequestThreadMutexSem |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Wed Sep 17, 2008 3:35 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
this is the corrective action to it
Corrective action: Ensure that an MQI call cannot be issued while another one is active. Do not issue MQI calls from within a data-conversion exit. On z/OS, if you want to provide a subtask to allow an application that is waiting for a message to arrive to be canceled, wait for the message by using MQGET with MQGMO_SET_SIGNAL, rather than MQGMO_WAIT.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| 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
|
|
|
|
