This is only a thought...
there were some deadlock issues in 1.3 that were fixed in 1.3.1...
assuming by 1.3 you mean 1.3 and not 1.3.1.
From what I remember they were triggered under load with the
ClusterNode turned on in the config. I don't think that you needed to be
running in a cluster. JCR-924 might be one of the related jiras (from
failing memory)
:)
Ian
KÖLL Claus wrote:
hi,
we have some time now jackrabbit (1.3) running in our pruduction environment but
without xa enabled. We are running on websphere 5.1 and i have configured now a
j2c resource adapter
for jackrabbit. it works fine till i try to modify a node in the repository in
a global transaction.
if i only try a search everything works fine.
i have taken a thread dump with the deadlock situation.
what i can see comes the deadlock from the DefaultISMLocking$ReadLockImpl Class
hope somebodycan help ....
BR,
claus
<<javacore.20080117.103807.536.txt>>
