| Author |
Message
|
| uherbst |
 Posted: Fri Jul 30, 2004 12:20 am Post subject: Automatic Channel restart doesn't work |
 |
|
Newbie
Joined: 30 Jul 2004
Posts: 5
|
I want to automatically restart a channel after an inactivity timeout.
I read the MQS-FAQ and the IBM Documentation.
I tried:
- alter ql(xmitqueue) trigdata(channelname)
- alter ql(xmitqueue) trigger trigdata(channelname) initq(system.channel.initq)
- alter ql(xmitqueue) trigger process(processname) initq(system.channel.initq) and define process(processname) userdata(channelname).
After starting the Channel Initiator (either with runmqchi or with start chinit) and putting a message to the remote queue, I get this message always in the dead letter queue.
The reason code in the dlq is MQFB_TM_ERROR.
What can I do about that ?
Uli |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Jul 30, 2004 5:20 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Uli,
We need some more info:
Environment (OS)
Version (mqver)
Triggertype(should be FIRST)
Thanks |
|
| Back to top |
|
|
| uherbst |
| Posted: Fri Jul 30, 2004 5:35 am Post subject: |
|
|
Newbie
Joined: 30 Jul 2004
Posts: 5
|
Your're right.
OS: Linux (RedHat ES 2.1)
mqver:
Name: WebSphere MQ
Version: 530
CMVC level: p000-L021011
BuildType: IKAP - (Production)
Details about transmit queue:
1 : dis ql(JDAX0.XMITQ)
AMQ8409: Display Queue details.
DESCR(Transmit-Queue zum JDAX-QMGR) PROCESS(JDAX0XMITQ)
BOQNAME( ) INITQ(SYSTEM.CHANNEL.INITQ)
TRIGDATA(MQVAFP.XJGJDAX0) CLUSTER( )
CLUSNL( ) QUEUE(JDAX0.XMITQ)
CRDATE(2004-07-26) CRTIME(12.56.55)
ALTDATE(2004-07-30) ALTTIME(10.32.5
GET(DISABLED) PUT(ENABLED)
DEFPRTY(0) DEFPSIST(NO)
MAXDEPTH(5000) MAXMSGL(4194304)
BOTHRESH(0) SHARE
DEFSOPT(SHARED) HARDENBO
MSGDLVSQ(PRIORITY) RETINTVL(999999999)
USAGE(XMITQ) TRIGGER
TRIGTYPE(FIRST) TRIGDPTH(1)
TRIGMPRI(0) QDEPTHHI(80)
QDEPTHLO(20) QDPMAXEV(ENABLED)
QDPHIEV(DISABLED) QDPLOEV(DISABLED)
QSVCINT(999999999) QSVCIEV(NONE)
DISTL(YES) DEFTYPE(PREDEFINED)
TYPE(QLOCAL) SCOPE(QMGR)
DEFBIND(OPEN) IPPROCS(0)
OPPROCS(0) CURDEPTH(0) |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Jul 30, 2004 12:30 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
For starters, get the info out of the PROCESS parameter of the XMITQ. At the current version of MQ, you only need the channel name in the TRIGGERDATA field. You do not need the PROCESS def.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jul 30, 2004 8:41 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
For seconds I believe that you will need to set it to get(enabled)
This changes typically when you stop the channel as well as the trigger attribute. But I have seldom seen a channel running when the xmit queue had get(disabled)
As Peter stated with your version you do not need any process info. Neither do you need any trigdata info unless you have more than one channel using this xmit queue. Your info shows you at base level. You might want to try and apply the latest patch (CSD07).
Hope this helps.
F.J.  |
|
| Back to top |
|
|
| uherbst |
| Posted: Tue Aug 03, 2004 3:16 am Post subject: |
|
|
Newbie
Joined: 30 Jul 2004
Posts: 5
|
OK, I got the problem:
After upgrading to CSD7, everything went smooth (even with trigdata and process defined).
And it went smoot without trigdata and process defined, too 
Thank you.
Uli |
|
| Back to top |
|
|
|
|
