also, check if there are timeout options on the com.ibm.db2.jcc.DB2Driver w.r.t connections or if there is a keepalive option in commons pooling that will discard an expired connection.
My assumption is that the database connections in the pool are getting stale in some way. 2009/4/9 Dejan Bosanac <[email protected]> > Hi, > > there is a lot of db2 specific exceptions in your log, so it looks like the > broker loses the connection to the database (and/or cannot obtain the > lock). > If your connection to the database is unstable, maybe you can consider amq > persistance store instead? > > Cheers > -- > Dejan Bosanac > > Open Source Integration - http://fusesource.com/ > ActiveMQ in Action - http://www.manning.com/snyder/ > Blog - http://www.nighttale.net > > > On Thu, Apr 9, 2009 at 11:13 AM, Raj_New <[email protected]> wrote: > > > > > I know my above message is really lenthy....Sorry but I need answer for > > this > > behaviour of AMQ...why its work fine for couple of days and then suddenly > > breaks down. > > > > > > > > -- > > View this message in context: > > > http://www.nabble.com/Embedded-Broker-shuts-down-automatically-AMQ5.2-tp22965564p22967169.html > > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > > > > -- http://blog.garytully.com Open Source SOA http://FUSESource.com
