Hi
Thanks for all the replies.
I got a fair idea of things. Just to make it more clear I will elaborate my
earlier query
1. Scenario 1
Two weblogic servers
Session bean on server 1 talks directly to session bean on server 2
Both session beans have database updates(same database on Oracle).
In this case I assume that the transactional context is propagated
to server2
So if the update on one of the servers fails both are rolled
back-right?
Does this hold true in Weblogic 5.1 irrespective of whether the
database supports XA or not. (I think Oracle supports XA, but i am asking
this question from a database portablity view)?
what about weblogic 6.0 regarding the same issue(ie; how is the
behaviour if the database is not supporting XA).
2. Scenario 2
Two weblogic servers
Session bean on server 1 communinates via RMI to a RMIServer on
server2 which in turn communicates to a session bean on server 2. There is a
firewall between the two servers allowing only specific requests to go
through.
In this case is the transactional context passed between the two
servers?
What happens if there is a network failure after server2 updates the
database?
How should the server1 handle it?
Do we have to do some explicit transcation handling mechasim in our
code(JTA/JTS)
I am a little confused on this issue
I hope somebody can throw more light on this.
Regards
Anup
-----Original Message-----
From: Rob Woollen [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 10, 2000 4:17 AM
To: [EMAIL PROTECTED]
Subject: Re: Two Phase commit
<vendor>
I asked our JTA team for their answer on this one. Here's what they
said:
In WebLogic Server our JDBC/RMI driver funnels database requests from
multiple servers over the same database connection. As long as only
one database is participating in the transaction, we don't incur any
two-phase commit overhead. Also, the database does not need to support
XA.
In WebLogic Server 6.0 if the database does support XA, we can call
its JDBC driver directly from multiple servers. WebLogic's
transaction manager implements what's called a "one phase"
optimization: if there's only one XA resource participating in the
transaction, we don't run the two-phase commit protocol, and we don't
write a commit record to disk.
</vendor>
-- Rob
Rob Woollen
Sr Software Engineer
BEA WebLogic
[EMAIL PROTECTED]
This e-mail and any files transmitted with it are for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply e-mail and
destroy all copies of the original message.
Any unauthorised review, use, disclosure, dissemination, forwarding, printing or
copying of this email or any action taken in reliance on this e-mail is strictly
prohibited and may be unlawful.
Visit us at http://www.cognizant.com
===========================================================================
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".
