| Author |
Message
|
| jefflowrey |
 Posted: Thu Aug 25, 2005 12:51 pm Post subject: |
 |
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| mangoMan wrote: |
| Could it be that WAS is running a queue manager? |
Dspmq would show this queue manager, if there was one.
Also, you would see multiple occurances of some of the mq processes that are unique per qm... so if you see more than one occurance of every amq* process, then there is more than one qm (and still, dspmq would show that!).
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Aug 25, 2005 1:11 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20763
Location: LI,NY
|
Jeff,
Would dspmq still show it while WAS is down or would it only show it while WAS is up?
What if he gave the WAS qmgr the same name as the WMQ qmgr ?
Sorry just having a nightmarish scenario here.  |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Aug 25, 2005 2:53 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| fjb_saper wrote: |
| Would dspmq still show it while WAS is down or would it only show it while WAS is up? |
It would show it while it was down.
| fjb_saper wrote: |
| What if he gave the WAS qmgr the same name as the WMQ qmgr ? |
This would be somewhat difficult to do.
I am not 100% sure, but I believe that it is not possible to create two queue managers with the same name using crtmqm - and as we have previously established, createMQ.sh runs crtmqm.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Aug 25, 2005 5:40 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
| I am not 100% sure, but I believe that it is not possible to create two queue managers with the same name using crtmqm |
Why not 100% sure? If a qmgr exists in mqs.ini, how can you create another one with the same name?
_________________
-wayne |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Aug 25, 2005 7:14 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20763
Location: LI,NY
|
Because both directories are not the same.
WAS MQ directory typically is somewhere under WAS ROOT
WMQ directory typically is somewhere under WMQ Install.
Now if they don't clash in the registry there is really nothing from keeping you from creating 2 qmgrs with the same name one in WAS and one in WMQ.
However there is no guarantee that either one would run as expected should both be up at the same time....or even that you can have both up at the same time....
What I would expect to be much more common is to have the same spelling but difference in the case for the qmgrs ...
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Aug 26, 2005 3:08 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| wschutz wrote: |
| Why not 100% sure? |
Cause my memory is faulty... 
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Aug 26, 2005 3:10 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| fjb_saper wrote: |
Because both directories are not the same.
WAS MQ directory typically is somewhere under WAS ROOT
WMQ directory typically is somewhere under WMQ Install. |
Even the embedded messaging really ends up putting stuff in /var/mqm/ and /usr/mqm on Unix. And on Windows, of course, there is only one Registry. This doesn't change things.
| fjb_saper wrote: |
| What I would expect to be much more common is to have the same spelling but difference in the case for the qmgrs ... |
That, yeah. But, again, dspmq would show you that. And it doesn't in this case.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| hopsala |
| Posted: Fri Aug 26, 2005 12:02 pm Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
OK, so considering the fact that
| mangoMan wrote: |
| I keep getting a 2033 even when I delete the queue. |
and that
| jefflowrey wrote: |
| mangoMan wrote: |
| Could it be that WAS is running a queue manager? |
Dspmq would show this queue manager, if there was one. |
I think we can safely assume that mangoMan is simply opening the wrong queue...
mangoMan - I suggest you simply trace the value of "_inQueueName" variable. I also restate my suggestion concerning some translation done by WAS for the queue name, be it JNDI names or something else.
There's a really easy way to check this - MQPUT to queue instead of MQGET, and search for a queue that changed depth... (remember to stop all SDRs and applications first) |
|
| Back to top |
|
|
| hopsala |
| Posted: Fri Aug 26, 2005 3:22 pm Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
Hm, just thought of something else - it's odd but it's the only solution I can think of that fits all patterns of behavior you told us about, i.e:
1. putting "" in qmgrname returns 2033
2. putting "PROD13" in qmgrname returns 2058
3. using "" after the queue (!) returns 2033
4. only one qm appears on dspmq - PROD13
so assuming Jeff's assertion that WASs internal qm appears in dspmqaut list is true (I don't know myself) there is only one solution here: You are using a client connection to another QM on a remote machine.
When using client connection with MQSERVER variable, if you specify a wrong QM name you get 2058, and if you specify a null string, you connect successfully. This also explains getting 2033 after deleting the queue - its the right queue name on the wrong qm.
A good way to check this would be to issue MQINQ for the qmgrname in your code.
Let us know what's going on, i'm curious  |
|
| Back to top |
|
|
|
|
