Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?
I am still facing this problem root cause of my issues are database related, it takes time time to respond what can I do to avoid pagemap lock? can I set timeout for all my pages in a global way ? Please advice. I saw this post http://apache-wicket.1842946.n4.nabble.com/Removing-Pagemap-lock-post-1-5-td3387575.html I am using wicket 1.4.12 , using wicket 1.5.1 or above will resolve this problem? or is there any hack in wicket 1.4.xx Please advice. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/After-1-minute-the-Pagemap-null-is-still-locked-by-Thread-how-to-kill-this-request-tp4565091p4649966.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?
See org.apache.wicket.settings.IRequestCycleSettings#setTimeout() On Thu, Jun 14, 2012 at 11:50 AM, fachhoch fachh...@gmail.com wrote: I am still facing this problem root cause of my issues are database related, it takes time time to respond what can I do to avoid pagemap lock? can I set timeout for all my pages in a global way ? Please advice. I saw this post http://apache-wicket.1842946.n4.nabble.com/Removing-Pagemap-lock-post-1-5-td3387575.html I am using wicket 1.4.12 , using wicket 1.5.1 or above will resolve this problem? or is there any hack in wicket 1.4.xx Please advice. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/After-1-minute-the-Pagemap-null-is-still-locked-by-Thread-how-to-kill-this-request-tp4565091p4649966.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- 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
Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?
by default its supposed to timeout after 1 minute , but whenever my pagemap is locked only way to call new resource is close the browser relogin as if new session. Please advice me. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/After-1-minute-the-Pagemap-null-is-still-locked-by-Thread-how-to-kill-this-request-tp4565091p4649970.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?
In 1.5+ it should release the lock when your DB operation finishes. I guess it should be the same in 1.4.x. On Thu, Jun 14, 2012 at 4:32 PM, fachhoch fachh...@gmail.com wrote: by default its supposed to timeout after 1 minute , but whenever my pagemap is locked only way to call new resource is close the browser relogin as if new session. Please advice me. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/After-1-minute-the-Pagemap-null-is-still-locked-by-Thread-how-to-kill-this-request-tp4565091p4649970.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- 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
Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?
if my dboperation is pending and taking long time, there is now way I can call another resource ? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/After-1-minute-the-Pagemap-null-is-still-locked-by-Thread-how-to-kill-this-request-tp4565091p4649973.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?
run such slow operations in a separate thread in 1.5+ the lock is per page instance so you can just start a new page (i.e. remove the ?pageId ffrom the url) and all will be fine. In 1.4 I guess you need to use a different pageMap. The default pageMap is null. I.e. you need to provide a non-null one: ?wicket:pageMapName=blah On Thu, Jun 14, 2012 at 4:51 PM, fachhoch fachh...@gmail.com wrote: if my dboperation is pending and taking long time, there is now way I can call another resource ? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/After-1-minute-the-Pagemap-null-is-still-locked-by-Thread-how-to-kill-this-request-tp4565091p4649973.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- 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
Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?
Maybe you should think about an asynchronous approach, i.e. poll the state of your long-time-backend-operation e.g. by using an AjaxSelfUpdatingTimerBehavior. -Tom On 14.06.2012 at 15:51 fachhoch wrote: if my dboperation is pending and taking long time, there is now way I can call another resource ? - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?
I cannot run this in seperate thread becasue this could happen in anypage not just one page , all my pages uses db operations and for some reason once in a while some db operation takes time and the page is stuck.Please tell more on using a different pagemap . I encode all my urls. can I provide a link in my basepage through which this link is accessible to all pages ,can you provide me simple code waht should be called in onclick ? Thanks a lot for you support. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/After-1-minute-the-Pagemap-null-is-still-locked-by-Thread-how-to-kill-this-request-tp4565091p4649976.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?
If a page is stuck with this error , is there any way I can identify this and throw a RestartResponseAtInterceptPageException exception to error page ? I am using wicket 1.4.12 -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/After-1-minute-the-Pagemap-null-is-still-locked-by-Thread-how-to-kill-this-request-tp4565091p4568619.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?
You can kill it in Session but killing a thread will leave it in unknown state. ** Martin 2012/4/18 fachhoch fachh...@gmail.com: If a page is stuck with this error , is there any way I can identify this and throw a RestartResponseAtInterceptPageException exception to error page ? I am using wicket 1.4.12 -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/After-1-minute-the-Pagemap-null-is-still-locked-by-Thread-how-to-kill-this-request-tp4565091p4568619.html Sent from the Users forum mailing list archive at Nabble.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
Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?
its a servlet container thread, probably not safe to kill... maybe we can have implement a hard-evict from the store, and some strategy to handle these cases. -igor On Wed, Apr 18, 2012 at 11:42 AM, Martin Makundi martin.maku...@koodaripalvelut.com wrote: You can kill it in Session but killing a thread will leave it in unknown state. ** Martin 2012/4/18 fachhoch fachh...@gmail.com: If a page is stuck with this error , is there any way I can identify this and throw a RestartResponseAtInterceptPageException exception to error page ? I am using wicket 1.4.12 -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/After-1-minute-the-Pagemap-null-is-still-locked-by-Thread-how-to-kill-this-request-tp4565091p4568619.html Sent from the Users forum mailing list archive at Nabble.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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?
We got some of these because of: - database deadlocks (unsorted race situation) - non-threadsafe access to hashmaps (hashmap/treemap has cool possibility to hang when used from multiple threads without synchronization) - excplicit lock bugs (reentrantlocks) I recommend to debug by displaying the stacktrace of the hanged thread. This can be achieved manually or via kill -3. ** Martin 2012/4/18 Igor Vaynberg igor.vaynb...@gmail.com: its a servlet container thread, probably not safe to kill... maybe we can have implement a hard-evict from the store, and some strategy to handle these cases. -igor On Wed, Apr 18, 2012 at 11:42 AM, Martin Makundi martin.maku...@koodaripalvelut.com wrote: You can kill it in Session but killing a thread will leave it in unknown state. ** Martin 2012/4/18 fachhoch fachh...@gmail.com: If a page is stuck with this error , is there any way I can identify this and throw a RestartResponseAtInterceptPageException exception to error page ? I am using wicket 1.4.12 -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/After-1-minute-the-Pagemap-null-is-still-locked-by-Thread-how-to-kill-this-request-tp4565091p4568619.html Sent from the Users forum mailing list archive at Nabble.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 - 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
Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?
here is stack trace , with this please help me identify the thread causing the lock, my applciation is deployed in weblogic. I assume once the thread is identified I have to use weblogic admin console to kill this particular thread ? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/After-1-minute-the-Pagemap-null-is-still-locked-by-Thread-how-to-kill-this-request-tp4565091p4568715.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?
There are a lot more threads that are running within a Weblogic container. The thread you are showing is not the thread that is creating the lock. It is the thread that is indicating the page map is locked. Also, I don't believe there is a way to kill a particular thread in weblogic. It only shows the threads in use with little or no management capability. Consequently, not sure how you would be able to kill a thread -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/After-1-minute-the-Pagemap-null-is-still-locked-by-Thread-how-to-kill-this-request-tp4565091p4569113.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?
I need to handle this , I know this is asked several times in forums , the solutions suggested I cannot apply as this happens once in while and I dont have steps to reproduce this , this happens in page 1 , page2 etc , but not always in page1 or page2 , its happens if database for some reason taking time for the query the page is using, the problem I face with this is none of my other links work , all links get stuck , only a new session will work good, user will close and start a new browser to over come this problem, I need advice if I can globally handle this , I want to show an error page and tell wicket it need not wait for the page map to fulfill the request and complete the request by sending the error page. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/After-1-minute-the-Pagemap-null-is-still-locked-by-Thread-how-to-kill-this-request-tp4565091p4565091.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
