Author |
Message
|
Subash |
Posted: Sat May 14, 2005 12:56 pm Post subject: CHANNEL NOT ACTIVE - STILL RETRYING |
|
|
Newbie
Joined: 14 May 2005 Posts: 4
|
I had set up a channel between two local queue managers. The listener is setup in the right port, but then the Sender Channel is still retrying. I am not able to ping the channel. Netstat shows that the port is listening.
Help needed . |
|
Back to top |
|
 |
vennela |
Posted: Sat May 14, 2005 2:21 pm Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
Is the listener running on the QMGR where the RCVR channel is defined or on the QMGR where the SDR is defined?
Posting your channel definitions might help.
What do you see in the error logs? (If Windows, eventvwr should be a good place to look for) |
|
Back to top |
|
 |
Subash |
Posted: Sun May 15, 2005 6:44 am Post subject: CHANNEL NOT ACTIVE - STILL RETRYING |
|
|
Newbie
Joined: 14 May 2005 Posts: 4
|
The listener is running in both the queue managers. The error log in the event viewer mentions that an TCP/IP error has occured with number 10038(X2736) and another error of 10054(X2736). All the definitions and port numbers are perfect.
??? |
|
Back to top |
|
 |
csmith28 |
Posted: Sun May 15, 2005 8:41 am Post subject: |
|
|
 Grand Master
Joined: 15 Jul 2003 Posts: 1196 Location: Arizona
|
10038 = Socket operation on non-socket.
10054 = Connection reset by Peer.
Make sure the Listeners are using the same port. _________________ Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
Back to top |
|
 |
EddieA |
Posted: Sun May 15, 2005 10:19 am Post subject: |
|
|
 Jedi
Joined: 28 Jun 2001 Posts: 2453 Location: Los Angeles
|
What platform, version, CSD level.
Are you seeing errors in both logs, or just the sender. If the answer is both, and this is Windows, you could try setting an environment variable MQNOREMPOOL=1 and reboot.
Cheers, _________________ Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
Back to top |
|
 |
Subash |
Posted: Sun May 15, 2005 4:04 pm Post subject: CHANNEL NOT ACTIVE - STILL RETRYING |
|
|
Newbie
Joined: 14 May 2005 Posts: 4
|
EDDIE. THANKS FOR REPLYING . I DON;T KNOW HOW TO SET THE MQNOREMPOOL=1 ? N BY THE WAY WAT IS THAT ? HOW DOES IT AFFECT THE CHANNEL OR THE LISTENER ? KINDLY HELP ME.
THANK YOU. |
|
Back to top |
|
 |
kevinf2349 |
Posted: Sun May 15, 2005 7:55 pm Post subject: |
|
|
 Grand Master
Joined: 28 Feb 2003 Posts: 1311 Location: USA
|
|
Back to top |
|
 |
Subash |
Posted: Mon May 23, 2005 4:41 am Post subject: CHANNEL NOT ACTIVE - STILL RETRYING |
|
|
Newbie
Joined: 14 May 2005 Posts: 4
|
I tried everything. I even added the port to the exception in the windows firewall, I set the envrionment variable MENOREMPOOL=1. I did that in the command prompt. But still the channel is retrying and not pinging. What would be problem and how to resolve it ?? Kindly give the solution as I am not able to send any messages. |
|
Back to top |
|
 |
jefflowrey |
Posted: Mon May 23, 2005 4:45 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
You need to look at logs on both sides.
If the receiver channel is not running, then the sender channel will never be able to start.
Are you using the MQ ping, or the standard ping command? If you are using the standard ping, then you will see errors in the logs about TCP/IP problems. This would not be the problem with the channel.
Stop both channels. Manually start the receiver channel and look for errors in it's logs. Manually start the sender channel - and look for errors. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
EddieA |
Posted: Mon May 23, 2005 8:16 am Post subject: |
|
|
 Jedi
Joined: 28 Jun 2001 Posts: 2453 Location: Los Angeles
|
Quote: |
I set the envrionment variable MENOREMPOOL=1. I did that in the command prompt |
Then it had no effect. This must be set as a system variable, followed by a re-boot.
Cheers, _________________ Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
Back to top |
|
 |
|