| Author |
Message
|
| cmkeller |
 Posted: Tue Jul 10, 2007 2:53 pm Post subject: Sender Channel stays in "Binding" |
 |
|
Apprentice
Joined: 09 Jan 2005
Posts: 41
Location: Queens, NY
|
I can't figure out what's wrong here - I have a Sender Channel on a Windows XP Pro workstation running Websphere MQ 6.0, and a Receiver Channel on another Windows XP Pro woskstation running Websphere MQ 5.3, with FixPack 12 installed. They have the same name. When I attempt to start the Sender Channel, it stays in "Binding", but the Receiver Channel is nicely in status "Running."
I checked my Windows Firewall, and it is configured to let incoming MQSeries through on Port 1414, which is definitely the relevant port for this Queue Manager.
There are no error messages in the Windows Event Viewer on either the sender or receiver machine. I see no error messages in any log files, either; the last message is "Channel (sender channel name) is Starting."
My only guess is that perhaps the machine with the Receiver Channel doesn't know the IP address toward which to direct messages back to the Sender Channel - but does that make sense, if it received the data? I will say that the two machines connect via a VPN, so the IP address of the machine with the Sender Channel varies from connection to connection - could that be the problem here?
_________________
Chaim Mattis Keller
Shadow Financial Services Corp
ckeller@shadowfinancial.com |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Tue Jul 10, 2007 3:09 pm Post subject: |
|
|
Guest
|
Can you IP ping from the senders ipaddress to the receivers ipaddress and port?
Do you have a listener on the receiving end?
Can you telnet from the sender to the receiver?
Did you successfully MQ PING from the sender channel to the receiver channel? |
|
| Back to top |
|
|
| cmkeller |
| Posted: Tue Jul 10, 2007 5:56 pm Post subject: |
|
|
Apprentice
Joined: 09 Jan 2005
Posts: 41
Location: Queens, NY
|
I can definitely IP ping the receiver address from the sender machine, but I'm not sure how I'd ping the specific port.
I don't see anything called "listener" in MQSeries Explorer on the receiver side (which, you might recall, is running 5.3). The only place I see the word listener is in the MQSeries Explorer for 6.0 running on the Sender machine. If there is such a thing as a listener in 5.3, how do I see it?
I can't telnet from the sender to the receiver.
When I right-click on the Sender Channel in MQSeries Explorer and select "Ping", I get error AMQ4054, Channel In Use.
_________________
Chaim Mattis Keller
Shadow Financial Services Corp
ckeller@shadowfinancial.com |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Tue Jul 10, 2007 6:35 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Hi
Try to push some datas through the channels...
Lets see if you are getting any errors or not...
Thanks and regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| cmkeller |
| Posted: Tue Jul 10, 2007 7:25 pm Post subject: |
|
|
Apprentice
Joined: 09 Jan 2005
Posts: 41
Location: Queens, NY
|
I created a remote queue on the sender side with the local being on the receiver side, and the transmission queue is the same as that used by the sender channel. Then I put a message on the remote queue. Result: The message is sitting on the transmission queue.
_________________
Chaim Mattis Keller
Shadow Financial Services Corp
ckeller@shadowfinancial.com |
|
| Back to top |
|
|
| cheanfeiy |
| Posted: Tue Jul 10, 2007 7:36 pm Post subject: |
|
|
Apprentice
Joined: 21 Jun 2003
Posts: 26
|
cmkeller wrote:
| Quote: |
If there is such a thing as a listener in 5.3, how do I see it?
|
In MQ 5.3, you can find the listener in the WebSphere MQ Services snap-in.
cmkeller wrote:
| Quote: |
When I right-click on the Sender Channel in MQSeries Explorer and select "Ping", I get error AMQ4054, Channel In Use.
|
In order to ping a channel, the sender channel must in stopped status. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jul 11, 2007 12:45 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| cmkeller wrote: |
I can't telnet from the sender to the receiver.
|
If you can't telnet then the channel can't connect. 
You've got network issues. You say there's a VPN in use which modifies IP addresses by session; does the channel use host names or IP addresses? In this (and most) situations it's better to quote a hostname and let the network later resolve the routing.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| cmkeller |
| Posted: Wed Jul 11, 2007 6:03 am Post subject: |
|
|
Apprentice
Joined: 09 Jan 2005
Posts: 41
Location: Queens, NY
|
That doesn't make sense, because I also can't telnet (just tried) between other machines which have perfectly fine channels running between them.
_________________
Chaim Mattis Keller
Shadow Financial Services Corp
ckeller@shadowfinancial.com |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Jul 11, 2007 6:06 am Post subject: |
|
|
Guest
|
| Try this: on the receiver end open a c: prompt; start a listener manually runmqlsr -t tcp -p portaddressgoeshere -m qmgrnamegoeshere. Then try to telnet. |
|
| Back to top |
|
|
| cmkeller |
| Posted: Wed Jul 11, 2007 6:25 am Post subject: |
|
|
Apprentice
Joined: 09 Jan 2005
Posts: 41
Location: Queens, NY
|
OK, I just figured out what was wrong with my telnetting - I wasn't specifying the 1414 port.
I can telnet fine into the receiver machine using port 1414. And on top of that, I used the MQ services snap-in and confirmed that there is a listener running on the receiver side.
The MQPing I have a real problem with. When I try it fron the Sender Channel, the Command Server doesn't respond in a timely manner, and then EVERYTHING stops responding - MQSeries Explorer won't let me see lists of Channels or Queues (always that message that the Command Server isn't responding in time), and if I close Explorer and re-open it, it re-opens with my Queue Manager disconnected. In that state, the "Quick Status View" says the queue manager and the command server are both running, but I can't Connect - again, because the Command Server won't respond. (I have to assume it's somehow totally hung up on that MQPing, but why? I mean, if the Ping failed, it should just fail and go back to responding to other commands normally, shouldn't it?)
_________________
Chaim Mattis Keller
Shadow Financial Services Corp
ckeller@shadowfinancial.com |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Jul 11, 2007 6:55 am Post subject: |
|
|
Guest
|
| It sounds like the path back from the qmgr your are trying to manage with Explorer isn't running. Thus, the 'not responding' message. Next check your receiver channel. Is it in running state? |
|
| Back to top |
|
|
| cmkeller |
| Posted: Wed Jul 11, 2007 6:57 am Post subject: |
|
|
Apprentice
Joined: 09 Jan 2005
Posts: 41
Location: Queens, NY
|
Yes, the receiver channel is in running state. That was one of the first things I checked.
_________________
Chaim Mattis Keller
Shadow Financial Services Corp
ckeller@shadowfinancial.com |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Jul 11, 2007 7:03 am Post subject: |
|
|
Guest
|
| On the qmgr you are trying to manage, any errors logged? at the qmgr level? at the mq level? |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jul 11, 2007 7:05 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| cmkeller wrote: |
| I can telnet fine into the receiver machine using port 1414. |
Sorry about that - sort of assumed you were telneting to the MQ port as has been described in this forum upteen times. 
Should have been clearer. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| cmkeller |
| Posted: Wed Jul 11, 2007 7:35 am Post subject: |
|
|
Apprentice
Joined: 09 Jan 2005
Posts: 41
Location: Queens, NY
|
No errors logged on the Sender side (where I'm having the explorer trouble). The MQ error log file just has warnings of when my trial version expires. The Queue Manager error log file just tells me that various processes have started, the latest one being the Channel Initiator.
On the receiver side, I just found the following errors, which I would not be surprised to discover is related to my problem. This one is from the general MQ Error log:
| Quote: |
7/11/2007 10:15:00
AMQ9207: The data received from host '10.10.11.116' is not valid.
EXPLANATION:
Incorrect data format received from host '10.10.11.116' over TCP/IP. It may be
that an unknown host is attempting to send data. An FFST file has been
generated containing the invalid data received.
ACTION:
Tell the systems administrator.
----- amqxfdcp.c : 631 --------------------------------------------------------
7/11/2007 10:15:00
AMQ6183: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 2568.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcp.c : 671 --------------------------------------------------------
|
and these are from the Queue Manager error log:
| Quote: |
7/11/2007 10:15:49
AMQ9209: Connection to host 'CMKELLER_LAPTOP (10.10.11.116)' closed.
EXPLANATION:
An error occurred receiving data from 'CMKELLER_LAPTOP (10.10.11.116)' over
TCP/IP. The connection to the remote host has unexpectedly terminated.
ACTION:
Tell the systems administrator.
----- amqccita.c : 2741 -------------------------------------------------------
7/11/2007 10:15:49
AMQ9228: The TCP/IP responder program could not be started.
EXPLANATION:
An attempt was made to start an instance of the responder program, but the
program was rejected.
ACTION:
The failure could be because either the subsystem has not been started (in this
case you should start the subsystem), or there are too many programs waiting
(in this case you should try to start the responder program later). The reason
code was 0.
----- amqrmrsa.c : 461 --------------------------------------------------------
|
Could this ("invalid data format") be because the Sender is on version 6.0 and the receiver on 5.3? Is 5.3 not recognizing some 6.0 data sent with the Start Channel command?
Does this shed any light?
_________________
Chaim Mattis Keller
Shadow Financial Services Corp
ckeller@shadowfinancial.com |
|
| Back to top |
|
|
|
|
