aspose file tools*
The moose likes Websphere and the fly likes inconistent session time-out,cookie name change is not a option Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Soft Skills this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "inconistent session time-out,cookie name change is not a option" Watch "inconistent session time-out,cookie name change is not a option" New topic
Author

inconistent session time-out,cookie name change is not a option

premchand chand
Greenhorn

Joined: May 07, 2008
Posts: 6
Dear Ranchers,

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

3)http://www-01.ibm.com/support/docview.wss?uid=swg21210881&wv=1
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.



thanks in advance
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: inconistent session time-out,cookie name change is not a option