Re: WOSessionStore$TimeoutEntry

by Chuck Hill :: Rate this Message:

On Jul 31, 2008, at 10:16 AM, Fred Larken wrote:

>
> Yes, we are setting this in the code:
> setAllowsConcurrentRequestHandling(true);

The trace below is probably a symptom then, not the cause.

> The session timeout is set to 30 minutes.
>
> How do I find out why a session is hung, or how to fix this?

Check the the thread dumps that don't show this trace.

Check that session's sleep() and terminate() methods can't throw.
Check awake too for good measure.

> I saw one post that said something about adding code to your
> Application.java
> Is this the correct way to fix it, or is this problem just a result of
> something else happening?
> http://www.mail-archive.com/webobjects-dev@.../msg09497.html
> http://www.mail-archive.com/webobjects-dev@.../msg09497.html

You could try this if nothing else pans out.

Chuck

>>
>>
>> On Jul 31, 2008, at 9:52 AM, Fred Larken wrote:
>>
>>>
>>> we have a linux server running our web objects app. After a day, the
>>> system
>>> locks up for 30 mins. It will self-recoverbut in the mean time,
>>> nobody can
>>> log in or use the app. I have seen thread dumps during this period
>>> and I
>>> have noticed the following trace:
>>>
>>>
>>> "http-20226-Processor24" daemon prio=1 tid=0x52321880 nid=0x593 in
>>> Object.wait() [0x51b7d000..0x51b7e120]
>>> at java.lang.Object.wait(Native Method)
>>> - waiting on <0xaaede7d8> (a
>>> com.webobjects.appserver.WOSessionStore$TimeoutEntry)
>>> at java.lang.Object.wait(Object.java:474)
>>> at
>>> com
>>> .webobjects
>>> .appserver.WOSessionStore.checkOutSessionWithID(WOSessionStore.java:
>>> 191)
>>> - locked <0xaaede7d8> (a
>>> com.webobjects.appserver.WOSessionStore$TimeoutEntry)
>>> at
>>> com
>>> .webobjects
>>> .appserver.WOApplication.restoreSessionWithID(WOApplication.java:
>>> 1904)
>>>
>>> There are a lot of http threads in this state. There is one lock for
>>> every 4
>>> http threads waiting on it.
>>>
>>> Can any one explain what the above means?
>>
>> Are you dispatching requests concurrently? I am guessing the answer
>> is
>> no. Is your session timeout 30 minutes? It looks like a session is
>> getting hung and blocking the app until it expires
>>
>> Chuck
>>
>>
>> --
>> Chuck Hill Senior Consultant / VP Development
>>
>> Practical WebObjects - for developers who want to increase their
>> overall knowledge of WebObjects or who are trying to solve specific
>> problems.
>> http://www.global-village.net/products/practical_webobjects
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> WebObjects-dev mailing list
>> WebObjects-dev@...
>> http://www.omnigroup.com/mailman/listinfo/webobjects-dev
>>
>>
>
> --
> View this message in context: http://www.nabble.com/WOSessionStore%24TimeoutEntry-tp18756956p18759318.html
> Sent from the WebObjects-Dev mailing list archive at Nabble.com.
>
> _______________________________________________
> WebObjects-dev mailing list
> WebObjects-dev@...
> http://www.omnigroup.com/mailman/listinfo/webobjects-dev
>

--
Chuck Hill Senior Consultant / VP Development

Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects

_______________________________________________
WebObjects-dev mailing list
WebObjects-dev@...
http://www.omnigroup.com/mailman/listinfo/webobjects-dev

« Return to Thread: WOSessionStore$TimeoutEntry