if you have a test case please make a jira issue and attach your sample.
It is strange because in onBeginRequest of a request cycle there is no page
locked what so ever.
So i dont see how this is related.
On Wed, May 19, 2010 at 00:49, Ayodeji Aladejebi aladej...@gmail.comwrote:
I notice
I notice this:
After 3 minutes the Pagemap null is still locked by:
Thread[http-8084-2,5,main], giving up trying to get the page for path:
2:topAdverts:advertListCont
What happened was that I called ((WebRequestCycle)
WebRequestCycle.get()).getWebRequest().getQueryString() within
onBeginRequest
version 1.4.6 on windows vista running on tomcat 6.0.26
On Wed, May 5, 2010 at 5:43 PM, Johan Compagner jcompag...@gmail.comwrote:
hmm
looking at the stack of the of that thread that has the lock on the page
map
then it seems to me that that shouldnt happen, because that thread is doing
hmm
looking at the stack of the of that thread that has the lock on the page map
then it seems to me that that shouldnt happen, because that thread is doing
nothing anymore if the stack dump of that thread is really the right one.
Because that just seems to be in a waiting state in a tomcat pool
SEVERE: org.apache.wicket.WicketRuntimeException: After 1 minute the Pagemap
null is still locked by: Thread[http-8084-7,5,main], giving up trying to get
the page for path: 2
Begin of stack trace of Thread[http-8084-7,5,main]
java.lang.Object.wait(Native Method)
dont execute code that takes 1+ minutes to finish inside a web thread
-igor
On Tue, May 4, 2010 at 2:40 PM, Ayodeji Aladejebi aladej...@gmail.com wrote:
SEVERE: org.apache.wicket.WicketRuntimeException: After 1 minute the Pagemap
null is still locked by: Thread[http-8084-7,5,main], giving up
or more like a thread must not block for that long?
On Tue, May 4, 2010 at 11:01 PM, Igor Vaynberg igor.vaynb...@gmail.comwrote:
dont execute code that takes 1+ minutes to finish inside a web thread
-igor
On Tue, May 4, 2010 at 2:40 PM, Ayodeji Aladejebi aladej...@gmail.com
wrote:
What do you mean? The page map is locked because another request is still
running. If you have anything that takes a noticeable amount of time
(several seconds or more) to process, put it in a separate thread and
redirect to a waiting page.
--
Jeremy Thomerson
http://www.wickettraining.com
