| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Client App connect fails when ip address (not hostname) chan |
« View previous topic :: View next topic » |
| Author |
Message
|
| PeterPotkay |
 Posted: Fri Apr 26, 2002 12:00 pm Post subject: |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Java App on a server. This UNIX server has the MQ Client installed only. It client connects to our MQServer (hostname ABC, ip address of 123). JavaApp has been running for a week without being restarted. It has the MQEnvironment.hostname value coded as ABC, and has been working correctly.
Server ABC is now moved to a new machine. Its hostname stays the same, ABC, but its ip address changes to 456. JavaApp now fails. Not until the instance of the app is bounced does it finally connect to ABC (456). How come?
It's like the old ip address for ABC, 123, was cached somewhere, and not until the app was bounced did it realize that ABC(123) was now ABC(456).
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| kolban |
| Posted: Fri Apr 26, 2002 4:17 pm Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
| Interesting ... I would say that caching the IP address of a DNS name should be fair game. Ideally, I would hope that the code internally detects a connection failure resulting from a cached name and tries a new DNS lookup before failing completely. It is an expensive process looking up a DNS name to resolve the IP address and can forgive MQ for caching. Remember, DNS names (THE identity of the box) should not change on server machines. Client machines with DHCP, now that is a different story but servers usually don't travel that far. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
