| Author |
Message
|
| dkoushik |
 Posted: Mon Aug 21, 2006 10:19 am Post subject: Sender channel does not start automatically |
 |
|
Novice
Joined: 08 Aug 2006
Posts: 16
|
I have configured MQ with Microsoft Hardware clustering between 2 nodes - Test1 and Test2.
Configuration seems to be sucessfull because when I initiate a failover , MQ Server in Test1 stops and MQ Server in Test2 starts automatically and vice versa. After the failover I have tested if I can put the messages in que, browse, delete quueue, message, etc. everything seems to be working fine in both the nodes.
But I am facing one issue, when the failover occurs the sender channels never starts automatically in the nodes where the MQ server comes up even though the receiver channel is in listening mode in other system.
disconnect interval is set to zero (0) for all the sender channels, still i had to start the sender channel manualy. As a reason one of my application is failed to start up because that is depending on the MQ channels.
Please, suggest whats going wrong...
Thanks |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Aug 21, 2006 10:30 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Did you configure transmit queues for triggering?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| dkoushik |
| Posted: Mon Aug 21, 2006 10:34 am Post subject: |
|
|
Novice
Joined: 08 Aug 2006
Posts: 16
|
Yes. transmit queue is configured for the other system.
I could start the sender channel manually from MQ Explorer in Test2 node. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Aug 21, 2006 10:47 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Please post the definition of the sender channel and the definition of the xmitq.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| dkoushik |
| Posted: Mon Aug 21, 2006 10:59 am Post subject: |
|
|
Novice
Joined: 08 Aug 2006
Posts: 16
|
QM_PM4CLUSTER - Queue Maneger in MSCS clustered Node
QM_112 - Queue Manager in external system to whom node will send messages
Sender Channel properties:
=================
display channel(PM4CLUSTER_TO_ENT)
1 : display channel(PM4CLUSTER_TO_ENT)
AMQ8414: Display Channel details.
CHANNEL(PM4CLUSTER_TO_ENT) CHLTYPE(SDR)
ALTDATE(2006-08-21) ALTTIME(11.50.43)
BATCHHB(0) BATCHINT(0)
BATCHSZ(50) COMPHDR(NONE)
COMPMSG(NONE) CONNAME(10.29.126.110)
CONVERT(NO) DESCR( )
DISCINT(0) HBINT(300)
KAINT(AUTO) LOCLADDR( )
LONGRTY(999999999) LONGTMR(1200)
MAXMSGL(4194304) MCANAME( )
MCATYPE(PROCESS) MCAUSER( )
MODENAME( ) MONCHL(QMGR)
MSGDATA( ) MSGEXIT( )
NPMSPEED(FAST) PASSWORD( )
RCVDATA( ) RCVEXIT( )
SCYDATA( ) SCYEXIT( )
SENDDATA( ) SENDEXIT( )
SEQWRAP(999999999) SHORTRTY(10)
SHORTTMR(60) SSLCIPH( )
SSLPEER( ) STATCHL(QMGR)
TPNAME( ) TRPTYPE(TCP)
USERID( ) XMITQ(QM_112)
Transmit Queue Properties
=================
display channel(PM4CLUSTER_TO_ENT)
1 : display channel(PM4CLUSTER_TO_ENT)
AMQ8414: Display Channel details.
CHANNEL(PM4CLUSTER_TO_ENT) CHLTYPE(SDR)
ALTDATE(2006-08-21) ALTTIME(11.50.43)
BATCHHB(0) BATCHINT(0)
BATCHSZ(50) COMPHDR(NONE)
COMPMSG(NONE) CONNAME(10.29.126.110)
CONVERT(NO) DESCR( )
DISCINT(0) HBINT(300)
KAINT(AUTO) LOCLADDR( )
LONGRTY(999999999) LONGTMR(1200)
MAXMSGL(4194304) MCANAME( )
MCATYPE(PROCESS) MCAUSER( )
MODENAME( ) MONCHL(QMGR)
MSGDATA( ) MSGEXIT( )
NPMSPEED(FAST) PASSWORD( )
RCVDATA( ) RCVEXIT( )
SCYDATA( ) SCYEXIT( )
SENDDATA( ) SENDEXIT( )
SEQWRAP(999999999) SHORTRTY(10)
SHORTTMR(60) SSLCIPH( )
SSLPEER( ) STATCHL(QMGR)
TPNAME( ) TRPTYPE(TCP)
USERID( ) XMITQ(QM_112)
Let me know if i need to provide anything else.
Thanks.[/img] |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Aug 21, 2006 11:02 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| dkoushik wrote: |
Transmit Queue Properties
=================
display channel(PM4CLUSTER_TO_ENT)
|
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| dkoushik |
| Posted: Mon Aug 21, 2006 11:14 am Post subject: |
|
|
Novice
Joined: 08 Aug 2006
Posts: 16
|
sorry my bad...
here is the transmit queue defination.
display qlocal(QM_112)
2 : display qlocal(QM_112)
AMQ8409: Display Queue details.
QUEUE(QM_112) TYPE(QLOCAL)
ACCTQ(QMGR) ALTDATE(2006-08-21)
ALTTIME(11.34.00) BOQNAME( )
BOTHRESH(0) CLUSNL( )
CLUSTER( ) CLWLPRTY(0)
CLWLRANK(0) CLWLUSEQ(QMGR)
CRDATE(2006-08-1 CRTIME(10.17.37)
CURDEPTH(0) DEFBIND(OPEN)
DEFPRTY(0) DEFPSIST(NO)
DEFSOPT(SHARED) DEFTYPE(PREDEFINED)
DESCR( ) DISTL(YES)
GET(ENABLED) HARDENBO
INITQ( ) IPPROCS(0)
MAXDEPTH(5000) MAXMSGL(4194304)
MONQ(QMGR) MSGDLVSQ(PRIORITY)
TRIGGER NPMCLASS(NORMAL)
OPPROCS(0) 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( ) TRIGDPTH(1)
TRIGMPRI(0) TRIGTYPE(FIRST)
USAGE(XMITQ)
Thanks |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Aug 21, 2006 11:21 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
INITQ(SYSTEM.CHANNEL.INITQ)
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Aug 21, 2006 11:21 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
INITQ(SYSTEM.CHANNEL.INITQ)
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| dkoushik |
| Posted: Mon Aug 21, 2006 12:10 pm Post subject: |
|
|
Novice
Joined: 08 Aug 2006
Posts: 16
|
I have altered the Transmit Queue property.
INITQ(SYSTEM.CHANNEL.INITQ)
Restatred the Queue Manager but the sender channel didn't start automatically. I had to start that manually. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Aug 21, 2006 12:16 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It won't start until something needs to get sent.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| dkoushik |
| Posted: Mon Aug 21, 2006 12:53 pm Post subject: |
|
|
Novice
Joined: 08 Aug 2006
Posts: 16
|
I understand and also checked the approach u mentioned. Its working whenever I tried to send something.
But still thats does not solve my problem. The application properly starts whenevr sender and receiver channels are up and running.
I am not sure how to acheive that. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Aug 21, 2006 1:01 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The application shouldn't notice these things. It's probably written wrong.
There's no way to configure a channel to start when the queue manager starts, without a script... You can configure a simple shell script as a service under queue manager control.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Tue Aug 22, 2006 12:10 am Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
| jefflowrey wrote: |
The application shouldn't notice these things. It's probably written wrong.
There's no way to configure a channel to start when the queue manager starts, without a script... You can configure a simple shell script as a service under queue manager control. |
You could do another trick:
- set the DISCINT to 0 -> then the channel never stops
- restart the QMgr, which hosts the sender channel -> when the channel was active before, MQ should start the channel again.
_________________
Regards
Hubert |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Aug 22, 2006 12:20 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| HubertKleinmanns wrote: |
- set the DISCINT to 0 -> then the channel never stops
|
IHMO that's not an optimal solution, as it can cause problems if (when!) the network has issues....
As always jefflowrey has made the valid point (Hail the PooBah!). dkoushik application should start if the channel is up, down or sliding sideways. Having got the chanel into a triggered state, the correct course of action is to investigate what's up with the app.
Probably in a new thread.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
