I saw that you are running wicket 1.4.2, I'd upgrade to 1.4.12. Thread
detach logic in Wicket has been improved in the releases between iirc.
This is not common enough for us to guess what is wrong. You should go
back in your logs and see what happened in the thread that keeps the
page map locked.
How do I properly detach pages from request threads? What could have
caused them not to be properly detached?
I saw this error only once in months, so I don't even know how to
reproduce it. However, even though it is rare this problem is critical
because it made the web site unresponsive.
I added
It appears that your pages have not been properly detached from their
request threads. Wicket still thinks that TP-Processor1 has the
pagemap locked, whereas that thread is waiting for mod_jk to deliver a
new request.
I'd look back in the history of what TP-Processor1 has done to get in
that state
Hello,
Our production server stopped processing AJAX requests today. I looked
in the log files and noticed a "After 1 minute the Pagemap null is
still locked".
The exception stack trace is shown below followed by a dump of the
thread that was blocking the page.
We are using Wicket 1.4.2, Tomcat 6
