| Author |
Message
|
| ajith_rajan |
 Posted: Fri Sep 05, 2003 7:53 am Post subject: Not able to start the Cluster Sender Channel |
 |
|
Apprentice
Joined: 05 Sep 2003
Posts: 32
|
Hi
I am facing the following problem. Please help me out in resolving this.
I have a unix box in which I had successfully installed the MQ series and verified. I need to create three Q Managers, of which two Q Managers are part of the cluster.
I had made the necessary changes to the inetd.conf and the services.conf file as well to enable the TCP/IP tranmission.
There are totally two cluster sender channels in these three QManagers.
I am able to successfully start the cluster sender channel in the first QManager. But I am not able to start the cluster sender in the second QManager. Its giving the following error.
-----------------------------------------------------------------
09/05/03 12:48:44
AMQ9203: A configuration error for TCP/IP occurred.
-----------------------------------------------------------------
I had properly edited the inetd.conf and the services file and also has rebooted the unix box itself and has also verified that the inetd service is running.
Is there any thing else I need to do.
Please help.
Regards
Ajith |
|
| Back to top |
|
 |
| vennela |
| Posted: Fri Sep 05, 2003 8:48 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Ajith:
Is the listener running for the other Queue Manager?
How did you verify this.
Have you specified different port numbers?
Can you start an ordinary SDR channel to the other Queue Manager ?
-------
Venny |
|
| Back to top |
|
|
| ajith_rajan |
| Posted: Fri Sep 05, 2003 8:53 am Post subject: |
|
|
Apprentice
Joined: 05 Sep 2003
Posts: 32
|
Yes, I am able to start the individual sender channels.
The Port numbers in which the queue managers needs to be listening is given in the inetd.conf and the services file. They are listening in different port numbers (First QMngr --> 1414, Second QMngr --> 1415, Third QMngr --> 1416).
The inet service is also running.
The Listener programs are running and also I am able to start the sender channels. Apart from this, I am also able to start one cluster sender channel in the first queue manager.
The Only problem is I am not able to start the cluster sender channel in the second QManager.
Any clue of what's happening??
TIA
Ajith |
|
| Back to top |
|
|
| mrlinux |
| Posted: Fri Sep 05, 2003 8:59 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
I would look at the cluster sender channel definition where this message
was produced
AMQ9203: A configuration error for TCP/IP occurred.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| vennela |
| Posted: Fri Sep 05, 2003 9:04 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Ajith:
Maybe your clussdr and clusrcvr definitions may be wrong.
On QMGR1 verify you have a clusrcvr channel
dis chl(*) chltype(clusrcvr) all
This should return a clusrcvr channel coming to QMGR1 with a conname having port 1414
Also on QMGR2
dis chl(*) chltype(clussdr) all
Verify the channel name and port number again. This channel name should be same as the above one.
-------
Venny |
|
| Back to top |
|
|
| ajith_rajan |
| Posted: Fri Sep 05, 2003 9:07 am Post subject: |
|
|
Apprentice
Joined: 05 Sep 2003
Posts: 32
|
Please find the channel definitions as below.
Cluster sender channel definition in First QMgr. --> Successfully started
----------------------------------------------
define channel (TO.LMUKQMNGR1) +
chltype(CLUSSDR) TRPTYPE(tcp) +
conname(‘137.46.225.85(1415)') +
cluster(GATEWAYCLUSTER)
Cluster receiver channel definition in First QMgr
-------------------------------------------------
define channel (TO.LMUKGATEWAYQMNGR) +
chltype(CLUSRCVR) TRPTYPE(tcp) +
conname(‘137.46.225.85((1414)') +
cluster(GATEWAYCLUSTER)
Cluster Sender Channel in Second QMngr --> Giving Configuration Error while starting.
------------------------------------------------
define channel (TO.LMUKGATEWAYQMNGR) +
chltype(CLUSSDR) TRPTYPE(tcp) +
conname(‘137.46.225.85(1414)') +
cluster(GATEWAYCLUSTER)
Cluster Receiver Channel in Second QMngr
-------------------------------------------------
define channel (TO.LMUKQMNGR1) +
chltype(CLUSRCVR) TRPTYPE(tcp) +
conname(‘137.46.225.85(1415)') +
cluster(GATEWAYCLUSTER)
Rgds
Ajith |
|
| Back to top |
|
|
| vennela |
| Posted: Fri Sep 05, 2003 9:19 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
The channel definitions look good but I would rather display them using runmqsc to make sure the definitions are what I think they are.
What does the error logs say.
Look at the error logs in the second queue manager and see what they say when you try to start a SDR channel. |
|
| Back to top |
|
|
| ajith_rajan |
| Posted: Fri Sep 05, 2003 9:19 am Post subject: |
|
|
Apprentice
Joined: 05 Sep 2003
Posts: 32
|
| Every thing was fine, as you said. |
|
| Back to top |
|
|
| ajith_rajan |
| Posted: Fri Sep 05, 2003 9:23 am Post subject: |
|
|
Apprentice
Joined: 05 Sep 2003
Posts: 32
|
There is no message logged in the error file while starting the sender channel. It starts successfully.
I am also able to start the cluster sender channel in the first QM connecting to port 1415.
The following is the error message logged while trying to start the cluster sender channel in the second Queue Manager connecting to the first one listening in port number 1414.
09/05/03 17:10:04
AMQ9203: A configuration error for TCP/IP occurred.
EXPLANATION:
Error in configuration for communications to host '137.46.225.85'. Allocation
of a TCP/IP conversation to host '137.46.225.85' was not possible.
ACTION:
The configuration error may be one of the following:
1.If the communications protocol is LU 6.2, it may be that one of the
transmission parameters (Mode, or TP Name) is incorrect. Correct the error
and try again. The mode name should be the same as the mode defined on host
'137.46.225.85'. The TP name on '137.46.225.85' should be defined.
2.If the communications protocol is LU 6.2, it may be that an LU 6.2 session
has not been established. Contact your systems administrator.
3.If the communications protocol is TCP/IP, it may be that the host name
specified is incorrect. Correct the error and try again.
4.If the communications protocol is TCP/IP, it may be that the host name
specified cannot be resolved to a network address. The host name may not be
in the nameserver.
The return code from the TCP/IP (connect) call was 126 (X'7E').
Record the error values and tell the system administrator.
Regards
Ajith |
|
| Back to top |
|
|
| ajith_rajan |
| Posted: Fri Sep 05, 2003 9:29 am Post subject: |
|
|
Apprentice
Joined: 05 Sep 2003
Posts: 32
|
I personally feel this should be some problem with the TCP/IP communication enabling.
I dont see anything wrong with the channel definitions.
One more interesting stuff is that when I create the MQ objects and then start the channel for the first time, it works fine. All channels starts fine.
But on stopping the channels and starting it once again gives problem in starting only that particular cluster sender channel in the second QMngr.
Any Clues. |
|
| Back to top |
|
|
| mrlinux |
| Posted: Fri Sep 05, 2003 10:50 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Shouldnt both of your cluster sender channels be pointing at the same
Cluster Repository box ???? o
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| GMcCarthy |
| Posted: Tue Sep 09, 2003 4:20 am Post subject: |
|
|
Centurion
Joined: 06 Nov 2001
Posts: 113
Location: Melville NY
|
Silly question....did you type in those definitions for this forum or are you defining exactly as they are seen here? Because you have a double left parenthesis..
conname(‘137.46.225.85((1414)') +
Since the conname is taken from the receiver on cluster channels...this may be your problem. 
_________________
Regards,
Gina
IBM Certified MQSeries Specialist |
|
| Back to top |
|
|
| Leafar |
| Posted: Tue Sep 09, 2003 5:45 am Post subject: |
|
|
Acolyte
Joined: 03 Apr 2003
Posts: 74
Location: Buenos Aires
|
Try doing
telnet 137.46.225.85 1414 (and the others ports) to see if the listener is normally running
Saludos
Rafael |
|
| Back to top |
|
|
|
|
