On a customer site, one of the users complained about being kicked out each time he wanted to create new documents in D2. This issue is happening in a default deployment of D2 and D2Config in a WebLogic Domain.We found out that the user sessions for D2Config and D2 are conflicting together.
This issue occurs if D2Config and D2 applications are opened in the same browser using different TABs and if the user is navigating from D2 to D2Config and vice versa.
The error message is misleading as it shows a session time out and the user just signed in .
Using a HTTP Header tracing tool, we saw that the JSESSIONID cookie which is the cookie storing the HTTP Session for the Java applications is changing when switching from one application to the other. This showed us that both Java Application were using the same session cookie which conduct to session lost.
Workaround or Fix:
An easy fix for this is to update the D2 weblogic.xml file included in the D2.war file with a section defining a new session cookie name as shown below:
<session-descriptor> <cookie-name>JSESSIONID_D2</cookie-name> <cookie-http-only>false</cookie-http-only> </session-descriptor>
To proceed, follow the steps below:
- Extract the weblogic.xml file from the war file
mkdir mytemp cd mytemp -- Put the D2.war file here jar xvf D2.war WEB-INF/weblogic.xml
- Edit the file and add the session-descriptor bloc above just after the Description closing TAG.
- Update the D2.war file with the new weblogic.xml
jar uvf D2.war WEB-INF/weblogic.xml
- And finally redeploy the D2.war file to the WebLogic Server.
This fix has been submitted to and validated by EMC support.