Another update, the LoginAction in Context2 had the below methods, two methods
to set the request. May be I have done RequestAware and then realized it should
be ServletRequestAware and did not
delete the setRequest method. I think having the setRequest is the culprit for
the invalid session
We use the path as / for the cookie path that allows the session to be shared
between context1 and context2. The JSESSIONID also remains the same when the
request is forwarded.
Martin asked me if we the action is session aware. It was not implementing
SessionAware interface even though session
On 5/16/2018 7:23 PM, Prasanth Pasala wrote:
> Exception: java.lang.IllegalStateException: UT10: Session is invalid
> r4yb7BtBx7fwmGbzMhgeyhvSFb3sAp6FhW6m-5Op
> at
> io.undertow.server.session.InMemorySessionManager$SessionImpl.getAttribute(InMemorySessionManager.java:481
> at
>
Martin,
We have the cookie config in the application.
20
/
true
true
Thanks,
Prasanth
On 05/15/2018 04:03 PM, Martin Gainty wrote:
>
> 8443 indicates secure connection so perhaps a
Below is a complete stack trace.
Exception: java.lang.IllegalStateException: UT10: Session is invalid
r4yb7BtBx7fwmGbzMhgeyhvSFb3sAp6FhW6m-5Op
at
io.undertow.server.session.InMemorySessionManager$SessionImpl.getAttribute(InMemorySessionManager.java:481
at
5 matches
Mail list logo