You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Jeremy Levy <je...@gmail.com> on 2008/03/18 21:06:38 UTC
After 1 minute the Pagemap null is still locked
I am seeing the "After 1 minute the Pagemap null is still locked" error in
production a couple of times a day for about the last week or so. We put in
a major update to our site about 3 weeks ago, but only recently started
seeing this error. I suspect they are related.
>From doing some research on the mailinglist it seems that this comes up when
a user requests a new page while there is an open request still processing.
http://www.nabble.com/pagemap-locking-to11350774.html#a11350774
At the same time (or a few seconds before) the CPU is pegged at 100% and
stays that way. Overtime the CPU usage progressively gets more and more
backed up (I assume because this issue keeps happening and compounds the
load).
The longest page request on the site is a panel which has 4 child lazy
loading panels but none of them take longer then a max of 4 seconds, which
is pretty strictly enforced.
The CPU getting pegged is a huge problem because it is forcing us to restart
the server every some often.
For now we have not been able to reproduce this error in a development
environment, any suggestions, or troubleshooting ideas?
Jeremy
Re: After 1 minute the Pagemap null is still locked
Posted by mfs <fa...@gmail.com>.
Hi Guys,
We are facing a similar problem on an "Import Page" which at times does take
more than a minute for large data-set, which breaks the import. I wonder if
there is a way we can bypass OR avoid this exception so as to make the
import finish properly. I understand one way can be to break the import into
smaller data-set or yet otherwise make the import an asynchronous call but I
still want to explore what other options exists
Farhan.
Johan Compagner wrote:
>
> it does say the thread:
>
> Thread[http-8080-Processor23,5,main]
>
> So look what that is doing
>
>
> On Fri, Jun 20, 2008 at 1:32 PM, lienok
> <li...@gmail.com>>
> wrote:
>
>>
>> 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
>> > <lienok+it@gmail.com
>> <li...@gmail.com>
>> >>
>> > 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
>> >> > <lienok+it@gmail.com <li...@gmail.com>
>> >> <lienok%2Bit@gmail.com
>> <li...@gmail.com>
>> <lienok%252Bit@gmail.com <li...@gmail.com>>
>> >> >>
>> >> > 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 <ma...@gmail.com> 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 <je...@meetmoi.com> 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: users-unsubscribe@wicket.apache.org
>> >> >> For additional commands, e-mail: users-help@wicket.apache.org
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >> --
>> >> 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: users-unsubscribe@wicket.apache.org
>> >> For additional commands, e-mail: users-help@wicket.apache.org
>> >>
>> >>
>> >
>> >
>>
>> --
>> 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: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
--
View this message in context: http://www.nabble.com/After-1-minute-the-Pagemap-null-is-still-locked-tp16129637p25716746.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: After 1 minute the Pagemap null is still locked
Posted by Johan Compagner <jc...@gmail.com>.
it does say the thread:
Thread[http-8080-Processor23,5,main]
So look what that is doing
On Fri, Jun 20, 2008 at 1:32 PM, lienok
<li...@gmail.com>>
wrote:
>
> 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
> > <lienok+it@gmail.com <li...@gmail.com>
> >>
> > 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
> >> > <lienok+it@gmail.com <li...@gmail.com>
> >> <lienok%2Bit@gmail.com <li...@gmail.com>
> <lienok%252Bit@gmail.com <li...@gmail.com>>
> >> >>
> >> > 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 <ma...@gmail.com> 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 <je...@meetmoi.com> 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: users-unsubscribe@wicket.apache.org
> >> >> For additional commands, e-mail: users-help@wicket.apache.org
> >> >>
> >> >>
> >> >
> >> >
> >>
> >> --
> >> 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: users-unsubscribe@wicket.apache.org
> >> For additional commands, e-mail: users-help@wicket.apache.org
> >>
> >>
> >
> >
>
> --
> 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: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: After 1 minute the Pagemap null is still locked
Posted by lienok <li...@gmail.com>.
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
> <li...@gmail.com>>
> 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
>> > <lienok+it@gmail.com
>> <li...@gmail.com>
>> >>
>> > 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 <ma...@gmail.com> 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 <je...@meetmoi.com> 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: users-unsubscribe@wicket.apache.org
>> >> For additional commands, e-mail: users-help@wicket.apache.org
>> >>
>> >>
>> >
>> >
>>
>> --
>> 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: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
--
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: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: After 1 minute the Pagemap null is still locked
Posted by Johan Compagner <jc...@gmail.com>.
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
<li...@gmail.com>>
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
> > <lienok+it@gmail.com <li...@gmail.com>
> >>
> > 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 <ma...@gmail.com> 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 <je...@meetmoi.com> 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: users-unsubscribe@wicket.apache.org
> >> For additional commands, e-mail: users-help@wicket.apache.org
> >>
> >>
> >
> >
>
> --
> 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: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: After 1 minute the Pagemap null is still locked
Posted by lienok <li...@gmail.com>.
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
> <li...@gmail.com>>
> 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 <ma...@gmail.com> 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 <je...@meetmoi.com> 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: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
--
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: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: After 1 minute the Pagemap null is still locked
Posted by Johan Compagner <jc...@gmail.com>.
run java.exe in a console and do CTRL-BREAK
On Tue, Jun 17, 2008 at 11:57 AM, lienok
<li...@gmail.com>>
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 <ma...@gmail.com> 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 <je...@meetmoi.com> 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: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: After 1 minute the Pagemap null is still locked
Posted by lienok <li...@gmail.com>.
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 <ma...@gmail.com> 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 <je...@meetmoi.com> 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: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: After 1 minute the Pagemap null is still locked
Posted by Gwyn Evans <gw...@gmail.com>.
Along the same lines, if/when you're able to run with Java 6, there
are a number of new & interesting options that become available for
monitoring without needing to run the app with special arguments...
(jstack, jconsole, visualvm & btrace for a start.)
/Gwyn
On 18/03/2008, Martijn Dashorst <ma...@gmail.com> 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 <je...@meetmoi.com> 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
> >
> >
> > On Tue, Mar 18, 2008 at 4:26 PM, Martijn Dashorst <
> > martijn.dashorst@gmail.com> wrote:
> >
> > > I suggest getting a thread dump at the time of the exception, to see
> > > which threads are stuck. You can do that by sending a kill -3 to the
> > > java process running your webapp. The stack traces should be in your
> > > console output captured by your server.
> > >
> > > Martijn
> > >
> > > On 3/18/08, Igor Vaynberg <ig...@gmail.com> wrote:
> > > > i think the only way this can happen is that you have something that
> > > > really takes longer then 1 minute to execute. i dont see how wicket
> > > > can take over your cpu....so may be it is that runaway process that
> > > > does that...
> > > >
> > > > i think to debug it you might want to attach a profiler to the server
> > > > and wait for it to happen, take a cpu timing profile and see what was
> > > > going on during the spike...
> > > >
> > > > does the message tell you who it is locked by? which page or
> > > > otherwise? if not that is possibly something we can improve also...
> > > >
> > > > -igor
> > > >
> > > >
> > > > On Tue, Mar 18, 2008 at 1:06 PM, Jeremy Levy <je...@gmail.com> wrote:
> > > > > I am seeing the "After 1 minute the Pagemap null is still locked"
> > > error in
> > > > > production a couple of times a day for about the last week or so.
> > > We put in
> > > > > a major update to our site about 3 weeks ago, but only recently
> > > started
> > > > > seeing this error. I suspect they are related.
> > > > >
> > > > > From doing some research on the mailinglist it seems that this comes
> > > up when
> > > > > a user requests a new page while there is an open request still
> > > processing.
> > > > >
> > > > > http://www.nabble.com/pagemap-locking-to11350774.html#a11350774
> > > > >
> > > > > At the same time (or a few seconds before) the CPU is pegged at 100%
> > > and
> > > > > stays that way. Overtime the CPU usage progressively gets more and
> > > more
> > > > > backed up (I assume because this issue keeps happening and compounds
> > > the
> > > > > load).
> > > > >
> > > > > The longest page request on the site is a panel which has 4 child
> > > lazy
> > > > > loading panels but none of them take longer then a max of 4 seconds,
> > > which
> > > > > is pretty strictly enforced.
> > > > >
> > > > > The CPU getting pegged is a huge problem because it is forcing us to
> > > restart
> > > > > the server every some often.
> > > > >
> > > > > For now we have not been able to reproduce this error in a
> > > development
> > > > > environment, any suggestions, or troubleshooting ideas?
> > > > >
> > > > > Jeremy
> > > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > >
> > > >
> > >
> > >
> > > --
> > > Buy Wicket in Action: http://manning.com/dashorst
> > > Apache Wicket 1.3.2 is released
> > > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.2
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
>
>
>
> --
>
> Buy Wicket in Action: http://manning.com/dashorst
> Apache Wicket 1.3.2 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.2
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Download Wicket 1.3.1 now! - http://www.apache.org/dyn/closer.cgi/wicket/1.3.1
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: After 1 minute the Pagemap null is still locked
Posted by Martijn Dashorst <ma...@gmail.com>.
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 <je...@meetmoi.com> 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
>
>
> On Tue, Mar 18, 2008 at 4:26 PM, Martijn Dashorst <
> martijn.dashorst@gmail.com> wrote:
>
> > I suggest getting a thread dump at the time of the exception, to see
> > which threads are stuck. You can do that by sending a kill -3 to the
> > java process running your webapp. The stack traces should be in your
> > console output captured by your server.
> >
> > Martijn
> >
> > On 3/18/08, Igor Vaynberg <ig...@gmail.com> wrote:
> > > i think the only way this can happen is that you have something that
> > > really takes longer then 1 minute to execute. i dont see how wicket
> > > can take over your cpu....so may be it is that runaway process that
> > > does that...
> > >
> > > i think to debug it you might want to attach a profiler to the server
> > > and wait for it to happen, take a cpu timing profile and see what was
> > > going on during the spike...
> > >
> > > does the message tell you who it is locked by? which page or
> > > otherwise? if not that is possibly something we can improve also...
> > >
> > > -igor
> > >
> > >
> > > On Tue, Mar 18, 2008 at 1:06 PM, Jeremy Levy <je...@gmail.com> wrote:
> > > > I am seeing the "After 1 minute the Pagemap null is still locked"
> > error in
> > > > production a couple of times a day for about the last week or so.
> > We put in
> > > > a major update to our site about 3 weeks ago, but only recently
> > started
> > > > seeing this error. I suspect they are related.
> > > >
> > > > From doing some research on the mailinglist it seems that this comes
> > up when
> > > > a user requests a new page while there is an open request still
> > processing.
> > > >
> > > > http://www.nabble.com/pagemap-locking-to11350774.html#a11350774
> > > >
> > > > At the same time (or a few seconds before) the CPU is pegged at 100%
> > and
> > > > stays that way. Overtime the CPU usage progressively gets more and
> > more
> > > > backed up (I assume because this issue keeps happening and compounds
> > the
> > > > load).
> > > >
> > > > The longest page request on the site is a panel which has 4 child
> > lazy
> > > > loading panels but none of them take longer then a max of 4 seconds,
> > which
> > > > is pretty strictly enforced.
> > > >
> > > > The CPU getting pegged is a huge problem because it is forcing us to
> > restart
> > > > the server every some often.
> > > >
> > > > For now we have not been able to reproduce this error in a
> > development
> > > > environment, any suggestions, or troubleshooting ideas?
> > > >
> > > > Jeremy
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
> >
> > --
> > Buy Wicket in Action: http://manning.com/dashorst
> > Apache Wicket 1.3.2 is released
> > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.2
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.2 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.2
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: After 1 minute the Pagemap null is still locked
Posted by Jeremy Levy <je...@meetmoi.com>.
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
On Tue, Mar 18, 2008 at 4:26 PM, Martijn Dashorst <
martijn.dashorst@gmail.com> wrote:
> I suggest getting a thread dump at the time of the exception, to see
> which threads are stuck. You can do that by sending a kill -3 to the
> java process running your webapp. The stack traces should be in your
> console output captured by your server.
>
> Martijn
>
> On 3/18/08, Igor Vaynberg <ig...@gmail.com> wrote:
> > i think the only way this can happen is that you have something that
> > really takes longer then 1 minute to execute. i dont see how wicket
> > can take over your cpu....so may be it is that runaway process that
> > does that...
> >
> > i think to debug it you might want to attach a profiler to the server
> > and wait for it to happen, take a cpu timing profile and see what was
> > going on during the spike...
> >
> > does the message tell you who it is locked by? which page or
> > otherwise? if not that is possibly something we can improve also...
> >
> > -igor
> >
> >
> > On Tue, Mar 18, 2008 at 1:06 PM, Jeremy Levy <je...@gmail.com> wrote:
> > > I am seeing the "After 1 minute the Pagemap null is still locked"
> error in
> > > production a couple of times a day for about the last week or so.
> We put in
> > > a major update to our site about 3 weeks ago, but only recently
> started
> > > seeing this error. I suspect they are related.
> > >
> > > From doing some research on the mailinglist it seems that this comes
> up when
> > > a user requests a new page while there is an open request still
> processing.
> > >
> > > http://www.nabble.com/pagemap-locking-to11350774.html#a11350774
> > >
> > > At the same time (or a few seconds before) the CPU is pegged at 100%
> and
> > > stays that way. Overtime the CPU usage progressively gets more and
> more
> > > backed up (I assume because this issue keeps happening and compounds
> the
> > > load).
> > >
> > > The longest page request on the site is a panel which has 4 child
> lazy
> > > loading panels but none of them take longer then a max of 4 seconds,
> which
> > > is pretty strictly enforced.
> > >
> > > The CPU getting pegged is a huge problem because it is forcing us to
> restart
> > > the server every some often.
> > >
> > > For now we have not been able to reproduce this error in a
> development
> > > environment, any suggestions, or troubleshooting ideas?
> > >
> > > Jeremy
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
>
> --
> Buy Wicket in Action: http://manning.com/dashorst
> Apache Wicket 1.3.2 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.2
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: After 1 minute the Pagemap null is still locked
Posted by Martijn Dashorst <ma...@gmail.com>.
I suggest getting a thread dump at the time of the exception, to see
which threads are stuck. You can do that by sending a kill -3 to the
java process running your webapp. The stack traces should be in your
console output captured by your server.
Martijn
On 3/18/08, Igor Vaynberg <ig...@gmail.com> wrote:
> i think the only way this can happen is that you have something that
> really takes longer then 1 minute to execute. i dont see how wicket
> can take over your cpu....so may be it is that runaway process that
> does that...
>
> i think to debug it you might want to attach a profiler to the server
> and wait for it to happen, take a cpu timing profile and see what was
> going on during the spike...
>
> does the message tell you who it is locked by? which page or
> otherwise? if not that is possibly something we can improve also...
>
> -igor
>
>
> On Tue, Mar 18, 2008 at 1:06 PM, Jeremy Levy <je...@gmail.com> wrote:
> > I am seeing the "After 1 minute the Pagemap null is still locked" error in
> > production a couple of times a day for about the last week or so. We put in
> > a major update to our site about 3 weeks ago, but only recently started
> > seeing this error. I suspect they are related.
> >
> > From doing some research on the mailinglist it seems that this comes up when
> > a user requests a new page while there is an open request still processing.
> >
> > http://www.nabble.com/pagemap-locking-to11350774.html#a11350774
> >
> > At the same time (or a few seconds before) the CPU is pegged at 100% and
> > stays that way. Overtime the CPU usage progressively gets more and more
> > backed up (I assume because this issue keeps happening and compounds the
> > load).
> >
> > The longest page request on the site is a panel which has 4 child lazy
> > loading panels but none of them take longer then a max of 4 seconds, which
> > is pretty strictly enforced.
> >
> > The CPU getting pegged is a huge problem because it is forcing us to restart
> > the server every some often.
> >
> > For now we have not been able to reproduce this error in a development
> > environment, any suggestions, or troubleshooting ideas?
> >
> > Jeremy
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.2 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.2
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: After 1 minute the Pagemap null is still locked
Posted by Igor Vaynberg <ig...@gmail.com>.
i think the only way this can happen is that you have something that
really takes longer then 1 minute to execute. i dont see how wicket
can take over your cpu....so may be it is that runaway process that
does that...
i think to debug it you might want to attach a profiler to the server
and wait for it to happen, take a cpu timing profile and see what was
going on during the spike...
does the message tell you who it is locked by? which page or
otherwise? if not that is possibly something we can improve also...
-igor
On Tue, Mar 18, 2008 at 1:06 PM, Jeremy Levy <je...@gmail.com> wrote:
> I am seeing the "After 1 minute the Pagemap null is still locked" error in
> production a couple of times a day for about the last week or so. We put in
> a major update to our site about 3 weeks ago, but only recently started
> seeing this error. I suspect they are related.
>
> From doing some research on the mailinglist it seems that this comes up when
> a user requests a new page while there is an open request still processing.
>
> http://www.nabble.com/pagemap-locking-to11350774.html#a11350774
>
> At the same time (or a few seconds before) the CPU is pegged at 100% and
> stays that way. Overtime the CPU usage progressively gets more and more
> backed up (I assume because this issue keeps happening and compounds the
> load).
>
> The longest page request on the site is a panel which has 4 child lazy
> loading panels but none of them take longer then a max of 4 seconds, which
> is pretty strictly enforced.
>
> The CPU getting pegged is a huge problem because it is forcing us to restart
> the server every some often.
>
> For now we have not been able to reproduce this error in a development
> environment, any suggestions, or troubleshooting ideas?
>
> Jeremy
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org