The stack trace shows the page that is holding the lock as well Martijn
On Wed, Jun 8, 2011 at 7:20 AM, Martin Grigorov <[email protected]> wrote: > On Wed, Jun 8, 2011 at 7:00 AM, Jeffrey Schneller > <[email protected]> wrote: >> I have started to see more and more of the following exception when >> users are using the wicket app. >> >> >> >> org.apache.wicket.WicketRuntimeException: After 1 minute the Pagemap >> null is still locked by: Thread[TP-Processor24,5,main], giving up trying >> to get the page for path: 4:products:0:prodBuyLink >> >> >> >> If my understanding is right, it is a timeout that is occurring because >> the app is still processing for the page that is trying to be viewed. >> Is this correct? Any ideas on how to debug or solve? What are some >> common reasons for this type of exception? > > Correct. You can dump the thread's state with tools like jconsole or > on unix machines with "kill -3 pid". > Making several dumps you will see the thread that is "stuck". >> >> >> >> >> >> > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
