Abstract | ||
---|---|---|
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 Existing application servers do not support this functionality The paper discusses the technical issues involved and shows how a solution can be engineered. |
Year | DOI | Venue |
---|---|---|
2006 | 10.1007/11915072_61 | OTM Workshops (2) |
Keywords | Field | DocType |
transaction manager failure,enterprise java bean component,jboss application server,transaction manager failover,backup transaction manager,transactional resource,technical issue,case study,application server,transaction manager,existing application server,distributed application,application servers,middleware,object oriented,replication,availability,fault tolerant,fault tolerance | Transaction processing,Log shipping,Computer science,Online transaction processing,X/Open XA,Microsoft Transaction Server,Distributed transaction,Nested transaction,Operating system,Database,Transaction processing system,Distributed computing | Conference |
Volume | ISSN | ISBN |
4278 | 0302-9743 | 3-540-48273-3 |
Citations | PageRank | References |
1 | 0.36 | 16 |
Authors | ||
3 |
Name | Order | Citations | PageRank |
---|---|---|---|
A. I. Kistijantoro | 1 | 1 | 0.36 |
Graham Morgan | 2 | 150 | 19.15 |
Santosh K. Shrivastava | 3 | 1185 | 188.62 |