| Author |
Message
|
| jeevan |
 Posted: Tue Mar 24, 2009 2:49 pm Post subject: MQ on VM server have connection problem |
 |
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
Hey folks
We are having an unique problem in our production MQ occassionally. We have 2 physical servers and 4 vm servers running on ESX 3.5. during the last one year, we have 3 or 4 instances that we observed all connections going to 2 physical boxes. When we checked the virtual servers, MQ is up and running and log is clean.
The physical and vm servers are in different subnets. However, there has not observed any problem in overall vm servers according to our windows folks.
We are clueless. We can not reproduce the problem as we do not know what is causing it.
Had any of you have any issues with MQ 6.0.2..2 on VM servers? |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Mar 25, 2009 1:43 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
More details are needed.
All connections from WHAT to WHAT are only going to the physical machines rather than the VMs?
What is the MQ topology? |
|
| Back to top |
|
|
| jeevan |
| Posted: Wed Mar 25, 2009 12:36 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| mqjeff wrote: |
More details are needed.
All connections from WHAT to WHAT are only going to the physical machines rather than the VMs?
What is the MQ topology? |
All connection from the clients go to physical servers.
What is why we thought whether there is some issues with 6.0.2.2? as I said earlier, when it happens, the connections stops going to all vm servers. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Mar 25, 2009 12:44 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
MQ Client application connections go to the physical address rather than the virtual address?
External business client queue manager connections go to the physical address rather than the virtual address?
What is the MQ topology?
What is the network topology? How are connection end points being resolved? DNS? |
|
| Back to top |
|
|
| jeevan |
| Posted: Wed Mar 25, 2009 2:05 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| mqjeff wrote: |
MQ Client application connections go to the physical address rather than the virtual address?
External business client queue manager connections go to the physical address rather than the virtual address?
What is the MQ topology?
What is the network topology? How are connection end points being resolved? DNS? |
around 12000 clients can connect to any of the 6 queue managers. In normal day, the connections to each queue manager is around 2000-2300. When this problem happens, which happens about 3 times upto now, no clients go to queue manager on virtual servers.
As I said, earlier, among the 6 qmgrs, 4 of them are in vm servers and 2 in physical servers. |
|
| Back to top |
|
|
| ramires |
| Posted: Wed Mar 25, 2009 3:33 pm Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
| And the problem is... ? Ahah THE PROBLEM! |
|
| Back to top |
|
|
| jeevan |
| Posted: Thu Mar 26, 2009 8:46 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| ramires wrote: |
| And the problem is... ? Ahah THE PROBLEM! |
pls read my first post.
occassionally, all connection request from cleints go to 2 physical servers while qmgrs on the other 4 vm servers are also up and running and chanels are not full. we want to resolve why this happens? |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Mar 26, 2009 8:55 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| 4 vm servers are also up and running and chanels are not full |
Are you saying that the 4 vmware qmgrs continue to process non-client (local) connections, but not the client connections? What does not full mean to you?
As a test, log on to a vmware qmgr and run a client-connection utility (like amqsputc) to see if the client-connection works locally.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| ramires |
| Posted: Thu Mar 26, 2009 9:04 am Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
you have 6 qmgrs, each one with his own ip address? How the clients decide which queue manager to use? Are a load balancer between the clients and the server? Error logs on client side?
what do you do to solve the problem? |
|
| Back to top |
|
|
| jeevan |
| Posted: Thu Mar 26, 2009 9:54 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| ramires wrote: |
you have 6 qmgrs, each one with his own ip address? How the clients decide which queue manager to use? Are a load balancer between the clients and the server? Error logs on client side?
what do you do to solve the problem? |
client uses a configuratino file with all queue manager name and a random generator decides which queue manager does it connect to. Also, when i can not connect in 5 go, it blacklists the queue manager and does not try to connect until the register is rebooted.
When we got an alarms ( this is not immediately, but after some time when the connection in physical boxes reaches certain numbers. When we then look at the qmgr in vmware, I found ( always) working and the log is clean ( no any sort of error nor any fdc files are generatoe). So we thought probably more of an issuew with vmware. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Mar 26, 2009 11:03 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Did the client configuration app blacklist the vmware qmgrs? Does it report when (date/time) it blacklists a qmgr?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| jeevan |
| Posted: Thu Mar 26, 2009 11:19 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| bruce2359 wrote: |
| Did the client configuration app blacklist the vmware qmgrs? Does it report when (date/time) it blacklists a qmgr? |
we are collecting the information from client side exactly how it blacklist a queue manager. But again, we are focusing more on why all connections stop going to vmware at once.
One queue manager can be blacklisted for some reason but not all and all qmgr on vm servers. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Mar 26, 2009 11:26 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| One queue manager can be blacklisted for some reason but not all and all qmgr on vm servers. |
From your description this is apparently what has happened.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| jeevan |
| Posted: Thu Mar 26, 2009 11:45 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| bruce2359 wrote: |
| Quote: |
| One queue manager can be blacklisted for some reason but not all and all qmgr on vm servers. |
From your description this is apparently what has happened. |
yes. The clients stop connecting to qmgrs on vmware at once. All connections go to physical boxes. |
|
| Back to top |
|
|
|
|
