I would be interested in the examples for performing the expensive operation on a separate thread and poll for completion of the operation from the client.
Thanks. -----Original Message----- From: robert.mcguinness [mailto:[email protected]] Sent: Wednesday, November 17, 2010 11:10 PM To: [email protected] Subject: Re: After 1 minute the Pagemap null is still locked by: Thread[[ACTIVE] typically this happens when your request takes too long to render. Wicket synchronizes components at the Pagemap (null is the default Pagemap name). This makes it easier to synchronize the front end with the backend at the cost of keeping requests synchronous. If you could explain the scenario more I can try and debug further. Some options: Render the UI as a resource. Resources are not synchronized If a component requires an expensive operation/calculation (ex: long db query), perform the expensive operation on a separate thread and poll for the completion of the operation from the client. I can provide examples if needed. Even if you return 10,000+ rows from the database rendering will be fast. Increase the lock time but I don't recommend since it kills the user experience and locks up server threads for longer than a minute if it's a DB query that is taking a long time, try and optimize the query If anyone finds my statements wrong please correct me -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/After-1-minute-the-Pagemap-nu ll-is-still-locked-by-Thread-ACTIVE-tp3047890p3048055.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]
