Author |
Message
|
sarasu |
Posted: Tue Feb 28, 2006 2:16 pm Post subject: Workflow error..help needed |
|
|
Master
Joined: 02 Feb 2006 Posts: 229
|
Hi all,
This is the error i am getting when i start my workflow in the services. My webclient is not working now.
I am using Workflow 3.5 MQSeries 5.3 db2...8.1 with Fixpack 7. Finally i need to install Monitor.
ERROR:::
FMC31050E An error has occurred which has terminated processing.
FmcFMLException, MQReturnCode=2, MQReasonCode=2161, MQObjectName=FMCQM, severe error
Help needed.
Thanks |
|
Back to top |
|
 |
karthik |
Posted: Tue Feb 28, 2006 2:39 pm Post subject: |
|
|
 Centurion
Joined: 17 Oct 2003 Posts: 114
|
Your QMGR is not started ..
If it doesnot start .. try starting on command line " strmqm <QMGR> "
and see if that works .. |
|
Back to top |
|
 |
sarasu |
Posted: Wed Mar 01, 2006 7:43 am Post subject: |
|
|
Master
Joined: 02 Feb 2006 Posts: 229
|
It is not running even from the command prompt. what else we can do to start the queuemanager.
Thanks |
|
Back to top |
|
 |
Vitor |
Posted: Wed Mar 01, 2006 7:54 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
When you try to start the queue manager from the command prompt are any error messages received? Are there any FFST dumps or any log messages?
Also, what platform are you running on? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
sarasu |
Posted: Wed Mar 01, 2006 8:00 am Post subject: |
|
|
Master
Joined: 02 Feb 2006 Posts: 229
|
It is showing that Q Manager is ending. Nothing more than that. I am using windows XP platform.
Any Idea? |
|
Back to top |
|
 |
Vitor |
Posted: Wed Mar 01, 2006 8:09 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
It is all consistent, 2161 is the return code for queue manager quiescing. Am I right in saying that this problem has persisted for a while? If so your best bet would be to work out why the qmgr is unable to complete the close down - my first guess would be a badly behaved or crashed application that's not disconnecting. Get rid of that, wait for the qmgr to complete the close down & restart.
If that fails, I refer you to the system administration manual endmqm command options and suggest you try and force it down, then restart it.
Be certain you're desperate before even thinking about the procedure shown in Appendix D - stopping a queue manager manually. Bouncing the box is preferable to deleteing processes on Windows!
(Was desperate once. Tried it once. Ended badly)  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
sarasu |
Posted: Wed Mar 01, 2006 8:37 am Post subject: |
|
|
Master
Joined: 02 Feb 2006 Posts: 229
|
I tried to delete from explorer, i deleted the q manager. But in services it is still there. All services are stopped except "CommandServer" it is still running.WHen i check from command prompt the qmanager is still quiescing... ..???
Thanks |
|
Back to top |
|
 |
Vitor |
Posted: Wed Mar 01, 2006 8:41 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Yes, well, when I said "look up the endmqm command" I wasn't aware it could be interpreted as "delete it from the gui"!
Oh well.
Is this XP machine a laptop/desktop for your use or a server? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
sarasu |
Posted: Wed Mar 01, 2006 8:58 am Post subject: |
|
|
Master
Joined: 02 Feb 2006 Posts: 229
|
Its a desktop. Right now i am using for myself only. May be later we may connect to server. |
|
Back to top |
|
 |
sarasu |
Posted: Wed Mar 01, 2006 9:00 am Post subject: |
|
|
Master
Joined: 02 Feb 2006 Posts: 229
|
can i create another Q manager with different name for the same Java API??? Because FMC is not running.. |
|
Back to top |
|
 |
Vitor |
Posted: Wed Mar 01, 2006 9:16 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Connection to a queue manager is defined within your API code (as part of the Connection object if memory serves me but it often doesn't with Java!) so in theory you can create as many queue managers as you like & point what you want at them. I worry that a) the current queue manager (or bits of it) will return like some kind of zombie when you reboot & b) whatever caused your initial problem will affect this new one.
I'd try and clear up the remains of the existing queue manager using the dltmqm command & endmqcsv (see the System Admin manual for details, and I do mean see it - don't just type!) then reboot & see what you've got.
(I personally do no administration from the gui - I don't trust it. Maybe I'm old & too rooted in the good old days of mainframe, with control cards and console commands)  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
sarasu |
Posted: Wed Mar 01, 2006 9:51 am Post subject: |
|
|
Master
Joined: 02 Feb 2006 Posts: 229
|
Ok..Thanks man..I will try to figure it out with your words. |
|
Back to top |
|
 |
|