ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » WF messages go to DLQ, runmqtrm generates .FDC

Post new topic  Reply to topic
 WF messages go to DLQ, runmqtrm generates .FDC « View previous topic :: View next topic » 
Author Message
Guava72
PostPosted: Fri Apr 14, 2006 7:06 am    Post subject: WF messages go to DLQ, runmqtrm generates .FDC Reply with quote

Apprentice

Joined: 06 Jun 2003
Posts: 46
Location: Champaign, IL
Hi,
We are using WMQ 5.3.05 and MQWF 3.4 on HP-UX 11i.
Our messages are going to the DLQ on our WF Server QM, and the runmqtrm process generates an .FDC file.
I don't see the cause for this in the MQ or MQWF logs. If anyone has solved this problem or has some other ideas, please let me know. Thanks in advance!

Quote:
fmc@cmih125> cat AMQ25272.0.FDC
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Thursday April 13 18:57:18 CDT 2006 |
| Host Name :- cmih125 (HP-UX B.11.11) |
| PIDS :- 5724B4102 |
| LVLS :- 530.5 CSD05 |
| Product Long Name :- WebSphere MQ for HP-UX |
| Vendor :- IBM |
| Probe Id :- XC338001 |
| Application Name :- MQM |
| Component :- xehAsySignalHandler |
| Build Date :- Sep 27 2003 |
| CMVC level :- p530-05-L030926 |
| Build Type :- IKAP - (Production) |
| UserID :- 00500423 (fmc) |
| Program Name :- runmqtrm_nd |
| Process :- 00025272 |
| Thread :- 00000002 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 1 1 |
| Arith2 :- 25272 62b8 |
| Comment1 :- SIGHUP |
| |
| |
+-----------------------------------------------------------------------------+

MQM Function Stack
xehAsySignalMonitor
xehHandleAsySignal
xcsFFST

MQM Trace History
{ xppInitialiseDestructorRegistrations
} xppInitialiseDestructorRegistrations rc=OK
{ xehAsySignalMonitor
-{ xppPostAsySigMonThread
-} xppPostAsySigMonThread rc=OK
-{ xehHandleAsySignal
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsReleaseThreadMutexSem
--} xcsReleaseThreadMutexSem rc=OK
-} xehHandleAsySignal rc=OK
-{ xehHandleAsySignal
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsReleaseThreadMutexSem
--} xcsReleaseThreadMutexSem rc=OK
-} xehHandleAsySignal rc=OK
-{ xehHandleAsySignal
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsReleaseThreadMutexSem
--} xcsReleaseThreadMutexSem rc=OK
-} xehHandleAsySignal rc=OK
-{ xehHandleAsySignal
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsReleaseThreadMutexSem
--} xcsReleaseThreadMutexSem rc=OK
-} xehHandleAsySignal rc=OK
-{ xehHandleAsySignal
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsReleaseThreadMutexSem
--} xcsReleaseThreadMutexSem rc=OK
-} xehHandleAsySignal rc=OK
-{ xehHandleAsySignal
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsReleaseThreadMutexSem
--} xcsReleaseThreadMutexSem rc=OK
-} xehHandleAsySignal rc=OK
-{ xehHandleAsySignal
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsReleaseThreadMutexSem
--} xcsReleaseThreadMutexSem rc=OK
-} xehHandleAsySignal rc=OK
-{ xehHandleAsySignal
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsReleaseThreadMutexSem
--} xcsReleaseThreadMutexSem rc=OK
-} xehHandleAsySignal rc=OK
-{ xehHandleAsySignal
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsFFST

Component Dumps (Thread 00000002)
-------------------------------------
fmc@cmih125>
Back to top
View user's profile Send private message Send e-mail
Guava72
PostPosted: Fri Apr 14, 2006 7:22 am    Post subject: Reply with quote

Apprentice

Joined: 06 Jun 2003
Posts: 46
Location: Champaign, IL
I usually run the Trigger Monitor in the background, but to get some more info I kept the shell. It seems to be having trouble with a Process related to the Scheduling Server:

Quote:
Waiting for a trigger message

/var/fmc/cfgs/FMCENV2/bin/fmczsmst 'TMC 2 FMC.FMCENV2.FMCENV2.PROC.SCH /var/fmc/cfgs/FMCENV2/bin/fmczsmst & -i:SchedSvr -y:FMCENV2 FMCENV2 ' &
Error starting triggered application.


So I'll try deleting and recreating this Process. And also I'll make sure there is not some problem with the fmczsmst binary.
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » WF messages go to DLQ, runmqtrm generates .FDC
Jump to:  



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
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.