inconistent session time-out,cookie name change is not a option
posted 4 years ago
I had 2 applications with same cookie name 'JSESSIONID' running on 2 different nodes of a Websphere Application Sever 6.1,my applications are not compatible for a change cookie name.Is there a way I can resolve.
Both app1 and app2 has same cookie name and running on same domain,so the browser is not able to differentiate between the cookies I reckon,session time out happens only sometimes the behaviour is not consistent.
Both my applications needs a separate login and are accessed from different browser windows using https.The way access the applications
eg : https://domainName.com/app1 https://domainName.com/app2
After googling I found the below possible approaches,
1)Change the cookie name(Which I can't)
2)Changing the path name at cookie level for both my applications
I don't know whether I can apply the same to my scenario.In case if I can apply this do I need create a custom property HttpSessionIdReuse at both the server nodes.
In this case does the session object contains the data set by both the applications.Can anyone through some light how this works or is there any better solution to this problem.