| Author |
Message
|
| Gorki |
 Posted: Thu Mar 02, 2006 10:45 am Post subject: Channel initiator initiate nothing [Resolved] |
 |
|
Newbie
Joined: 02 Mar 2006
Posts: 5
|
Hi,
I set up a configuration in cluster with 4 servers
S1, S2 -> Windows based servers
A1, A2 -> AIX based servers
There is channel defined explicitly:
S1->S2
S2->S1
A1->A2
A2->A1
S1->A1
S1->A2
S2->A1
S2->A2
I know i don't normally need so much, but it doesn't matter.
All is running perfectly when my channels from S* to A* are running. But when they come inactive the channel initiator (which is running) doesn' restart them.
- there is no global error log
- there is no system error log
- there is only the normal deactivation messages for the channel from S* -> A*
So, I don' see any activation message for the channels.
Another problem maybe related : the channels takes up to 5 mn from S*->A* to becomes running they are initializing during this time. No performance problems noted afterthat.
My questions are :
- how to control that channel initiator wants to start the channels
- can we have more traces ?
- is the slow startup can prevent channel initiator to display its messages ?
If you can help 
I can also put some configuration stuff if you wants. But S and A are in different networks, there is no login / password on the channels, the configuration is the default one and we checked that it is the same on the 4 servers.
Thx !
S.
Last edited by Gorki on Fri Mar 03, 2006 7:52 am; edited 1 time in total |
|
| Back to top |
|
 |
| wschutz |
| Posted: Thu Mar 02, 2006 10:50 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Are you saying that you have setup the channels to be triggered, messages arrive on the xmitq, and then the channels aren't being triggered (started)?
Also, is your conname a IP address or a host name..sometimes lazy DNS servers can slow down IP address resolution.....
_________________
-wayne |
|
| Back to top |
|
|
| Nigelg |
| Posted: Thu Mar 02, 2006 1:17 pm Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
Are these cluster channels? if so, the normal channel triggering techniques do not apply, i.e. xmitq atributes INITQ TRIGGER TRIGTYPE.
At MQPUT to a cluster queue the qmgr starts cluster channels from INACTIVE.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| Gorki |
| Posted: Fri Mar 03, 2006 12:30 am Post subject: |
|
|
Newbie
Joined: 02 Mar 2006
Posts: 5
|
| Quote: |
Are you saying that you have setup the channels to be triggered, messages arrive on the xmitq, and then the channels aren't being triggered (started)?
Also, is your conname a IP address or a host name..sometimes lazy DNS servers can slow down IP address resolution.....
|
Yes the channels don't seem to be triggered when new messages arrive.
We use IP and no DNS name.
| Quote: |
Are these cluster channels? if so, the normal channel triggering techniques do not apply, i.e. xmitq atributes INITQ TRIGGER TRIGTYPE.
At MQPUT to a cluster queue the qmgr starts cluster channels from INACTIVE. |
Yes, this is cluster channels. I maybe made a mistake in xmitq attributes.
The channels are inactive and are not becoming running
I will check the channel triggering techniques in this case. |
|
| Back to top |
|
|
| Gorki |
| Posted: Fri Mar 03, 2006 12:58 am Post subject: |
|
|
Newbie
Joined: 02 Mar 2006
Posts: 5
|
I have a doubt....
We defined a local queue :
S1.QL.CHINIT
just with :
DEFINE QLOCAL (S1.QL.CHINIT)
for the queue manager S1
and afterthat we start the channel initiator with :
amqmdain crtchi S1 S1.QL.CHINIT
Is it the right way to do it ? |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Fri Mar 03, 2006 4:29 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
does not look too bad on a first view.
how did you set up your xmitqs for channel tringgering?
_________________
Regards, Butcher |
|
| Back to top |
|
|
| Gorki |
| Posted: Fri Mar 03, 2006 7:51 am Post subject: |
|
|
Newbie
Joined: 02 Mar 2006
Posts: 5
|
I resolve my problem !!
The channel initiator was checking the queue S1.QL.CHINIT, but as this is a cluster, the channel initiator MUST listen :
SYSTEM.CHANNEL.INITQ
Once I modified this, restart the CI, all works perfertly, channels come up in a few seconds, and are restarted when deactivated.
Thanks for all your help, it really give me a clue to resolve this. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Mar 03, 2006 7:55 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You should not have needed to create the channel initiator, or change any setup of an existing one.
Did you forget to set the CLUSTER name on your cluster channels?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Gorki |
| Posted: Fri Mar 03, 2006 8:03 am Post subject: |
|
|
Newbie
Joined: 02 Mar 2006
Posts: 5
|
No, the channels had the cluster_name correctly configured.
But, we configured explicitely a channel initiator, maybe it was the error ? |
|
| Back to top |
|
|
| wschutz |
| Posted: Fri Mar 03, 2006 10:51 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Gorki wrote: |
No, the channels had the cluster_name correctly configured.
But, we configured explicitely a channel initiator, maybe it was the error ? |
To repeat what Nigel said earlier:
| Quote: |
Are these cluster channels? if so, the normal channel triggering techniques do not apply, i.e. xmitq atributes INITQ TRIGGER TRIGTYPE.
|
You must not define triggering on the cluster xmit queue...
_________________
-wayne |
|
| Back to top |
|
|
|
|
