Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?

2012-06-14 Thread fachhoch
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

Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?

2012-06-14 Thread Martin Grigorov
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  

Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?

2012-06-14 Thread fachhoch
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:

Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?

2012-06-14 Thread Martin Grigorov
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

Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?

2012-06-14 Thread fachhoch
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

Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?

2012-06-14 Thread Martin Grigorov
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

Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?

2012-06-14 Thread Thomas Götz
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

Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?

2012-06-14 Thread fachhoch
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

Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?

2012-04-18 Thread fachhoch
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:

Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?

2012-04-18 Thread Martin Makundi
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

Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?

2012-04-18 Thread Igor Vaynberg
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

Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?

2012-04-18 Thread Martin Makundi
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

Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?

2012-04-18 Thread fachhoch
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:

Re: After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?

2012-04-18 Thread Doug Leeper
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

After 1 minute the Pagemap null is still locked by: Thread how to kill this request ?

2012-04-17 Thread fachhoch
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