Re: WebFacing and dying IE sessions

Hi Mike!

The local sessions vanishes as in "disappearing without a trail". The application server still thinks everything is fine and so does the iSeries. That means that on the iSeries all QQFxxx jobs for that user are still running.

As one poster assumed - no it is not a timing issue. We covered that very carfully. iSeries has a 3 hours session limit, WAS 2 hours and on the client side we use a scripted timer that takes care of local session inactivity. Even if it was a timing issue we would at least get an WAS Application Error. That is not the case. And as I mentioned in my original post sometimes people work only 5 minutes or less before the described problem happened.

Even if a user accidently closed the entire IE window the regarding iSeries sessions would be terminated almost immediately.

As I said all WebFacing Apps are launched through an internal web portal. That portal is the parent window for a subsequent WebFacing app. If everything works fine and a user exits that application regularily he/she will land back at the portal.

When the session abnormally ends (vanishes) you find yourself back at the portal. You don't see any scripting errors or WAS Application Errors. If you press "back" in IE you'll return back to http://<whatever>//webfacing/WebFacing.do and straight into an Application Error.

To me it looks as if IE gets a problem interpreting a page and just terminates that child session abnormally. That means we're not getting a window.close event and the QQFxx job becomes a zombie.

Again ...

Does anyone have an idea how to trace or better prevent this issue?

Kind regards and many thanks in advance


Mit freundlichen Grüßen