You should use some asynchronous querying. In other words, you search is submitted to a background process and the Wicket request completes to some intermediary "please wait while we do your search" page (like all the big airline middlemen do).... It polls the background service to see if it's complete, and when it is, continues on.
You don't want page requests that literally take minutes. -- Jeremy Thomerson http://wickettraining.com *Need a CMS for Wicket? Use Brix! http://brixcms.org* On Sun, Apr 3, 2011 at 9:47 AM, fachhoch <fachh...@gmail.com> wrote: > we have a complex search screen , right now the query behind the search > is > not tuned , sometimes for different combinations search takes very long > time > and I get > > [raw] > Caused by: org.apache.wicket.WicketRuntimeException: After 1 minute the > Pagemap null is still locked by: Thread[[ACTIVE] ExecuteThread: '3' for > queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads], giving up > trying to get the page for path: 2 > [raw/] > > once I get this error then all links becomes non functional ,ie I click > on > the link nothing happens all my links are ajax links .only way to get rid > of > this error is kill the session ie kill the browser and open new browser . > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/fter-1-minute-the-Pagemap-null-is-still-locked-by-Thread-ACTIVE-tp3423610p3423610.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 > >
