Win a copy of Functional Reactive Programming this week in the Other Languages forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

session cookie problem when UAT and production runs at same time by a user.

 
Raak Das
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We have a UAT and production application running on different port deployed in two separate weblogic servers..

http://localhost:7001/app1 for UAT

http://localhost:7002/app1 for production

UAT is replica of production.
The problem is user can’t use both at the same time in the same machine, because if you login in to one, will get log out from another(happens both in IE and firefox).
looks like session cookie in the browser is over written. I cant use different session cookie name since ear deployed in to both weblogic is same.Is there an another way to solve this issue ?
How can this be prevented. Content of weblogic.xml is below.
Is there any expamles or links for another solution Please help.

<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN" "http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
<session-descriptor>
<session-param>
<param-name>
CookieName
</param-name>
<param-value>
SESSIONID2
</param-value>
</session-param>
</session-descriptor>
<jsp-descriptor>
<jsp-param>
<param-name>
pageCheckSeconds
</param-name>
<param-value>
1
</param-value>
</jsp-param>
<jsp-param>
<param-name>
verbose
</param-name>
<param-value>
true
</param-value>
</jsp-param>
<jsp-param>
<param-name>
keepgenerated
</param-name>
<param-value>
true
</param-value>
</jsp-param>
<jsp-param>
<param-name>
precompile
</param-name>
<param-value>
false
</param-value>
</jsp-param>
<jsp-param>
<param-name>
printNulls
</param-name>
<param-value>
false
</param-value>
</jsp-param>
</jsp-descriptor>
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
</weblogic-web-app>


 
Deepak Pant
Ranch Hand
Posts: 446
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have faced this issue in our UAT and PROD environments for both IE and Firefox. The only way I know is to have different cookie names in the weblogic.xml file.

Simple way is to have @@ENV_NAME@@_JSESSIONID in the weblogic.xml file. Then using replace the value of @@ENV_NAME@@ with a prefix that you can read from properties file.

But this would mean two different EAR files for two environment.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic