Thanks for the idea of using kill -3 pid

I don't see the page in the stack trace which is below, unless it is the line I 
have started with ===>.



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
 
Stack Trace: 
org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:262)
org.apache.wicket.protocol.https.HttpsRequestCycleProcessor.resolve(HttpsRequestCycleProcessor.java:219)
org.apache.wicket.RequestCycle.step(RequestCycle.java:1310)
org.apache.wicket.RequestCycle.steps(RequestCycle.java:1436)
org.apache.wicket.RequestCycle.request(RequestCycle.java:545)
org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:486)
org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:319)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:198)
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
===>com.myapp.web.MDCSessionFilter.doFilter(MDCSessionFilter.java:40)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
java.lang.Thread.run(Thread.java:619)

-----Original Message-----
From: Martijn Dashorst [mailto:martijn.dasho...@gmail.com] 
Sent: Wednesday, June 08, 2011 3:30 AM
To: users@wicket.apache.org
Subject: Re: WicketRuntimeException

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 <mgrigo...@apache.org> wrote:
> On Wed, Jun 8, 2011 at 7:00 AM, Jeffrey Schneller
> <jeffrey.schnel...@envisa.com> 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: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to