Author |
Message
|
Pablo Taboada |
Posted: Thu Sep 06, 2007 4:55 am Post subject: Queue Manager goes down when I logoff. |
|
|
Apprentice
Joined: 19 Jul 2007 Posts: 36 Location: Spain - Barcelona
|
I have installed WebSphere MQ 6.0 with maintenance level 6.0.2.1 under windows 2000 Service Pack 4 and I have next problem:
If I run the "strmqm QMGR" command. Quene manager starts right, but when I logoff, the Queue Manager goes down.
I have configured it as Automatic and Queua Manager control.
WebSphere MQ Service is automatic.
Anybody can help me?
A lot of thanks _________________ Regards,
Pablo Taboada
INSA - IBM Global Services
WebSphere MQ System Administrator Certified |
|
Back to top |
|
 |
Vitor |
Posted: Thu Sep 06, 2007 5:06 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
What id is the service running as? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Thu Sep 06, 2007 5:22 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
Pablo, if your strmqm under your ID, the QM will end when you end (log off).
Look up the amqmdain command that lets you start up the QM as a "service" itself. Then it will remain running when you logoff.
Better yet, use MQExplorer on Windows to stop and start your QM. That works like amqmdain. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
Pablo Taboada |
Posted: Thu Sep 06, 2007 5:24 am Post subject: |
|
|
Apprentice
Joined: 19 Jul 2007 Posts: 36 Location: Spain - Barcelona
|
Service Id: MQSeriesServices _________________ Regards,
Pablo Taboada
INSA - IBM Global Services
WebSphere MQ System Administrator Certified |
|
Back to top |
|
 |
Pablo Taboada |
Posted: Thu Sep 06, 2007 5:30 am Post subject: |
|
|
Apprentice
Joined: 19 Jul 2007 Posts: 36 Location: Spain - Barcelona
|
Hi Peter,
I've just trid with MQExplorer and I obtain the same problem. _________________ Regards,
Pablo Taboada
INSA - IBM Global Services
WebSphere MQ System Administrator Certified |
|
Back to top |
|
 |
Vitor |
Posted: Thu Sep 06, 2007 5:30 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Pablo Taboada wrote: |
Service Id: MQSeriesServices |
I meant user id!!
I'd have expected "mqm" or "Local System".
It sounds a lot like it's using your id. Either change the service or use Peter's excellent suggestions. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Pablo Taboada |
Posted: Thu Sep 06, 2007 5:39 am Post subject: |
|
|
Apprentice
Joined: 19 Jul 2007 Posts: 36 Location: Spain - Barcelona
|
Uhm sorry... I was abset-minded...
User Id than runs service is Local System. _________________ Regards,
Pablo Taboada
INSA - IBM Global Services
WebSphere MQ System Administrator Certified |
|
Back to top |
|
 |
Vitor |
Posted: Thu Sep 06, 2007 5:51 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Pablo Taboada wrote: |
Uhm sorry... I was abset-minded...
|
And I should have been more explicit.  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Pablo Taboada |
Posted: Thu Sep 06, 2007 6:06 am Post subject: |
|
|
Apprentice
Joined: 19 Jul 2007 Posts: 36 Location: Spain - Barcelona
|
Message that I obtain when I start Queue Manager...
C:\Documents and Settings\INSXM01>strmqm ESISAI00
WebSphere MQ queue manager 'ESISAI00' starting.
29 log records accessed on queue manager 'ESISAI00' during the log replay phase.
Log replay for queue manager 'ESISAI00' complete.
Transaction manager state recovered for queue manager 'ESISAI00'.
WebSphere MQ queue manager 'ESISAI00' started.
Where ESISAI00 is the QMGR Name. _________________ Regards,
Pablo Taboada
INSA - IBM Global Services
WebSphere MQ System Administrator Certified |
|
Back to top |
|
 |
Vitor |
Posted: Thu Sep 06, 2007 6:13 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
And these messages concern you why? Perfectly normal & nothing to do with why it closed. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
UglyAngelX |
Posted: Thu Sep 06, 2007 7:36 am Post subject: |
|
|
Voyager
Joined: 04 Dec 2001 Posts: 90 Location: BEARS FAN IN STEELER COUNTRY
|
Do you possibly have a DOMAIN ID in place and that id is not part of your domain mqm group? I have run into this issue when the Domain ID's were not added to the proper groups. |
|
Back to top |
|
 |
Pablo Taboada |
Posted: Thu Sep 06, 2007 8:41 am Post subject: |
|
|
Apprentice
Joined: 19 Jul 2007 Posts: 36 Location: Spain - Barcelona
|
Exactly. That's the question!
I have solved it, changing the domain configuration.
The problem was MQSeriesServices wasn't running with MUSR_MQADMIN. I've changed it in "Prepare WebSphere MQ Wizard", -> "WebSphere MQ Network Configuration" by selecting that I have not any Domain controler.
A lot of thanks to all!!! _________________ Regards,
Pablo Taboada
INSA - IBM Global Services
WebSphere MQ System Administrator Certified |
|
Back to top |
|
 |
|