Forgot to ask this in my previous post...after the connection is restablished will the broker be able to continue without a restart or will we need to restart the broker every time there is a network issue like this?
thanks jaya jaya_srini wrote: > > Hello > > We are using ActiveMQ 5.0.0 and the JDBCPersistenceAdapter. From time to > time we see the following message in the logs > > [Q Cleanup Timer] WARN JDBCPersistenceAdapter - Old message > cleanup failed due to: com.jnetdirect.jsql.x: DBComms.transmit > exception:[java.net.SocketException: Connection reset by peer: socket > write error] context:[(3) [Thread[ActiveMQ Cleanup Timer,5,main], > IO:caedd, Dbc:3941]]] > > Does this mean there is a network blip between the box that has the broker > and the box that has the database and the broker can't connect to the > database? Or does this happen in other circumstances i.e when a specific > number of messages have been stored in DB or some other reason? > > We are using SQLServer 2005 > > > thanks > jaya > -- View this message in context: http://www.nabble.com/Database-connection-between-ActiveMQ-and-broker-tp17321330s2354p17322812.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
