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 So then it is more that there is some exception in front of that maybe that somehow didnt release the pagemap What version of wicket do you use? On Tue, May 4, 2010 at 23:40, 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 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) > java.lang.Object.wait(Object.java:485) > > org.apache.tomcat.util.net.AprEndpoint$Worker.await(AprEndpoint.java:1511) > > org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1536) > java.lang.Thread.run(Thread.java:619) > End of stack trace of Thread[http-8084-7,5,main] > org.apache.wicket.protocol.http.request.InvalidUrlException: > 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) > java.lang.Object.wait(Object.java:485) > > org.apache.tomcat.util.net.AprEndpoint$Worker.await(AprEndpoint.java:1511) > > org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1536) > java.lang.Thread.run(Thread.java:619) > End of stack trace of Thread[http-8084-7,5,main] > > -- Any tips > > I >
