| Author |
Message
|
| In_love_with_MQ |
 Posted: Thu Nov 16, 2006 7:18 am Post subject: windows 2003 MQ 6 : QM END WHEN USERS LOG OUT |
 |
|
Acolyte
Joined: 10 Jul 2005
Posts: 70
|
Hi ,
On windows 20003 and MQ 6
When the user logs out , the Queue managers end .......
This dont happen on windows 2000 and MQ 5.3 ..
Has anybody seen a solution for this |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Nov 16, 2006 7:21 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
|
| Back to top |
|
|
| In_love_with_MQ |
| Posted: Thu Nov 16, 2006 7:45 am Post subject: I had seen this |
|
|
Acolyte
Joined: 10 Jul 2005
Posts: 70
|
Hi Victor ,
Yes i tried out that solution before i posted this .
I used amqmdain start QM and logged out ..
But when i logged back it showws ended immediately .
1)QMNAME(TEST3) STATUS(Ended unexpecte)
2):\Documents and Settings\sasidhv.SLTSD51.000>Amqmdain qmgr start TEST3
WebSphere MQ queue manager 'TEST3' starting.
39 log records accessed on queue manager 'TEST3' during the log replay ph
QMNAME(TEST3) STATUS(Running)
3) logoff and comeback
QMNAME(TEST3) STATUS(Ended unexpecte |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Nov 16, 2006 7:48 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
So you've satisfied yourself that the MQ Services are properly configured (as per the manual), not running as your local id & the queue manager has been set to start automatically & run independently of any user interaction?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| In_love_with_MQ |
| Posted: Thu Nov 16, 2006 8:08 am Post subject: Hi |
|
|
Acolyte
Joined: 10 Jul 2005
Posts: 70
|
| The mq services is automatic and runs as lOCAL SYSTEM acount . |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Nov 16, 2006 8:08 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
This is good. How's the queue manager set?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| In_love_with_MQ |
| Posted: Thu Nov 16, 2006 8:18 am Post subject: I CAN NOTICE A DIFFERENCE |
|
|
Acolyte
Joined: 10 Jul 2005
Posts: 70
|
Hi ,
i can see a diff between a working system and Not working system
On working system ,
amqsrvrn runs as MUSR_MQADMIN ...
On non working it runs as logged in id .
Why is it so ?
All other setting are similar...qm is auto . |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Nov 16, 2006 8:20 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Because that's how it's been set up?
This is clearly the problem - starting the queue manager as a child of a process that itself is using the logged in id is not going to resolve the problem of the queue manager ending! 
Change the user. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| In_love_with_MQ |
| Posted: Thu Nov 16, 2006 8:27 am Post subject: |
|
|
Acolyte
Joined: 10 Jul 2005
Posts: 70
|
Hi Victor ,
Sorry for this .
what do u mean by change user ..... |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Nov 16, 2006 8:31 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
On your failing system the amqsvrn process has been set to use the logged on user id - it should run as MUSR_MQADMIN
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
