You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Ralph Goers <Ra...@dslextreme.com> on 2006/01/05 07:54:22 UTC
Locks not released in AuthenticationProfileManager?
I got another stack trace from our product today. I have 25 threads that
look like the one below. No thread appears to have the lock. I then
looked at getProfile() which is the only method getting the writeLock.
However, I don't see a releaseLocks() being done in that method. Am I
missing something?
Ralph
"http-8080-Processor70" daemon prio=1 tid=0x081571a0 nid=0xbbd in
Object.wait() [2807d000..2807e87c]
at java.lang.Object.wait(Native Method)
- waiting on <0x60b14778> (a
org.apache.cocoon.portal.profile.impl.AuthenticationProfileManager$ReadWriteLock)
at java.lang.Object.wait(Object.java:429)
at
org.apache.cocoon.portal.profile.impl.AuthenticationProfileManager$ReadWriteLock.readLock(AuthenticationProfileManager.java:489)
- locked <0x60b14778> (a
org.apache.cocoon.portal.profile.impl.AuthenticationProfileManager$ReadWriteLock)
at
org.apache.cocoon.portal.profile.impl.AuthenticationProfileManager.loadProfile(AuthenticationProfileManager.java:105)
at
org.apache.cocoon.portal.profile.impl.AbstractUserProfileManager.getPortalLayout(AbstractUserProfileManager.java:345)
at
org.apache.cocoon.portal.impl.PageLabelManager.initializeLabels(PageLabelManager.java:251)
at
org.apache.cocoon.portal.impl.PageLabelManager.getPageLabelEvents(PageLabelManager.java:190)
at
org.apache.cocoon.portal.event.aspect.impl.PageLabelEventAspect.process(PageLabelEventAspect.java:84)
Re: Locks not released in AuthenticationProfileManager?
Posted by Ralph Goers <Ra...@dslextreme.com>.
I figured out that the releaseLocks happens elsewhere.
I noticed that several of the threads are waiting for the write lock.
There does appear to be one thread, that based on where it is, should
have the read lock, however the stack trace doesn't show it. That
thread is in the class loader in Castor (we haven't deployed the mapping
file changes yet).
So it appears that because there are outstanding writers the readers are
also being blocked and everything is stacking up behind Castor.
So never mind (for now).
<sigh>
Ralph
Ralph Goers wrote:
> I got another stack trace from our product today. I have 25 threads
> that look like the one below. No thread appears to have the lock. I
> then looked at getProfile() which is the only method getting the
> writeLock. However, I don't see a releaseLocks() being done in that
> method. Am I missing something?
>
> Ralph
>
> "http-8080-Processor70" daemon prio=1 tid=0x081571a0 nid=0xbbd in
> Object.wait() [2807d000..2807e87c]
> at java.lang.Object.wait(Native Method)
> - waiting on <0x60b14778> (a
> org.apache.cocoon.portal.profile.impl.AuthenticationProfileManager$ReadWriteLock)
>
> at java.lang.Object.wait(Object.java:429)
> at
> org.apache.cocoon.portal.profile.impl.AuthenticationProfileManager$ReadWriteLock.readLock(AuthenticationProfileManager.java:489)
>
> - locked <0x60b14778> (a
> org.apache.cocoon.portal.profile.impl.AuthenticationProfileManager$ReadWriteLock)
>
> at
> org.apache.cocoon.portal.profile.impl.AuthenticationProfileManager.loadProfile(AuthenticationProfileManager.java:105)
>
> at
> org.apache.cocoon.portal.profile.impl.AbstractUserProfileManager.getPortalLayout(AbstractUserProfileManager.java:345)
>
> at
> org.apache.cocoon.portal.impl.PageLabelManager.initializeLabels(PageLabelManager.java:251)
>
> at
> org.apache.cocoon.portal.impl.PageLabelManager.getPageLabelEvents(PageLabelManager.java:190)
>
> at
> org.apache.cocoon.portal.event.aspect.impl.PageLabelEventAspect.process(PageLabelEventAspect.java:84)
>
>
>