| Author |
Message
|
| poulter90 |
 Posted: Tue Apr 15, 2008 1:33 am Post subject: Impossible to start channel after Xmit queue became full |
 |
|
Apprentice
Joined: 31 Dec 2007
Posts: 36
|
Hi All ,
I am running MQSeries Version 6 on UNIX HP itanium :
Memory = 8171 MB (7.979492 GB)
Firmware info:
Firmware revision = 01.01
FP SWA driver revision: 1.18
IPMI is supported on this system.
ERROR: Unable to obtain manageability firmware revision info.
Platform info:
model string = "ia64 hp server BL860c"
machine id number = 115ecff5-58f8-11dc-be55-2c0d7d7bd422
machine serial number = GB8730NB7B
OS info:
sysname = HP-UX
nodename = hic1h01
release = B.11.23
version = U (unlimited-user license)
machine = ia64
idnumber = 0291426293
vmunix _release_version:
@(#) $Revision: vmunix: B11.23_LR FLAVOR=perf Fri Aug 29 22:35:38 PDT 2003 $
Because my Xmit queue attached to my sender channel has become full
on a process , channel went on retrying mode .
I have tried to reset ,resolve and start channel but it is still saying
MQOPEN FAILED .
I have listed all processes supposed to be running on my xmit queue but list is empty . It seems that xmit queue is still used by a process
as I am receiving a 2042 error code.
Any idea to unlock and release my xmit queue ?
Apart from restarting my QManager which is nonsense in a Production environment !
Thanks , Francis |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Tue Apr 15, 2008 1:52 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Mods Please move this MQ Section:
did you check the IPPROCS and OPPROCS
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Apr 15, 2008 2:27 am Post subject: Re: Impossible to start channel after Xmit queue became ful |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| poulter90 wrote: |
Because my Xmit queue attached to my sender channel has become full
on a process , channel went on retrying mode .
I have tried to reset ,resolve and start channel but it is still saying
MQOPEN FAILED .
|
What happens when you explicitly stop it?
And please try to pick a more appropraite section for your posts..... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Apr 15, 2008 2:49 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| poulter90 wrote: |
Because my Xmit queue attached to my sender channel has become full
on a process , channel went on retrying mode .
I have tried to reset ,resolve and start channel but it is still saying
MQOPEN FAILED . |
This is entirely the wrong troubleshooting attitude.
Your channel did not go into retrying because the xmitq is full.
The xmitq is full because your channel is in retry mode.
You must first determine why your channel is not working.
Try looking at the qmgr error logs (/var/mqm/qmgrs/<qmgr>/error)
Check if you can create a telnet session from the sending box to the receiving box on the mq port.
Is your channel referencing the right xmitq?
Enjoy reading the intercommunications manual  
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| poulter90 |
| Posted: Tue Apr 15, 2008 3:55 am Post subject: |
|
|
Apprentice
Joined: 31 Dec 2007
Posts: 36
|
Could not reach any informations in the Log .
Cannot start my channel because my Xmit queue is in used (2042 error)
How to release an xmit queue from a process ?
Any command ?
Thanks |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Apr 15, 2008 4:07 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| poulter90 wrote: |
| Could not reach any informations in the Log . |
Why? Do you not have read permissions against the directory? The mqm id should have, and if it hasn't that's a problem.
| poulter90 wrote: |
| Cannot start my channel because my Xmit queue is in used (2042 error) |
Again I ask what happens when you stop it? There is a difference between a channel that won't start, and a channel that's stopped.
| poulter90 wrote: |
| How to release an xmit queue from a process ? |
A good way is to stop the channel - see my comment above! Another way is to check the IPPROCS & OPPROCS as suggested earlier
| poulter90 wrote: |
| Any command ? |
Aside from the stop channel? No. The xmitq is only a queue with a particular usage & some special rights. You detach processes from it in the traditional ways, like stopping the process using it.
And I agree with fjb_saper - the xmitq filled because the channel stopped working. I suspect you have an old/crashed MCA still holding a handle on the queue & causing this problem, but you still need to investigate the underlying problem which caused the queue to fill!
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| poulter90 |
| Posted: Tue Apr 15, 2008 4:23 am Post subject: |
|
|
Apprentice
Joined: 31 Dec 2007
Posts: 36
|
Hi ,
When I said "cannot access the log " means I cannot go backwards enough to see the problem which hoccurred during the night .
Due to high activity , a lot of messages are filling the AMQERR01/02/03.LOG and informations are out of bounds !
When I saw my sender channel retrying , I stopped it and it was fine .
My xmit queue was full , so I increased the size .
Then I tried to start the channel , but it said MQOPEN FAILED ,
That's why I suspected my xmit queue was still attached to a process.
AS you said " I suspect you have an old/crashed MCA still holding a handle on the queue & causing this problem"
I will investigate , also what do you mean by "check the IPPROCS & OPPROCS"
Anything to see with ipcs command ?
I am not an expert in UNIX !
Thanks |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Apr 15, 2008 4:29 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
The IPPROCS and OPPROCS show the number of processes have the queue open for input (which in the case of a TXQ should be the channel process), and what has the queue open for output.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Apr 15, 2008 4:43 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| poulter90 wrote: |
I will investigate , also what do you mean by "check the IPPROCS & OPPROCS"
Anything to see with ipcs command ?
|
No, they're queue attibutes visible through runmqsc. This is not rocket science MQ.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| poulter90 |
| Posted: Tue Apr 15, 2008 4:49 am Post subject: |
|
|
Apprentice
Joined: 31 Dec 2007
Posts: 36
|
Hi ,
I found interesting documentation on IBM site
http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.csqzal.doc/fg17940_.htm
The Connect sample program allows you to explore the MQCONNX call and its options from a client. The sample connects to the queue manager using the MQCONNX call, inquires about the name of the queue manager using the MQINQ call, and displays it.
Have you heard about a sample program which closes a queue
(in term of abending existing process attached to it ?)
I was thinking it may have helped in my case
Regards |
|
| Back to top |
|
|
| poulter90 |
| Posted: Tue Apr 15, 2008 4:55 am Post subject: |
|
|
Apprentice
Joined: 31 Dec 2007
Posts: 36
|
| OK exerg but where to find The IPPROCS and OPPROCS ? |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Apr 15, 2008 4:59 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| poulter90 wrote: |
Have you heard about a sample program which closes a queue
(in term of abending existing process attached to it ?)
|
You can't "close" a queue. Any application you run will open it's own handle, and close it when it's finished. If it's well behaved and closes normally.
The only thing you could do to "close" the queue is to disable both gets & puts on the xmitq. This would, in theory, cause any connected application to abend & disconnect.
In your instance, I suspect the connected application is already abended, or so far gone that a simple thing like not being able to use it's queue no longer bothers it. Far more effective to locate the process and terminate it as discussed above.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Apr 15, 2008 5:00 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| poulter90 wrote: |
| OK exerg but where to find The IPPROCS and OPPROCS ? |
| Vitor wrote: |
| they're queue attibutes visible through runmqsc |
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| poulter90 |
| Posted: Tue Apr 15, 2008 5:14 am Post subject: |
|
|
Apprentice
Joined: 31 Dec 2007
Posts: 36
|
|
| Back to top |
|
|
| poulter90 |
| Posted: Tue Apr 15, 2008 5:57 am Post subject: |
|
|
Apprentice
Joined: 31 Dec 2007
Posts: 36
|
Hi ,
As you can see IPPROCS and OPPROCS values
But I can't determine the process still enqueuing
Display Queue details.
QUEUE(CSQ3) TYPE(QLOCAL)
ACCTQ(QMGR) ALTDATE(2008-04-15)
ALTTIME(15.22.0 BOQNAME( )
BOTHRESH(0) CLUSNL( )
CLUSTER( ) CLWLPRTY(0)
CLWLRANK(0) CLWLUSEQ(QMGR)
CRDATE(2008-02-19) CRTIME(14.15.22)
CURDEPTH(8132) DEFBIND(OPEN)
DEFPRTY(0) DEFPSIST(YES)
DEFSOPT(SHARED) DEFTYPE(PREDEFINED)
DESCR(XMITQ CSQ3) DISTL(NO)
GET(DISABLED) HARDENBO
INITQ(SYSTEM.CHANNEL.INITQ) IPPROCS(1)
MAXDEPTH(10000) MAXMSGL(4194304)
MONQ(QMGR) MSGDLVSQ(FIFO)
TRIGGER NPMCLASS(NORMAL)
OPPROCS(1) PROCESS( )
PUT(ENABLED) QDEPTHHI(80)
QDEPTHLO(20) QDPHIEV(DISABLED)
QDPLOEV(DISABLED) QDPMAXEV(ENABLED)
QSVCIEV(NONE) QSVCINT(999999999)
RETINTVL(999999999) SCOPE(QMGR)
SHARE STATQ(QMGR)
TRIGDATA(QMINT.CSQ3) TRIGDPTH(1)
TRIGMPRI(0) TRIGTYPE(FIRST)
USAGE(XMITQ) |
|
| Back to top |
|
|
|
|
