 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Tomcat - JSP/Servlet container | | Struts - A MVC web framework | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | JSP - A mailing list about Java Server Pages specification and reference | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | |
Struts & Hibernate
|
|
|
| | | how to avoid transaction aborting | how to avoid transaction aborting 2006-01-19 - By bin cai
Back
Hi, Dear guys
I really hope you can help me to solve this problem.
for example:
i open two transactions which both get access to same record in database. so
two objects are loaded for this record. and in these two transactions, both of
these object(mapped to same record) are modified. upon committing, one these
two transactions will be aborted (dirty modification). and user lost all the
data. I think it is not acceptable for user. and these problems happen quite
often since the many transactions in our system are long transactions which
last over ten minutes or longer.
Could anyone can give me some hint? i search internet and did not get some
userful info related to that?
I don't know if it is practicle to implemented dirty checking before
committing anything to database in transaction?
Thanks in advaced
bin
-- ---- ---- ---- ---- ---- -----
Yahoo! Photos
Got holiday prints? See all the ways to get quality prints in your hands ASAP.
===========================================================================
To unsubscribe, send email to listserv@(protected) and include in the body
of the message "signoff J2EE-INTEREST". For general help, send email to
listserv@(protected) and include in the body of the message "help".
<DIV id=RTEContent>Hi, Dear guys</DIV> <DIV>I really hope you can help me to
solve this problem.</DIV> <DIV>for example:</DIV> <DIV>i open two
transactions which both get access to same record in database. so two objects
are loaded for this record. and in these two transactions, both of these object
(mapped to same record) are modified. upon committing, one these two
transactions will be aborted (dirty modification). and user lost all the data.
I think it is not acceptable for user. and these problems happen quite often
since the many transactions in our system are long transactions which
last over ten minutes or longer.</DIV> <DIV> </DIV> <DIV>Could anyone
can give me some hint? i search internet and did not get some userful info
related to that?</DIV> <DIV>I don't know if it is practicle to implemented
dirty checking before committing anything to database in transaction?</DIV>
<DIV> </DIV> <DIV>Thanks in advaced</DIV> <DIV>bin</DIV><p>
<hr size=1>Yahoo! Photos<br>
Got holiday prints? <a href="http://us.rd.yahoo.com/mail_us/taglines
/holidayprints/*http://pa.yahoo.com/*http://us.rd.yahoo.com/mail_us/taglines
/photos/evt=38089/*http://pg.photos.yahoo.com/ph//print_splash">See all the ways
</a> to get quality prints in your hands ASAP.
===========================================================================
To unsubscribe, send email to listserv@(protected) and include in the body
of the message "signoff J2EE-INTEREST". For general help, send email to
listserv@(protected) and include in the body of the message "help".
<p>
|
|
|
