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 <[email protected]>: > 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 > <[email protected]> wrote: >> You can kill it in Session but killing a thread will leave it in unknown >> state. >> >> ** >> Martin >> >> 2012/4/18 fachhoch <[email protected]>: >>> 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: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
