Author |
Message
|
Lex |
Posted: Wed Jan 10, 2007 1:25 am Post subject: Problem after a complete deploy |
|
|
 Acolyte
Joined: 14 Nov 2006 Posts: 73
|
Hi everyone!
I got the following version of the software:
MQSeries 5.3
MQ Integrator 2.1
I tried a complete deploy, but it never ends! Then i checked the queue and saw some queue as SYSTEM.AUTH.DATA.QUEUE with messages stuck in it, and i can't clear it...
I heard about a program that allows to do destructive mqget on a object being in use (which is the case of the SYSTEM.AUTH.DATA.QUEUE queue), is there any way to clear this queue or should i re install the components? (Broker with its queue manager)? |
|
Back to top |
|
 |
Vitor |
Posted: Wed Jan 10, 2007 1:37 am Post subject: Re: Problem after a complete deploy |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Lex wrote: |
I got the following version of the software:
MQSeries 5.3
MQ Integrator 2.1
should i re install the components? (Broker with its queue manager)? |
No, you should upgrade. MQSI 2.1 is out of support.
I also wouldn't a) have thought the problem was the SYSTEM.AUTH.DATA.QUEUE or that b) clearing it out was an especially good idea. But you can clear it out (if you decide you want to) with an application like amqsget - it's only the explorer that won't do it if it's in use.
Unless the queue's been opened with exclusive access obviously.
But I would think carefully, and do a little research first. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Lex |
Posted: Wed Jan 10, 2007 1:40 am Post subject: |
|
|
 Acolyte
Joined: 14 Nov 2006 Posts: 73
|
Yup i know the versions we have are out of date, but our next steps in developpement is to set a 6.0 websphere server so it'd be ok later
I just restarted the server, cause i saw that the SYSTEM.AUTH.DATA.QUEUE was set to non persistant, hope it'll change some things... |
|
Back to top |
|
 |
Vitor |
Posted: Wed Jan 10, 2007 1:43 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Lex wrote: |
I just restarted the server, cause i saw that the SYSTEM.AUTH.DATA.QUEUE was set to non persistant, hope it'll change some things... |
Do post how it goes for you. I suspect you'll find that, while the queue has default non-persistence, the messages are in fact persistant. For good and sufficient reason.
Do you have any grounds for thinking this is the problem, or have you just spotted a queue with messages in it? And if so, why do you think this particular queue should be empty? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Lex |
Posted: Wed Jan 10, 2007 2:01 am Post subject: |
|
|
 Acolyte
Joined: 14 Nov 2006 Posts: 73
|
Well after the restart, i still have the messages stuck in it.
In fact, i have 53 messages stuck in SYSTEM.AUTH.DATA.QUEUE, 2 messages stuck in SYSTEM.CLUSTER.REPOSITORY.QUEUE and 50 messages stuck in SYSTEM.CLUSTER.TRANSMIT.QUEUE.
I guess that 1 messages from the SYSTEM.AUTH.DATA.QUEUE is associated with 1 message from one of the other queue, right?
When i deployed, i waited for something like 2 hours, regularly checking the journal to see how the deployment goes, while working on something else, but after 2 hours i found it was strange that the deployment was not finished. So i did a new complete deployment, but this time a force deployment.
The deployment has never completed... So i checked the state of the queues, and saw that these queues were full and were not emptied... That's why I thought they were the little bad duck of my app. Am i wrong? |
|
Back to top |
|
 |
Vitor |
Posted: Wed Jan 10, 2007 2:05 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Lex wrote: |
Well after the restart, i still have the messages stuck in it.
In fact, i have 53 messages stuck in SYSTEM.AUTH.DATA.QUEUE, 2 messages stuck in SYSTEM.CLUSTER.REPOSITORY.QUEUE and 50 messages stuck in SYSTEM.CLUSTER.TRANSMIT.QUEUE.
I guess that 1 messages from the SYSTEM.AUTH.DATA.QUEUE is associated with 1 message from one of the other queue, right? |
I'd be rather surprised, given what those queues are used for.
Lex wrote: |
That's why I thought they were the little bad duck of my app. Am i wrong? |
I'm certainly struggling to see why these queues would cause a problem with the deploy given their use; though the 50 messages in the transmit queue would bother me for other reasons.
Have you searched (here or Google) for these queues and their uses? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Lex |
Posted: Wed Jan 10, 2007 2:08 am Post subject: |
|
|
 Acolyte
Joined: 14 Nov 2006 Posts: 73
|
I just searched about the SYSTEM.AUTH.DATA.QUEUE and saw it'd be dangerous to clear it.
I also searched how to clear a queue that is stated as an "object in use".
Since then, i can't deploy anymore, and i need to test some message flows quick, but i wanted to make it work without stopping/deleting/reinstalling the component  |
|
Back to top |
|
 |
Vitor |
Posted: Wed Jan 10, 2007 2:11 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Lex wrote: |
I just searched about the SYSTEM.AUTH.DATA.QUEUE and saw it'd be dangerous to clear it. |
I did say I didn't think it would be an especially good idea to clear it....
You should look into that cluster xmitq though - messages should not sit on that (though they do sit on the repository queue for the same reason they sit on auth.data).
Lex wrote: |
I also searched how to clear a queue that is stated as an "object in use".
Since then, i can't deploy anymore
|
Since when? What did you clear? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Lex |
Posted: Wed Jan 10, 2007 2:15 am Post subject: |
|
|
 Acolyte
Joined: 14 Nov 2006 Posts: 73
|
Vitor wrote: |
Since when? What did you clear? |
I cleared nothing, i just can't clear the object in use queue
I think i'm gonna have to reinstall the components, like that i'll have a fresh configuration. Too bad it's the only quick solution to the problem  |
|
Back to top |
|
 |
Vitor |
Posted: Wed Jan 10, 2007 2:28 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Lex wrote: |
Vitor wrote: |
Since when? What did you clear? |
I cleared nothing, i just can't clear the object in use queue
|
But none of the queues you've mentioned have anything to do with deploys, and all can (in theory) be cleared by a simple application. I wouldn't, for reasons which I hope are now clear to you, but you could. What other queue are you hoping to clear and what gives you confidence it will help?
I think you need to have a more creditable stab at diagnoising the problem before going through the whole reinstall thing. Just looking for queues with messages doesn't seem exhaustive. What else have you tried diagnosis wise? _________________ Honesty is the best policy.
Insanity is the best defence.
Last edited by Vitor on Wed Jan 10, 2007 2:30 am; edited 1 time in total |
|
Back to top |
|
 |
Mr Butcher |
Posted: Wed Jan 10, 2007 2:29 am Post subject: |
|
|
 Padawan
Joined: 23 May 2005 Posts: 1716
|
prior to reinstall you should try to find out what the problem really is. just looking over a queuemanager, picking up queues with depth and trying to clear them (without knowing what these queues are for) is not what i would call a proper investigation of a problem.
where is the deploy stuck? waiting for response? a timeout should occur. or is it stuck in creating what has to be deployed? then the queuemanager is not involved at that point in time. do you deploy using mqseries clustering (because you said you have messages in the system.cluster.transmit.queue)? if so, you should check if your mq cluster is working properly, and if the channels to the destination are up and running. anything in the logs? _________________ Regards, Butcher |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Jan 10, 2007 2:36 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
If there are messages piling up in SYSTEM.CLUSTER.TRANSMIT.QUEUE, then this means that the cluster is not working.
If the cluster is not working, then it's likely that the Configuration Manager can not send deployment messages to the Broker.
Fix the cluster!
Troubleshoot your cluster channels - what state are they in? _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
Lex |
Posted: Wed Jan 10, 2007 2:40 am Post subject: |
|
|
 Acolyte
Joined: 14 Nov 2006 Posts: 73
|
I have tried the reinstall before coming back here and... it changes nothing.
I don't know what's the proper way to investigate such a problem because as you can guess i'm a newbie on Websphere MQ (all i did actually was changing some flow for our client needs, create some queue and some other simple things like that). I am not good at resolving system problems :/
I don't know where the deploy is stuck. I didn't find any intersting log actually and so i don't have much information about the problem. I must not be searching at the right place, I hope you'd have any good suggestions for me! The only thing i know is that i don't have any return in the event journal in my control center, after i deployed.
I omited to precise one thing: our environment is set on 2 computers: the broker and it's qmgr is installed on an AIX server, and our configmgr with its qmgr is installed on a Windows server.
Hopefully, the environment i'm working on is the development environment, that's why i'm trying some strong (and surely not recommended) actions. |
|
Back to top |
|
 |
Vitor |
Posted: Wed Jan 10, 2007 2:42 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Lex wrote: |
I omited to precise one thing: our environment is set on 2 computers: the broker and it's qmgr is installed on an AIX server, and our configmgr with its qmgr is installed on a Windows server. |
If you're using 2.1 the config manager can't be elsewhere.
Following previous points, where does the cluster come into the deploy process? And why are there messages on the cluster xmitq? What's being done to fix that.
When you reinstalled, did you clear the databases down? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Lex |
Posted: Wed Jan 10, 2007 2:46 am Post subject: |
|
|
 Acolyte
Joined: 14 Nov 2006 Posts: 73
|
Yes i cleared the database, but maybe not the good one lol.
I recreated only the broker size (so i worked on the AIX part), and i deleted the queue, the broker and the tables associated with the broker then recreated them (we have a script for quickly rebuilding the broker). |
|
Back to top |
|
 |
|