Hello,
I am using now yourkit, but still can not recognize the problematic thread.
In the point when exception appeared, I have some threads running, but they
seems to be proper ones, expected according request what was clicked in a
webapplication.
see below my exception, and please give me some advice
20.6.2008 12:57:04 org.apache.wicket.RequestCycle logRuntimeException
SEVERE: After 1 minute the Pagemap null is still locked by:
Thread[http-8080-Processor23,5,main], giving up trying to get the page for
path: 11
org.apache.wicket.WicketRuntimeException: After 1 minute the Pagemap null is
still locked by: Thread[http-8080-Processor23,5,main], giving up trying t
o get the page for path: 11
at org.apache.wicket.Session.getPage(Session.java:740)
at
org.apache.wicket.request.AbstractRequestCycleProcessor.resolveRenderedPage(AbstractRequestCycleProcessor.java:448)
at
org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:139)
at org.apache.wicket.RequestCycle.step(RequestCycle.java:1224)
at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1331)
at org.apache.wicket.RequestCycle.request(RequestCycle.java:493)
at
org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:363)
at
org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:194)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
at java.lang.Thread.run(Thread.java:619)
Johan Compagner wrote:
>
> start tomcat or jetty just with java in the command prompt. So that you
> have
> a console window
>
> Also you can use other tools like yourkit to see the stack traces (or jmx)
> johan
>
>
> On Tue, Jun 17, 2008 at 12:14 PM, lienok
> <[EMAIL PROTECTED]<[EMAIL PROTECTED]>>
> wrote:
>
>>
>> Hi Johan,
>>
>> I am sorry but I don't understand. How can I run wicket application just
>> from the console?
>> Which class should I lunch to start it?
>>
>>
>> Johan Compagner wrote:
>> >
>> > run java.exe in a console and do CTRL-BREAK
>> >
>> >
>> >
>> > On Tue, Jun 17, 2008 at 11:57 AM, lienok
>> > <[EMAIL PROTECTED]
>> <[EMAIL PROTECTED]><[EMAIL PROTECTED]<[EMAIL PROTECTED]>
>> >>
>> > wrote:
>> >
>> >>
>> >> Hello
>> >>
>> >> I have the similar problem, but not running on Unix. Can you please
>> help
>> >> me
>> >> how can get thread dump in windows?
>> >>
>> >> any advice appreciated
>> >> Lenka
>> >>
>> >>
>> >> On 18/03/2008, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
>> >> > Glad to be of help. kill -3 is one of those gems you should never
>> >> > forget as it can save your life. "Kill to save your life": nice
>> >> > slogan... :D
>> >> >
>> >> >
>> >> > Martijn
>> >> >
>> >> >
>> >> > On 3/19/08, Jeremy Levy <[EMAIL PROTECTED]> wrote:
>> >> > > Thanks Igor / Martijn for your help.
>> >> > >
>> >> > > As you mentioned Wicket had nothing to do with it. I had a
>> piece
>> >> of
>> >> > code
>> >> > > that was executed when a user clicked a certain link and was
>> >> blocking
>> >> > by
>> >> > > accident, caught in a loop peging the CPU. Your suggestions of
>> >> kill
>> >> > -3 to
>> >> > > get the thread dump over a couple of samples helped me to narrow
>> >> down
>> >> > the
>> >> > > issue and fix it.
>> >> > >
>> >> > > Thanks very much.
>> >> > >
>> >> > >
>> >> > > Jeremy
>> >> > >
>> >>
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/After-1-minute-the-Pagemap-null-is-still-locked-tp16129637p17881661.html
>> >> Sent from the Wicket - User mailing list archive at Nabble.com.
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >>
>> >>
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/After-1-minute-the-Pagemap-null-is-still-locked-tp16129637p17881906.html
>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/After-1-minute-the-Pagemap-null-is-still-locked-tp16129637p18027755.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
