Posted: Fri Mar 19, 2004 11:14 am Post subject: QPasa Servers loose connectivity to DB2
Newbie
Joined: 19 Mar 2004 Posts: 2
We monitor the OpenInputCount on our queues. When the count goes to zero QPasa sends out emails and pages to the MQAdmins and key Application support folk. This has been working fine for many months.
Recently the DB2 DBA's started performing weekly off-line backups of the QPasa databases. After this is done the email and pager notifications don't happen anymore. I stopped and started all four servers and that corrected everything. So we could schedule a stop and start after every off-line backup; however, when the servers come back in they send out notifications as if an event has occured yet all of the queue readers still have an OpenInputCount greater than zero.
So what is going on?
1. why doesn't QPasa reconnect to the databases when they are brought back on-line?
2. why the event notification when there is no event?
3. should I be stopping and starting the QPasa servers in a specific order?
4. is there ony one server that needs to be stopped and started rather than all three?
Posted: Fri Mar 19, 2004 1:04 pm Post subject: Q Pasa! Questions/Help for 2.3.1
Newbie
Joined: 19 Mar 2004 Posts: 1
Rich,
Please contact MQSoftware support at support@mqsoftware.com or by phone at 1-866-89Q-PASA or 1-866-897-7272. We will be happy to assist you with this issue.
Thanks,
April Hickel
MQSoftware Product Management
Posted: Wed Mar 31, 2004 1:05 pm Post subject: order of services to be started
Acolyte
Joined: 08 Mar 2003 Posts: 72 Location: Austin, TX
I don't know what version you are using.
We're using Q Pasa 3.0.0.215. This has 5 services(when you said servers I hope you meant services)
1) Security Service
2) Topic Service
3) Media Service
4) History Service
5) Event Service.
While starting the services first you need to start Security and then Topic service. Rest of them you can start in any order. To stop you should follow the reverse stop the three in any order, then Topic and then finally Security service.
We're using Oracle DB but we never had this problem. Probably you are messing the order to restart the services. Follow the correct order and see what happens.
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