ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Clustering » Does WMQ retain TCP/IP routing info anyplace?

Post new topic  Reply to topic
 Does WMQ retain TCP/IP routing info anyplace? « View previous topic :: View next topic » 
Author Message
sstubble
PostPosted: Sun Jun 03, 2007 9:48 am    Post subject: Does WMQ retain TCP/IP routing info anyplace? Reply with quote

Novice

Joined: 09 Dec 2005
Posts: 20

We have an issue where channels that have been working will no longer connect. The platforms are AIX -> Windows 2003 Server. The channels now get stuck in retrying status. AMQERR01.LOG shows AMQ9203: A configuration error for TCP/IP occurred. The return code from the TCP/IP (gethostbyname) call was 0 (X'0'). I can TCP/IP ping the hostname listed in the channel definition(s) successfully. The AIX sys admin modified the host configuration file on the AIX server and the problems started after that. He came in and restored the host file to it's previous configuration this morning but that did not resolve the problems. The channels in question are automatically and explicitly defined cluster sender channels. Thinking that cluster was hosed somehow I tried defining a static sender/receiver pair between two of the affected queue managers. No dice. Same error message. Any ideas? By the way, I saw the other post about channels stuck in retry. The connection name at both ends of the channel is exactly the same.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Sun Jun 03, 2007 11:01 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

So what you're saying...

You had a working cluster configuration.

Your AIX system administrator made networking changes.

Your cluster configuration stopped working.

Your AIX system administrator claims he has undone all the changes he made.

Your cluster configurtion still doesn't work.

And you think it's an MQ problem? It's clearly a network problem. It might not be specific to the AIX changes that were made - they may, for example, have been made to accomodate other network changes.

If you can't get new, manually defined channels to work, it's useless to play around with the cluster. Try using amqcnxc from the windows server to the AIX machine as an additional tester. And get your network admins and the AIX admin involved immediately.

The failure to gethostbyname, by the way, indicates something wrong with name resolution - either the name in your conname doesn't resolve to the thing you think it does, or it's taking too long for the name to resolve.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
sstubble
PostPosted: Sun Jun 03, 2007 11:44 am    Post subject: Reply with quote

Novice

Joined: 09 Dec 2005
Posts: 20

Nope. Don't think it's an MQ problem. I just wanted to cover all the bases. WMQ clustering can be a strange and touchy beast. I watched the AIX sysadmin make the change so I can verify that work. I think it's something the Windows sysadmin did to the DNS but I can't prove it.
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Sun Jun 03, 2007 2:43 pm    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

sstubble wrote:
WMQ clustering can be a strange and touchy beast.

In my opinion,
90% of cluster problems are plain old MQ channel problems.
99% of those problems are network problems (if the channels are properly configured to begin with, which yours apparently were).

Can you open up a telnet session from your sending machine to the port number on the receiving machine? (pings aren't always the best test as some firewalls restrict them). Kinda the same thing as using amqscnxc, but "that's an MQ program, and since your MQ is broken, it not working just proves MQ is the problem".

By showing something as basic as telnet can't make it, you can really prove your case ad get the right people looking at the right things.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
mvenu
PostPosted: Sun Jun 03, 2007 6:39 pm    Post subject: Re: Does WMQ retain TCP/IP routing info anyplace? Reply with quote

Novice

Joined: 06 May 2007
Posts: 10
Location: US

Another common mistake happens is sometimes network admin validates using ip address but turns to be hostname is used in channel definition. Make sure you validate the test with telnet/nslookup with what ever is defined in the CLUSTER CHANNEL DEFINITION ie ip address or hostname.
_________________
- Venu

- IBM Certified SOA Solution Designer
- IBM Certified System Administrator - WebSphere MQ V6
- IBM Certified Solution Designer - WebSphere MQ V6
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Clustering » Does WMQ retain TCP/IP routing info anyplace?
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.