you can ensure that your MQ listener only attachs to the virtual IP.
Then you don't have to worry about apps connecting to the wrong address, you only have to worry about app developers complaining that MQ must be broken because they can't connect to the physical address.
A more single handled version of what I was suggesting.
I would tend to use "correct" rather than "single handed". the clear point of the VIP is to ensure that the listener is available at a fixed and known location regardless of which machine the qmgr is running on. So there's no reason to make any other option available.
Thanks mqjeff. Vitor for your valueable inputs and giving the insight what falls under MQAdmin responsibility.
I will try to figure it out from netstat command.
I understand that even if Queue manager listener is running on vip the client apps which are using physical ip are able to connect this QM, not sure how the network works internally to resolve that!!! .
The problem only arises when the QM gets fail over on the another physical ip with same vip.
I understand that even if Queue manager listener is running on vip the client apps which are using physical ip are able to connect this QM, not sure how the network works internally to resolve that!!! .
The problem only arises when the QM gets fail over on the another physical ip with same vip.
The listener by default will listen to all network addresses on the machine.
You can configure it to listen to a specific network address, rather than just a specific port number.
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