In order to maintain an acid transaction across resouce managers you really
need resource managers which support XA or another 2PC protocol. So, if you
databases cannot act as a 2PC resource manager, then you will need some
server infront of them which can act.
In a traditional sense, I would normally consider my EJB container as the
transaction manager, and my databases as my resouce managers. IF the
database cannot be, I will need to either use another server product in
front of my database, or place another ejb server in front of each database.
Very few application servers today can act as 2PC transaction managers. The
only ones I am aware of are <VENDOR> Sybase EAServer </VENDOR> as well as
iPlanet 6 and <BLECK>MTS</BLECK>.
Dave Wolf
Internet Applications Division
Sybase
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Amine Belouali
> Sent: Monday, September 11, 2000 11:19 AM
> To: [EMAIL PROTECTED]
> Subject: EJB and the two phase commit
>
>
> Hi all,
>
> In the case we have an EJB wich call more than two Ressource
> Managers and each one of them don't support the two phase commit
> (2 JDBCs for examlpe); what is the best way to have a
> transactional behaviour in the whole?
>
> many thanks for any help
> Amine
>
> ==================================================================
> =========
> To unsubscribe, send email to [EMAIL PROTECTED] and include
> in the body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
>
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
