• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

How to set Session tracking cookie other than in weblogic.xml

 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Is there any other method to set session tracking cookie name (set dynamically when application loads) than configure in weblogic.xml.
We have same application deployed in different weblogic server for testing. Each application (same ear file) runs as http:/domainName/port1,
http:/domainName/port2 , http:/domainName/port3 like that. Jdbc Conection pools is configured different for each.
When some body try to login to more than one there is a session conflict. It is not practical to put separate cookie name in each ear file ,
since it is all build once.
So I am looking for a method to set session tacking cookie outside weblogic.xml. so when application loads cookie name will be generated.
Or is there anything in config.xml that I can do so each ports run with out any session conflicts. Each ports may be logged in by different id.
Servlet vertion using is 2.3
Weblogic werver 8.1
please hlep.
 
Bartender
Posts: 6663
5
MyEclipse IDE Firefox Browser Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Welcome to JR Raak.

Your question is confusing. By 'port' I think you meant to say application. And what you seem to want is a single sign on solution, but you also mention that different IDs may be used to login to each application.

The session tracking cookie maintained by java is JSESSIONID. You cannot configure this anywhere. It is up to the container to generate a JSESSION ID and associate it with an application for any given login
 
Raak Das
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks Deepak for your reply. sorry that my question is confusing. I understand that session tracking cookie can be set in weblogic.xml.
we have non clustered servers on same domain. So i am login in to one application and in between try to start another application the first one get logged out.
If I open only one at a time it is all fine. or another option is i have to open application in 2 different browsers. if i start on in IE and another in firefox everything is fine.

so is there a way to solve this - other than specifying different session cookie name in weblogic.xml .


Thank you so much for your time.
 
Deepak Bala
Bartender
Posts: 6663
5
MyEclipse IDE Firefox Browser Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

So i am login in to one application and in between try to start another application the first one get logged out.



That is a sign that something is wrong. Your application should not log you out just because you started / logged into another application
 
Every snowflake is perfect and unique. And every snowflake contains a very tiny ad.
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic