My Wicket app occasionally "freezes" on making an Ajax submit that invokes a potentially lengthy database operation. My theory is that the database work is taking longer than Wicket allows, & the Ajax call times out. I'm guessing that the browser does not detect this timeout, so my "Please Wait" message continues to be displayed, making the user think he will eventually get an answer from the server. However, in these cases, no matter long he waits (up to many minutes), no reply is ever forthcoming.
Before I invest a lot of time trying to FIX this problem, is there a way to determine that an Ajax timeout actually IS the problem? Also, does anyone know what Wicket's default Ajax timeout interval is? I looked over the Javadocs for the various Wicket Ajax classes, but none of them seemed to address this particular issue. Any advice or pointers would be greatly appreciated! ** This email and any attachments may contain information that is confidential and/or privileged for the sole use of the intended recipient. Any use, review, disclosure, copying, distribution or reliance by others, and any forwarding of this email or its contents, without the express permission of the sender is strictly prohibited by law. If you are not the intended recipient, please contact the sender immediately, delete the e-mail and destroy all copies. **
