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-t
Try hitting the servlet container (tomcat/jetty) direct instead of going
through the apache proxy. Do you still see the issue?
If the issue doesn't occur when hitting direct, you've isolated the problem
as an apache proxying issue. It's now time to start inspecting the HTTP
traffic in both cases.
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-tp5716584p571
