The removeEntry NPE has been fixed, correct. But I wonder why the NPE causes the thread to stop and if not any other exception causes the thread to stop as well. Any ideas?
Juergen On 4/26/06, Ari Suutari <[EMAIL PROTECTED]> wrote: > Great ! I'll wait for next rc then. > > Ari S. > > ----- Original Message ----- > From: "Igor Vaynberg" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Wednesday, April 26, 2006 8:55 AM > Subject: Re: [Wicket-user] wicket hangs in Session.getPage (causes tomcat to > run out of threads !) > > > should already be fixed in trunk. > > -Igor > > > On 4/25/06, Ari Suutari <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > We have been preparing one part of our wicket application to production > > use. > > In testing there have been multple cases where whole application stops > > working and > > I think that we have now isolated to reason for this. > > > > One of my collegues noticed that there is a message on tomcat's log file: > > > > Apr 22, 2006 9:00:01 PM org.apache.tomcat.util.threads.ThreadPool logFull > > SEVERE: All threads (150) are currently busy, waiting. Increase > > maxThreads (150) or check the servlet status > > > > As 150 should be more than enough for current environment, he did some > > further > > research on issue, which shows that problem is related to case where > > end-user > > clicks a link on page before the page has completely rendered (users just > > do > > it and I think that it cannot be changed :-). > > > > When a link is clicked on page which hasn't fully rendered yet, following > > exception occurs: > > > > java.lang.NullPointerException > > at wicket.PageMap.removeEntry(PageMap.java:335) > > at wicket.PageMap.access(PageMap.java:628) > > at wicket.PageMap.get(PageMap.java:459) > > at wicket.Session.getPage(Session.java:395) > > at > > wicket.request.compound.DefaultRequestTargetResolverStrategy.resolveRenderedPage > > (DefaultRequestTargetResolverStrategy.java:149) > > at wicket.request.compound.DefaultRequestTargetResolverStrategy.resolve( > > DefaultRequestTargetResolverStrategy.java:92) > > at wicket.request.compound.AbstractCompoundRequestCycleProcessor.resolve( > > AbstractCompoundRequestCycleProcessor.java:48) > > at wicket.RequestCycle.step(RequestCycle.java:942) > > at wicket.RequestCycle.steps(RequestCycle.java:1034) > > at wicket.RequestCycle.request(RequestCycle.java:453) > > at wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:215) > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > > > > > > This wouldn't be a problem otherwise, but it seems that wicket does not > > recover > > from this situation, as the thread in tomcat is left waiting for like > > this: > > > > Name: http-80-Processor22 > > State: WAITING on [EMAIL PROTECTED] > > Total blocked: 7 Total waited: 5 > > > > Stack trace: > > java.lang.Object.wait(Native Method) > > java.lang.Object.wait(Object.java:474) > > wicket.Session.getPage(Session.java:386) > > > > wicket.request.compound.DefaultRequestTargetResolverStrategy.resolveRenderedPage > > (DefaultRequestTargetResolverStrategy.java:149) > > wicket.request.compound.DefaultRequestTargetResolverStrategy.resolve( > > DefaultRequestTargetResolverStrategy.java:92) > > wicket.request.compound.AbstractCompoundRequestCycleProcessor.resolve( > > AbstractCompoundRequestCycleProcessor.java:48) > > wicket.RequestCycle.step(RequestCycle.java:942) > > wicket.RequestCycle.steps(RequestCycle.java:1034) > > wicket.RequestCycle.request(RequestCycle.java:453) > > wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:215) > > javax.servlet.http.HttpServlet.service(HttpServlet.java:689) > > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > > > > The thread just sits there forever so tomcat creates a new thread to serve > > next thread and > > if the user does similar things again we run out of threads. > > > > This is occurring on wicket 1.2 rc2 and it is rather serious issue for us > > since > > I cannot figure any workaround for this. > > > > Ari S. > > > > > > > > ------------------------------------------------------- > > Using Tomcat but need to do more? Need to support web services, security? > > Get stuff done quickly with pre-integrated technology to make your job > > easier > > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > _______________________________________________ > > Wicket-user mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/wicket-user > > > > > > ------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
