I have two projects, one a standard Web application the other Web services application using Chained IOs. I am testing in WAS 7.0 by exporting the EAR file and installing via the WAS console. After installing I set the session-timeout to 4 minutes. Now I test the session timeout.
I connect with the standard Web application and wait. The session times out after 4 minutes and the session cleaned up.
I use the Web Services Explorer and run the FIC to log on. I wait, and wait and wait. I wait 15 minutes and the session is still active. In a previous test I waited in excess of 30 minutes and the session did not terminate.
Question, what is happening that causes WAS to ignore the idle session timeout for Web Services using chained IOs?