you will have to ask your DB driver supplier to explain the com.jnetdirect.jsql.x: DBComms.transmit > exception:[java.net.SocketException error in more detail.
As far as having to restart the broker for that specific error, it would be a no, because the the clean up task is periodic and can handle failing everyone in a while. It will just pickup cleaning where it left off the next time it runs. If it fails every time, the old acked messages are not going to get propertly deleted out of your database. On Mon, May 19, 2008 at 11:49 AM, jaya_srini <[EMAIL PROTECTED]> 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-tp17321330s2354p17321330.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com
