Tuesday, October 9, 2001 03:52 PM
I am currently using a MessageDriven EJB that pops messages of a JMS queue and then grabs a connection from a weblogic dbpool and process it. However if the database is down, the EJB still pops off messages and then throws exceptions when trying to get the connection from the pool and the exception is logged and the message lost.
How can i architect the application so that when the db is down the messages are queued up in the JMS queue, so that when the DB comes back online they can be processed.?