|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
What is this FmcTransXException? |
« View previous topic :: View next topic » |
Author |
Message
|
praveenchhangani |
Posted: Thu May 08, 2003 5:45 am Post subject: What is this FmcTransXException? |
|
|
 Disciple
Joined: 20 Sep 2002 Posts: 192 Location: Chicago, IL
|
Anyone know what a FmcTransXException might be caused by? Below is what I found in the sys log. The error pretty much has the same info.
FMCSYS.LOG:
-----------------------------
05/07/03 12:11:05 FMC31050E An error has occurred which has terminated processing.
05/07/03 12:11:05 FmcTransXException, ReturnCode=2122
-----------------------------
05/07/03 12:18:27 FMC31050E An error has occurred which has terminated processing.
05/07/03 12:18:27 FmcTransXException, ReturnCode=212205/07/03 12:24:57 FMC31050E An error has occurred which has terminated processing.
05/07/03 12:24:57 FmcFMLException, MQReturnCode=2, MQReasonCode=2161, MQObjectName=FMC.FMGRP.FMSYS2.EXE, severe error05/07/03 12:24:57 FMC31050E An error has occurred which has terminated processing.
Any input is appreciated.
Thanks,Praveen _________________ Praveen K. Chhangani,
IBM Certified Solutions Designer -
MQ Workflow 3.4. |
|
Back to top |
|
 |
vennela |
Posted: Thu May 08, 2003 6:12 am Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
Praveen:
From the error logs looks like you have 2121(participant not available) and 2161 (qmanager quiescing).
Either your qmanager was shutdown before MQWF server or DB2 was shutdown before MQWF Server or may be both.
-------
Venny |
|
Back to top |
|
 |
praveenchhangani |
Posted: Thu May 08, 2003 11:01 am Post subject: |
|
|
 Disciple
Joined: 20 Sep 2002 Posts: 192 Location: Chicago, IL
|
I believe you are correct Venny. What had originally happened is that fmcamain went down and so did 2 of my execution servers(fmcemain). At that point in time, I went ahead and tried to start fmcamain, but workflow in turn decided to take a core dump.
Confused at this point, I checked my listeners and they were fine, but the queue manager happened to be in an odd state. After a few minutes the queue manager came down by itself, so I tried to start it back up, but there was still an associated mq queue manager related process (Keep in mind this is on AIX), so I decided to kill the process.
At this point in time, I was successfully able to bring the configuration back up and running, which brings me back to the same question.....Why did this occur in the first place??? Based on the logs, it is kind of hard to come to a judgement, but Venny's observation on the queue manager's state is definitely in conjunction with what I was thinking.
Here's another question, is the coredump in a format that one can understand. It would be interesting to see if the coredump has any information as far as the system itself is concerned.
Thanks for your replies!
Praveen _________________ Praveen K. Chhangani,
IBM Certified Solutions Designer -
MQ Workflow 3.4. |
|
Back to top |
|
 |
misraasheesh |
Posted: Tue Dec 26, 2006 1:24 am Post subject: FMC31050E : Error Terminated while processing. |
|
|
Newbie
Joined: 07 Sep 2006 Posts: 6
|
There are some reason to come this kind of error :
First : Template space problem,so check your database template space and increase it.In this case you will get sql=-289 error also.
Second : Might be someone deleted entry from runtime database,so again import FDL in the workflow server and try again.
Third : You had more than 1 DB2 database associated with the Workflow
queue manager. The following are the actions you performed:
Went to the MQSeries console, highlighted the QMGR, right-
clicked and selected "Properties", and then went to the Resources
tab (XA Resource Manager Settings). Then clicked on the pulldown
entitled "Name" and noted that there was more than 1 DB2 database
named there. Deleted all the databases listed in that pulldown
except the one that was supposed to be there. Saved the
information, then stopped the QMGR and restarted it, and the problem
was resolved.
Regards,
Asheesh Misra |
|
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
|
|
|
|