Please consider the example application created using JDeveloper 184.108.40.206.0
It has two pages that show session information and allow to invalidate the session and navigate from one to the other page.
It allows to reproduce the following scenario (sc1) :
- (sc1-a) run the sessionInfoA view in JDeveloper, which shows a session object String on the page (e.g. "weblogic.servlet.internal.session.MemorySessionData@cbaaf5b")
- (sc1-b) click the button "do invalidateSession and goSessionInfoB", which shows the sessionInfoB page with a different session object String (confirming we have a different session)
- (sc1-c) check the "IntegratedWebLogicServer - Log" panel in JDeveloper, showing the error
It also has a page that allows to login and logout which causes similar HttpSessionScopeAdapter errors to be logged.
It allows to reproduce the following scenario (sc2) :
- (sc2-a) run the loginInfo view in JDeveloper, which shows securityContext.userName as anonymous
- (sc2-b) click the login link, which shows the login page
- (sc2-c) login, e.g. using usergreen/welcome1 , which shows securityContext.userName no longer as anonymous (but e.g. usergreen) which confirms authentication
- (sc2-d) click the logout link, which shows securityContext.userName as anonymous
- (sc2-e) check the "IntegratedWebLogicServer - Log" panel in JDeveloper, showing the errors
- (q1) How can these HttpSessionScopeAdapter errors in (sc1) and (sc2), about 'Request is in an invalid state', be explained?