| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Newbie desperate for help! QM not receiving messages |
« View previous topic :: View next topic » |
| Author |
Message
|
| PeterPotkay |
 Posted: Thu Jul 07, 2005 4:42 pm Post subject: |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| Quote: |
I can ping 204.a.b.c from QM2, but I get no response when I ping 207 from QM1 even though TO.MEMP.01 is connected?!
|
Firwall dudes can set up rules to not allow pings, but to allow other traffic. A better test to see if 1 server can get to the port where MQ is listening on is to use a telnet session. If you want to see if there is something listening on port 1414 on 123.345.56.78, you would type this from a command prompt:
| Code: |
telnet 123.345.56.78 1414
|
On Windows, if you get a blank screen in the command window, thats good, you connected, but be aware that MQ will throw a harmless FDC in this case, because the listener has no clue what the telnet format is. If you get a connection refused error, you know you can't MQ to that server/port.
It looks like QM1 cannot talk to 207.a.b.c(1414). Can you go to the server that houses QM1, and try that telnet trick to 207.a.b.c 1414? If that doesn't work ( or the reverse QM0 cant talk to QM1) that explains why QM1 does not have info on a queue housed by QM0, if QM0 and QM1 are the only FRs. It is imperative that the FRs can communicate freely with each other.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| hguapluas |
| Posted: Tue Jul 19, 2005 2:48 pm Post subject: |
|
|
Centurion
Joined: 05 Aug 2004
Posts: 105
Location: San Diego
|
And, w/firewalls, if NAT translations (or rules in general) are used, be sure that your firewall folks create the rules in both directions! I don't know how many times I've had to go back to firewall folks and say, "Hey, it works one way but not the other. Did you create the reciprocal rules?!?"
General reply: "Oh, you mean it needs to be two-way communications?!?" |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jul 19, 2005 9:16 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| hguapluas wrote: |
And, w/firewalls, if NAT translations (or rules in general) are used, be sure that your firewall folks create the rules in both directions! I don't know how many times I've had to go back to firewall folks and say, "Hey, it works one way but not the other. Did you create the reciprocal rules?!?"
General reply: "Oh, you mean it needs to be two-way communications?!?" |
Now is good time to revisit my earlier post about using DNS network setup instead of IP numbers. This will greatly help you with changing IPs and nat traversal.
Enjoy  |
|
| Back to top |
|
|
| gstephen |
| Posted: Fri Oct 14, 2005 11:34 am Post subject: |
|
|
Newbie
Joined: 16 Jun 2005
Posts: 7
Location: Toronto, Canada
|
Hi all,
I'm still having a problem with this. Mysteriously no longer getting the 2085 error, but now after examining the application log it appears that I'm receiving messages with blank/null msgid and correlid and hence why they cannot be tracked. Channels are all running, I'm getting responses back etc. No other errors in the logs either. The other QM on another machine in the cluster is still working fine as we haven't touched it. The machine in question had Solaris patches applied some time ago. You'd think there would be an error reported *somewhere*??
I'm using MQ 5.3 with JMS and Weblogic on Solaris.
Help?!
Graham |
|
| Back to top |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
