1 person found this helpful
if you have a support agreement with Oracle then you should be able to access the following Knowledge Article:
How ATG Session Management Works on WebLogic, JBoss, and WebSphere (Doc ID 1364857.1)
which explains in some detail how session management works with Oracle web Commerce.
In short the Application server is responsible for session creation and invalidation. The create and invalidate messages are reported back to Oracle Web Commerce by an
atg.servlet.SessionBindingReporter object (which implements the javax.servlet.http.HttpSessionBindingListener interface) which is added to each web application session as an attribute.It is this mechanism that handles session scoped component expiration.
As you know session timeout is web application specific so what you want to do seems to be breaking this rule. Have you ruled out using a request scoped component? Though without knowing exactly what your requirements are it is difficult to suggest an alternative approach.
Please mark the answer as helpful or correct if it assists.