if the backend database is the same, that DB will handle your transactions according to your transaction level. if you want to handle the transactions by JTA/JTS then you need a system that implements distributed transactions, and that will not have a pleasant effect on your performance :)
Filip ----- Original Message ----- From: "Jignesh Patel" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Monday, August 02, 2004 6:09 PM Subject: RE: concurrency management No Yoav, My question is different. By using UserTransaction class I can get the control on transaction which is being executed on one server. But what if we are having two different tomcat server with two different machine mapped by one load balancer. In this type of situation what to be done, since the other server is not aware that what transaction going on to one server. -Jignesh On Mon, 2004-08-02 at 09:20, Shapira, Yoav wrote: > Hi, > If two users are on the app at the same time, both accessing the > database at the same time, and both have write privileges to the same > data, you are responsible for synchronization to suit your goals. This > might mean no sync at all, meaning a simple race. That's not > necessarily a bad thing, it depends on your app. Many people think a > race condition is always a bad thing, and it's not. > > If your application requires transactions, you will need to download the > JTA (you can get it by itself from java.sun.com, don't download the > whole J2EE jar) and an implementation thereof, e.g. Tyrex or JOTM, and > code your app to use it. You can do this within Tomcat without going to > JBoss or another full-fledged J2EE server. However, again depending on > your sync requirements and surrounding architecture, you might want to > get a full J2EE server which would have JTA support built-in. > > BTW, JOTM is an excellent product, we use in production and like it. > > Yoav Shapira > Millennium Research Informatics > > > >-----Original Message----- > >From: Jignesh Patel [mailto:[EMAIL PROTECTED] > >Sent: Saturday, July 31, 2004 1:09 PM > >To: [EMAIL PROTECTED] > >Subject: Re: concurrency management > > > >On Sat, 2004-07-31 at 11:47, Jignesh Patel wrote: > >> Hi V. > >> > >> Here is my question again. > >> > >> -Jignesh > >> On Fri, 2004-07-30 at 13:00, Vic Cekvenich wrote: > >> > The connection pools and data sources are more of a container > question, > >> > since you are using Tomcat ask on Tomcat list, and I will follow up > >there. > >> > > >> > .V > >> > > >> > Jignesh Patel wrote: > >> > > Hi, > >> > > How do we will manage concurrency if suppose we have connection > pool > >> > > which is managed with struts1.1 on tomcat. > >> > > > >> > > > >> > > And then we have two we server now suppose two connection from > two > >> > > server try to access the database at the same time. How we can > >handle? > >> > > > >> > > I know from my previous posting connection pool is thread safe if > it > >one > >> > > JVM but what in the case of two JVM. > >> > > > >> > > -Jignesh > >> > > >> > > >> > > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: [EMAIL PROTECTED] > >> > For additional commands, e-mail: [EMAIL PROTECTED] > >> > > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > This e-mail, including any attachments, is a confidential business communication, > and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
