FYI, I suspect that the session id is not being proxied (either via a cookie
or via the URL) which causes a user to start a new session rather than
re-using their existing session.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Base-page-action-with-null-session-object
c in both cases. Keep an eye out for request / response headers that
are not being proxied through apache.
It sounds like this issue might be off topic for this list and a more
general apache config issue.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Base-page-action-wi
Is your prod environment a cluster? If yes, have you enabled sticky sessions?
Is your servlet container behind an apache proxy? Any suspect rules we
should be aware of?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Base-page-action-with-null-session-object
ivate() {
if (!isUserWorkspaceExists()) {
//handle timeout
}
}
}
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Base-page-action-with-null-session-object-tp5716584.html
Sent fro
