For fail over concept, does developer needs to do any special coding in his components. I know the answer is no but when i was going through one of BEA Weblogic examples he implemented client code in such a way that if the transaction fails he will attempt the transaction again with the same information(now it is on different server in a clustered environment). In this case he is not maintaing transaction state on more that one server, am i correct. I believe if we do set up same environment to take care of Session for fail over, it will work good for transactions also, am i correct. Please correct me if i am wrong and let me know how to accomplish the same.
Thanks,
Srinivas Gamini
-
Fail Over concept regarding Transaction management (1 messages)
- Posted by: Srini gams
- Posted on: October 07 2001 11:31 EDT
Threaded Messages (1)
- Fail Over concept regarding Transaction management by Venkat Subramani on October 07 2001 21:57 EDT
-
Fail Over concept regarding Transaction management[ Go to top ]
- Posted by: Venkat Subramani
- Posted on: October 07 2001 21:57 EDT
- in response to Srini gams
Can your post the client code here mentioning what
exactly he did.
I agree with you that application need not do any special
coding for failover as it should be taken care of by
the underneath transport mechanism of EJB and should
be totally transparent.