-
1. Re: JMS unusable when DB is unavailable at JBoss startup
genman Feb 1, 2006 10:04 PM (in response to kwinterm)
JMS won't come up if the DB isn't available, true.
But you can use the start operation on the MBean to start the service that failed, likely the DestinationManager. You could write a service that could try to start the service every 10 seconds or something. -
2. Re: JMS unusable when DB is unavailable at JBoss startup
kwinterm Feb 1, 2006 11:51 PM (in response to kwinterm)Thank you genman, but as I wrote, trying to start any services with MBeans under "jboss.mq" has no effect. I have to redeploy JMS or restart the server.
-
3. Re: JMS unusable when DB is unavailable at JBoss startup
kwinterm Feb 2, 2006 8:46 AM (in response to kwinterm)OK, now I got it: So I need to invoke
- destroy
- create
- start
on both the PersistenceManager and the StateManager. Then everything is back to normal.
But wouldn't it be a lot easier if the JMS services could connect themselves automatically to the database when it becomes available? Why is the number of retry attempts limited in PersistenceManager.getConnection()?
Cheers, Karsten -
4. Re: JMS unusable when DB is unavailable at JBoss startup
adrian.brock Feb 2, 2006 12:01 PM (in response to kwinterm)"kwinterm" wrote:
Why is the number of retry attempts limited in PersistenceManager.getConnection()?
That code shouldn't even be there. It is only there to workaround
the stupid way that hypersonic starts.
http://jira.jboss.com/jira/browse/JBAS-1942 -
5. Re: JMS unusable when DB is unavailable at JBoss startup
adrian.brock Feb 2, 2006 12:03 PM (in response to kwinterm)Failure monitoring/recovery belongs in the mangement layer not the implementation.