detail.php
OW2 Forge: Detail: 304793 JOTM 2.0.8 two phase commit causes the transaction to hang in MS SQL Server during rollback

Advanced - Powered by Google


   
Log In
New Account
  
 
Home
My Page
Project Tree
Project Openings
JOTM
          
 
 
Summary
Tracker
Lists
Tasks
News
CVS
Files
SVN
                
 

Tracker: Bugs

Submit New | Browse | Admin | ExportToXml

[ #304793 ] JOTM 2.0.8 two phase commit causes the transaction to hang in MS SQL Server during rollback

Date:
2006-03-16 02:17
Priority:
3
Submitted By:
Muthukumaran Thayumanavan (thayu)
Assigned To:
Philippe Durieux (durieuxp)
Category:
JOTM
State:
Open
Summary:
JOTM 2.0.8 two phase commit causes the transaction to hang in MS SQL Server during rollback

Detailed description:
Hi, We have rolled in to production a J2ee application using JOTM 2.0.8 with xapool 1.5.0 as the Transaction manager and JOTM being instantiated to be local. We have been commiting records to Oracle 9.0.2 and MS SQL Server 2000 using two phase commit. We have been experiencing the following problem during high load. The Transaction in SQL Server hangs and blocks all other transactions and renders the SQL Server DB instance un-usable while the JOTM is trying to do a rollback. The JVM CPU utilization shoots up to 96% and almost freezes the application. We end up killing the transaction at the SQL Server DB Instance and restarting the application in production. Could any one let us know whether this issue was noticed earlier and any fix was made in the later release (2.0.10)? I would appriciate help in this regard very much. Since this is a production isssue, it would be of great help if we can get a solution as soon as possible. Thanks Very much. Regards, -Thayu

Add A Comment:

Please login

Followup

Message
Date: 2009-08-13 19:58
Sender: jayakrishnankr
Logged In: YES 
user_id=17871

Hi I have a same kind of issue. we are using jotm2.0.10 
version with xapool1.5. Here a sequence is blocking an 
insert statement. the below is the error log. 

25-JUN-2009 12:11:22 User XXXX@XXXXX ( SID= XXXX) with the 
statement: SELECT A_SEQ.NEXTVAL FROM DUAL is blocking the 
SQL statement on XXXX@XXXXX ( SID=XXXX ) blocked SQL -> 
INSERT INTO segment (x, x, x, x, x, x, x, x, x, x, x, x, x, 
x, x, x, x, x, x, x, x, x, x, x, x, x, x, x, x) VALUES 
(:1, :2, :3, :4, :5, :6, :7, :8, :9, :10, :11, :12, :13, :14
, :15, :16, :17, :18, :19, :20, :21, :22, :23, :24, :25, :26
, :27, :28, :29)

Can anyone suggest if it is a bug..
Date: 2009-01-06 11:40
Sender: durieuxp
Logged In: YES 
user_id=228

A fix has been done in the branch jotm-2-0-11-br
See bug 312305.
Maybe this can explain this issue (not sure)

Attached Files:

Name Description Download
No Files Currently Attached

Changes:

Field Old Value Date By
artifact_group_idNone2009-03-10 16:40durieuxp
resolution_idNone2009-01-06 11:43durieuxp
priority82009-01-06 11:43durieuxp
assigned_tonone2009-01-06 11:40durieuxp
priority52006-03-28 20:12thayu

Copyright © 1999-2008, OW2 Consortium | contact | You have a difficulty, a problem ? Please report an issue using your OW2 forge account credentials