[
https://issues.apache.org/jira/browse/JCR-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664435#action_12664435
]
Marcel Reutegger commented on JCR-1938:
---------------------------------------
It seems the JVM is running out of memory. Thread '156' it not waiting for any
other thread, but it is waiting for memory to be freed.
You should try to find out what's causing the memory consumption, e.g. using
this tool: http://e-docs.bea.com/jrockit/tools/usingmmleak/gettingstart.html
> Thread lock with weblogic
> -------------------------
>
> Key: JCR-1938
> URL: https://issues.apache.org/jira/browse/JCR-1938
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jca
> Affects Versions: core 1.4.6
> Environment: BEA JRockit 1.5.0_06 - Weblogic 9.2
> Reporter: Francois Masurel
> Attachments: thread_dump.txt
>
>
> Hello,
> We have some deadlock issues with jackrabbit 1.4.6 under weblogic 9.2.
> It seems to happen when the connection pool has reached the maximum
> connections allowed.
> We have to restart weblogic to resolve the problem, it's a bit annoying.
> Actually used on our intranet, we plan to use our CMS solution based on
> jackrabbit on an important public administration internet portal but this
> problem is a showstopper for us.
> Is it a bug ? Did we miss something in our jackrabbit/weblogic configuration
> ?
> Thanx for your help.
> Thread dump excerpt :
> "[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default
> (self-tuning)'" id=13 idx=0x1a tid=24446 prio=1 alive, in native, blocked,
> daemon
> -- Blocked trying to get lock:
> EDU/oswego/cs/dl/util/concurrent/writerpreferencereadwritelock$readerl...@0xabdd8d0[fat
> lock]
> at jrockit/vm/Threads.waitForSignal(J)Z(Native Method)
> at
> jrockit/vm/Locks.fatLockBlockOrSpin(ILjrockit/vm/ObjectMonitor;II)V(Unknown
> Source)[optimized]
> at
> jrockit/vm/Locks.lockFat(Ljava/lang/Object;ILjrockit/vm/ObjectMonitor;Z)Ljava/lang/Object;(Unknown
> Source)[optimized]
> at
> jrockit/vm/Locks.monitorEnterSecondStage(Ljava/lang/Object;I)Ljava/lang/Object;(Unknown
> Source)[optimized]
> at
> jrockit/vm/Locks.monitorEnter(Ljava/lang/Object;)Ljava/lang/Object;(Unknown
> Source)[inlined]
> at jrockit/vm/Locks.monitorEnterForced(Ljava/lang/Object;)Z(Unknown
> Source)[optimized]
> at jrockit/vm/RNI.c2java(IIII)V(Native Method)
> at jrockit/vm/Locks.monitorEnterUnmatched(Ljava/lang/Object;)V(Native
> Method)
> at
> EDU/oswego/cs/dl/util/concurrent/WriterPreferenceReadWriteLock$ReaderLock.acquire()V(Unknown
> Source)[optimized]
> at
> org/apache/jackrabbit/core/state/DefaultISMLocking$ReadLockImpl.<init>(LEDU/oswego/cs/dl/util/concurrent/Sync;)V(DefaultISMLocking.java:103)[inlined]
> at
> org/apache/jackrabbit/core/state/DefaultISMLocking$ReadLockImpl.<init>(LEDU/oswego/cs/dl/util/concurrent/Sync;Lorg/apache/jackrabbit/core/state/Defaul
> tISMLocking$1;)V(DefaultISMLocking.java:97)[inlined]
> at
> org/apache/jackrabbit/core/state/DefaultISMLocking.acquireReadLock(Lorg/apache/jackrabbit/core/ItemId;)Lorg/apache/jackrabbit/core/state/ISMLocking$Re
> adLock;(DefaultISMLocking.java:65)[optimized]
> at
> org/apache/jackrabbit/core/state/SharedItemStateManager.acquireReadLock(Lorg/apache/jackrabbit/core/ItemId;)Lorg/apache/jackrabbit/core/state/ISMLocki
> ng$ReadLock;(SharedItemStateManager.java:1454)[inlined]
> at
> org/apache/jackrabbit/core/state/SharedItemStateManager.hasItemState(Lorg/apache/jackrabbit/core/ItemId;)Z(SharedItemStateManager.java:270)[optimized]
> at
> org/apache/jackrabbit/core/state/XAItemStateManager.hasItemState(Lorg/apache/jackrabbit/core/ItemId;)Z(XAItemStateManager.java:285)[optimized]
> at
> org/apache/jackrabbit/core/state/SessionItemStateManager.hasItemState(Lorg/apache/jackrabbit/core/ItemId;)Z(SessionItemStateManager.java:210)[optimize
> d]
> at
> org/apache/jackrabbit/core/ItemManager.itemExists(Lorg/apache/jackrabbit/core/ItemId;)Z(ItemManager.java:282)[inlined]
> at
> org/apache/jackrabbit/core/NodeImpl.hasProperty(Ljava/lang/String;)Z(NodeImpl.java:2752)[optimized]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
