Are you saying that (8000 DB2 calls/connections + 2000 IMS calls through IMF transactions + normal validation routine) per session can not normally take 30-40 min??? I am not saying that. I have absolutely no idea what is normal for your app, and what is not.
It might be written in your project requirements. Or might be not, and now the customer might be willing to add something
I think that changing the session timeout while you are investigating the issue might be useful.
I have thought that the problem is not a bug, but my poore design. As far as I understood, you have a performance issue, right?
I would suggest you to find out what causes those ocasional performance degradations, and then decide
whether it requires a redesign, or a simple code change to resolve it.
Or you might find out that it's Ok to simply set a longer session timeout in your web-server configuration file,
and the problem (as you have described it) will go away.
Unfortunattelly, in my practice this application is one of a kind and I can not compare the time it runs to the other apps. You can compare performance of your app against your customer's needs (present and/or future). If you find out that performance
needs improvement, then you better start thinking right now on how it could be improved
I would start with discovering most
time-greedy operations
Thanks for the advice to track the timestamps - I will definatelly try that. Good luck