This content has been marked as final. Show 1 reply
Design is inappropriate.
Long running processes, and specifically reports, shouldn't rely on session connections.
Instead the following should be done.
- Process initiation (user request), post a task request to a task request queue. Return a unique identifier to requestor.
- Separate process processes tasks in the task queue.
- Requestor (such as a gui) periodically polls using the indentifier to see if the task is complete.
- When the task is complete the requestor asks for the results (GUI displays them.)
The problem with extending timeouts is that there are valid error scenarios where long timeouts will mean resources not returned to the system for long periods of time when they should have been.
Per your current solution there is probably some other timeout somewhere. Could be several. The JSP forum might be a better place to ask where all of the possible timeouts could be.