On Mar 1, 2007, at 1:25 PM, luv2hike wrote:
I am trying to do a seemingly simple thing, but have run into
issues. I have
a single instance of Resin running 2 different web apps that have
nothing to
do with each other except for running on the same server. If a
user logs
into appA then opens a new browser window or tab and logs into
appB, appA's
session is lost as the session cookie is common to both apps. What
I need
is a way to change JSESSIONID to something unique for each app.
Starting
another instance of Resin is not desired due to RAM and OS/X
service startup
issues.
Can this be done? Or is there another way with one instance of
Resin to
support simultaneous but independent sessions in 2 or more web apps?
I think we might be able to add that capability. It would look like:
session-config
session-cookieAPP2/session-cookie
There might be a few complications in implementing it, since the load-
balancer only understands a single cookie. So we might need to
generate an APP2 cookie as well as a JSESSIONID cookie, where the
JSESSIONID is used for sticky-sessions.
-- Scott
--
View this message in context: http://www.nabble.com/trouble-with-
session-cookie-and-multiple-apps-tf3329855.html#a9258847
Sent from the Resin mailing list archive at Nabble.com.
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
