Lock request timeout ...

Question

Dear Rob ,
To consult you again and thanks in advise.
The following code is my session bean's method ,
public void updateDclrDiagnose(String hospitalNo,String dclrYYMM,int postSeq,String
diagKindSign,String[] diagNoAll,String caseNo,String operatorNo) throws CommonException{
DclrDiagnoseHome dclrDiagNoseHome = getDclrDiagnoseHome();
Collection c = dclrDiagNoseHome.findByDiagKindSign (hospitalNo,dclrYYMM,postSeq,diagKindSign);
Iterator it = c.iterator();
while(it.hasNext()){
DclrDiagnose dclrDiagnose = (DclrDiagnose) it.next();
log("delete diagnose - diagNo=" + dclrDiagnose.getDcg_diag_no());
dclrDiagnose.remove();
for(int i = 0; i < diagNoAll.length; i++){
log("create diagnose - diagNo=" + diagNoAll);
dclrDiagNoseHome.create(hospitalNo,dclrYYMM,postSeq,diagKindSign,i+1,diagNoAll[i],caseNo,operatorNo);
log("method complete!!");
When my client JSP call this method several times later , then it will throw an exception
, as following
javax.transaction.TransactionRolledbackException: The lock request from EJB:com.
syscom.prjnckm.hospitalization.declaration.entity.DclrDiagnose with primary key:
com.syscom.prjnckm.hospitalization.declaration.entity.DclrDiagnosePK@74dfef60 ti
med-out after waiting 0 ms. The transaction or thread requesting the lock was:Na
me=[EJB com.syscom.prjnckm.hospitalization.declaration.session.DclrMaintainBean.
updateDclrDiagnose(java.lang.String,java.lang.String,int,java.lang.String,[Ljava
.lang.String;,java.lang.String,java.lang.String)],Xid=155:94dc41cc01ac93a7(35974
8176),Status=Active,numRepliesOwedMe=1,numRepliesOwedOthers=1,seconds since begi
n=30,seconds left=0,activeThread=Thread[ExecuteThread: '9' for queue: 'default',
5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connec
tion]=(state=ended,assigned=none),SCInfo[nckmdomain+nckmsvr]=(state=active),prop
erties=({weblogic.transaction.name=[EJB com.syscom.prjnckm.hospitalization.decla
ration.session.DclrMaintainBean.updateDclrDiagnose(java.lang.String,java.lang.St
ring,int,java.lang.String,[Ljava.lang.String;,java.lang.String,java.lang.String)
], weblogic.jdbc=t3://10.10.10.1:80}),OwnerTransactionManager=ServerTM[ServerCoo
rdinatorDescriptor=(CoordinatorURL=nckmsvr+10.10.10.1:80+nckmdomain+, Resources=
{})],CoordinatorURL=nckmsvr+10.10.10.1:80+nckmdomain+).: weblogic.ejb20.locks.Lo
ckTimedOutException: The lock request from EJB:com.syscom.prjnckm.hospitalizatio
n.declaration.entity.DclrDiagnose with primary key:com.syscom.prjnckm.hospitaliz
ation.declaration.entity.DclrDiagnosePK@74dfef60 timed-out after waiting 0 ms. T
he transaction or thread requesting the lock was:Name=[EJB com.syscom.prjnckm.ho
spitalization.declaration.session.DclrMaintainBean.updateDclrDiagnose(java.lang.
String,java.lang.String,int,java.lang.String,[Ljava.lang.String;,java.lang.Strin
g,java.lang.String)],Xid=155:94dc41cc01ac93a7(359748176),Status=Active,numReplie
sOwedMe=1,numRepliesOwedOthers=1,seconds since begin=30,seconds left=0,activeThr
ead=Thread[ExecuteThread: '9' for queue: 'default',5,Thread Group for Queue: 'de
fault'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=ended,assigned=n
one),SCInfo[nckmdomain+nckmsvr]=(state=active),properties=({weblogic.transaction
.name=[EJB com.syscom.prjnckm.hospitalization.declaration.session.DclrMaintainBe
an.updateDclrDiagnose(java.lang.String,java.lang.String,int,java.lang.String,[Lj
ava.lang.String;,java.lang.String,java.lang.String)], weblogic.jdbc=t3://10.10.1
0.1:80}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(Coordinat
orURL=nckmsvr+10.10.10.1:80+nckmdomain+, Resources={})],CoordinatorURL=nckmsvr+1
0.10.10.1:80+nckmdomain+).
at weblogic.ejb20.locks.ExclusiveLockManager$LockBucket.lock(ExclusiveLo
ckManager.java:527)
at weblogic.ejb20.locks.ExclusiveLockManager.lock(ExclusiveLockManager.j
ava:258)
at weblogic.ejb20.manager.ExclusiveEntityManager.acquireLock(ExclusiveEn
tityManager.java:164)
at weblogic.ejb20.manager.ExclusiveEntityManager.getReadyBean(ExclusiveE
ntityManager.java:219)
at weblogic.ejb20.manager.ExclusiveEntityManager.preInvoke(ExclusiveEnti
tyManager.java:198)
What it does mean ?
Could you give me some idea. Thanks you very much.
imagine
ps.
AP server is WLS 6.1 sp1
all method's tx aattribute is set to Required
log msg is as following,
the first time call:
create diagnose - diagNo=00804
create diagnose - diagNo=00809
method complete!!
the second time call:
delete diagnose - diagNo=00804
delete diagnose - diagNo=00809
create diagnose - diagNo=00804
method complete!!
the third time call:
delete diagnose - diagNo=00804
create diagnose - diagNo=00804
create diagnose - diagNo=00809
method complete!!
the firth time call:
delete diagnose - diagNo=00804
...then Exception occur

Answer 1

Thank you Erland. This is what I got from sys.sysprocesses:
spid 7
kpid 6544
blocked 0
waittype 0x009D
waittime 489897
lastwaittype KSOURCE_WAKEUP 
waitresource
dbid 1
uid 1
cpu 0
physical_io 0
memusage 0
login_time 12-05-2014 21:09
last_batch 12-05-2014 21:09
ecid 0
open_tran 4
status background                    
sid 0x0100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
hostname
program_name
hostprocess
cmd SIGNAL HANDLER 
nt_domain
nt_username
net_address
net_library
loginame sa
context_info 0x0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
sql_handle 0x0000000000000000000000000000000000000000
stmt_start 0
stmt_end 0
request_id 0
I think I should apply latest service pack and see if the issue exists.