Toggle Main Menu Toggle Search

Open Access padlockePrints

Transaction Manager Failover: A Case Study Using JBOSS Application Server

Lookup NU author(s): Achmad Kistijantoro, Professor Graham MorganORCiD, Emeritus Professor Santosh Shrivastava



The extension of object-oriented middleware to component-oriented middleware is now commonplace, with many distributed applications structured as remote clients invoking services constructed from components. An advantage components offer over objects is that only the business logic of an application needs to be addressed by a programmer. An application server hosts components, managing supporting services to provide the execution environment for components. A transaction manager within an application server assumes responsibility for managing the execution of transactions. Failure of an application server instance could result in abortion of ongoing transactions that are being managed by the transaction manager on that server. This paper describes, for the case of Enterprise Java Bean components and JBoss application server, how replication for availability can be supported to tolerate application server/transaction manager failures. Replicating the state associated with the progression of a transaction (i.e., which phase of two-phase commit is enacted and the transactional resources involved) provides an opportunity to continue a transaction using a backup transaction manager if the transaction manager of the primary fails.

Publication metadata

Author(s): Kistijantoro AI, Morgan G, Shrivastava SK

Publication type: Report

Publication status: Published

Series Title: School of Computing Science Technical Report Series

Year: 2006

Pages: 22

Print publication date: 01/07/2006

Source Publication Date: July 2006

Report Number: 975

Institution: School of Computing Science, University of Newcastle upon Tyne

Place Published: Newcastle upon Tyne