Integration

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Empty Transaction on UnitOfWork.commit()

387441Mar 4 2003 — edited Mar 4 2003

While SQL Profiling my company's application, I noticed an extra empty transaction during UnitOfWork.commit().

If my analysis is correct, could someone tell me why this is happening and if it can be removed.
I created a test TopLink project with one class and a test program which created one object and saw the same SQL Profiler results.

TopLink 9.0.3
i-net Sprinta2000 v4.17 JDBC driver
SQL Server 2000 SP2

SQL:BatchStarting IF @@TRANCOUNT>0 COMMIT TRAN BEGIN TRAN
SP:ExecContextHit
SQL:StmtStarting IF @@TRANCOUNT>0
SQL:StmtCompleted IF @@TRANCOUNT>0
SQL:StmtStarting COMMIT TRAN
SQL:StmtCompleted COMMIT TRAN
SQL:StmtStarting BEGIN TRAN
SQL:StmtCompleted BEGIN TRAN
SQL:BatchCompleted IF @@TRANCOUNT>0 COMMIT TRAN BEGIN TRAN

SQL:BatchStarting IF @@TRANCOUNT>0 COMMIT TRAN
SQL:StmtStarting IF @@TRANCOUNT>0
SQL:StmtCompleted IF @@TRANCOUNT>0
SQL:StmtStarting COMMIT TRAN
SQL:StmtCompleted COMMIT TRAN

Locked Post

New comments cannot be posted to this locked post.

Locked on Apr 1 2003

Added on Mar 4 2003

#application-servers, #toplink-jpa

2 comments

630 views