| Author |
Message
|
| vinumon |
 Posted: Mon Nov 21, 2016 5:54 pm Post subject: Multi instance queuemanager failed over automatically |
 |
|
Acolyte
Joined: 06 May 2014
Posts: 59
|
| We have a qm1 running on A server and qm2 on B server..suddenly yesterday both fail over automatically..we were unale to check error log as it was overwritten.. don't know why the error logs are overwritten..there was a huge traffic of messages ..is it the reason qm got fail over?? |
|
| Back to top |
|
 |
| exerk |
| Posted: Tue Nov 22, 2016 2:55 am Post subject: Re: Multi instance queuemanager failed over automatically |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| vinumon wrote: |
| We have a qm1 running on A server and qm2 on B server..suddenly yesterday both fail over automatically.. |
Fail-over to what? qm1 to server B and qm2 to server A? What do the server logs say in regard to the fail-over? Which OS? Which version of MQ?
More information helps more targeted advice.
| vinumon wrote: |
| we were unable to check error log as it was overwritten.. don't know why the error logs are overwritten.. |
Queue manager error logs are circular by nature so what other errors (if any) are being written into those logs?
| vinumon wrote: |
| there was a huge traffic of messages ..is it the reason qm got fail over?? |
It shouldn't be, but lack of storage or other resources can have a negative impact on a queue manager.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| umatharani |
| Posted: Tue Nov 22, 2016 6:53 am Post subject: |
|
|
Apprentice
Joined: 23 Oct 2008
Posts: 39
|
If the queue manager failed over because of an error then the queue manager generates FDCs. I suggest checking for FDC files in /var/mqm/errors directory. You can also run the command ffstsummary in /var/mqm/errors directory to generate FDC summary.
Thanks,
mahesh |
|
| Back to top |
|
|
| vinumon |
| Posted: Wed Nov 23, 2016 8:22 am Post subject: |
|
|
Acolyte
Joined: 06 May 2014
Posts: 59
|
| The issue was because the SAN server was rebooted..causing qm to failover..but once qm failover the listener port of qm was running on both servers.. due to this application connectivity failed..application is connecting to qm via load balancer.. mq version is 7.5.0.0 and running on Solaris . Is this due to shared drive lock issue ..that the ports didnot get failover...? Also once application restarted they were able to connect to active instance |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Nov 23, 2016 11:37 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| vinumon wrote: |
| ...mq version is 7.5.0.0... |
Apply maintenance and check the application is coded correctly to try disconnecting and reconnecting as appropriate, and the DefRecon value in the mqclient.ini file (if being used).
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
|
|
