1 Reply Latest reply on Apr 2, 2007 3:03 AM by Ronald van Kuijk

    Transaction commit fail (network down)

    William Power Newbie

      I am working on a system that needs to update a web service (WS) and a database (DB) within a single transaction. Since the WS is non transactional, I make an update to the DB first, then make a call to the WS; if the WS succeeds the DB update is committed (DBC).

      Details:

      Client makes a call to a stateless session bean. The ssb uses container managed transactions.
      The session bean updates an entity bean.
      The session bean then makes a call to the web service.

      This approach works well except in the following scenario: If there is a network problem during DBC the WS and DB get out of sync.

      Does anyone know if it is possible to configure JBoss to continue to retry the DBC in the event of a network problem?