can plugged-in persistance recover after db crash?

I don't see any settings for the plugged-in persistance related to db connection pools. Is there any way for IMQ 3.5 to recover if the database crashes?

The broker just logs the following:

[10/Jun/2004:14:21:11 PDT] ERROR [B4080]: Database rollback failed.:

java.sql.SQLException: Io exception: Broken pipe

[10/Jun/2004:14:21:11 PDT] ERROR [B4004]: Failed to persist message 15-AAA.BBB.CCC.DDD(xxx)-40113-1086902471062:

java.sql.SQLException: [INSERT INTO IMQMSG35 (MID, DID, MSGSIZE, MSG) VALUES ( ?,?,?,? )]: Io exception: Broken pipe

[10/Jun/2004:14:21:11 PDT] ERROR [B2011]: Storing of JMS message from 15-AAA.BBB.CCC.DDD(xxx)-40113-1086902471062 failed:

com.sun.messaging.jmq.jmsserver.util.BrokerException: Failed to persist message 15-AAA.BBB.CCC.DDD(xxx)-40113-1086902471062

at com.sun.messaging.jmq.jmsserver.persist.jdbc.MsgTable.storeMessage(MsgTable.java:288)

at com.sun.messaging.jmq.jmsserver.persist.jdbc.JDBCStore.storeMessage(JDBCStore.java:192)

at com.sun.messaging.jmq.jmsserver.core.PacketReference.store(PacketReference.java:801)

at com.sun.messaging.jmq.jmsserver.core.Topic.routeNewMessage(Topic.java:265)

at com.sun.messaging.jmq.jmsserver.data.handlers.DataHandler.handle(DataHandler.java:146)

at com.sun.messaging.jmq.jmsserver.data.handlers.DataHandler.handle(DataHandler.java:59)

at com.sun.messaging.jmq.jmsserver.data.PacketRouter.handleMessage(PacketRouter.java:146)

at com.sun.messaging.jmq.jmsserver.service.imq.IMQConnection.readData(IMQConnection.java:1747)

at com.sun.messaging.jmq.jmsserver.service.imq.IMQConnection.process(IMQConnection.java:791)

at com.sun.messaging.jmq.jmsserver.service.imq.OperationRunnable.process(OperationRunnable.java:135)

at com.sun.messaging.jmq.jmsserver.util.pool.BasicRunnable.run(BasicRunnable.java:455)

at java.lang.Thread.run(Thread.java:534)

Caused by: java.sql.SQLException: [INSERT INTO IMQMSG35 (MID, DID, MSGSIZE, MSG) VALUES ( ?,?,?,? )]: Io exception: Broken pipe

at com.sun.messaging.jmq.jmsserver.persist.jdbc.DBManager.wrapSQLException(DBManager.java:355)

at com.sun.messaging.jmq.jmsserver.persist.jdbc.MsgTable.storeMessage(MsgTable.java:239)

... 11 more

[2298 byte] By [ZacJacobson] at [2007-11-25 17:13:56]
# 1

MQ does not currently do database connection pooling

and does not reconnect after the database server crashed.

This will be fixed in future release.

After the database/database server crashed, you need

to restart the MQ broker.

http://wwws.sun.com/software/products/message_queue/

jnakata at 2007-7-3 10:47:00 > top of Java-index,Application & Integration Servers,Sun Java System Message Queue...
# 2
Not what I was hoping to hear.Is there an interface I can fulfill to implement my own connection pooling/recovery mechanism for plugged-in persistance?
ZacJacobson at 2007-7-3 10:47:00 > top of Java-index,Application & Integration Servers,Sun Java System Message Queue...
# 3
No, no such interface available.
jnakata at 2007-7-3 10:47:00 > top of Java-index,Application & Integration Servers,Sun Java System Message Queue...
# 4
This will probably be fixed in the next release. You can trackthe status of this issue here: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4962906Chris http://wwws.sun.com/software/products/message_queue/
kasso at 2007-7-3 10:47:00 > top of Java-index,Application & Integration Servers,Sun Java System Message Queue...
# 5
I see at http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4962906 that "This bug is not available." Does that mean it's been addressed? What is the release schedule looking like for that change?
ZacJacobson at 2007-7-3 10:47:00 > top of Java-index,Application & Integration Servers,Sun Java System Message Queue...
# 6

Thanks for bringing this to our attention. Due to a configuration change to the bugtracking system none of the MQ bugs are accessible via bugs.sun.com. We will get this fixed.

A fix for the bug in question is currently being worked on, but we don't yet have a release date of when it will be available.

Joe

http://wwws.sun.com/software/products/message_queue/

jfdp at 2007-7-3 10:47:00 > top of Java-index,Application & Integration Servers,Sun Java System Message Queue...
# 7
I don't see it in the release notes, but just to verify, is this feature in 3.5 SP2?
ZacJacobson at 2007-7-3 10:47:00 > top of Java-index,Application & Integration Servers,Sun Java System Message Queue...
# 8
No, this is not fixed in 3.5 SP2. It is fixed in 3.6 which shouldbe available next quarter.Joe
jfdp at 2007-7-3 10:47:00 > top of Java-index,Application & Integration Servers,Sun Java System Message Queue...