Jira Server session conflict with Confluence Server

[Diego Villagra]

We have installed JiraServer and ConfluenceServer versions on the same Windows Server running over different Ip ports. 

When a browser client try to use both applications at the same time the sessions closes automatically, all the time. 

It seems that something about the session manager is in a conflict. But when we use the applications in different times (not simultaneously) the applications and sessions works perfectly.

is there some recommendations about this kind of configuration?

[Nic Brough -Adaptavist- · Accepted solution]

Could you tell us four things please?

1. The url you access Jira on
2. The url you access Confluence on
3. The base url set in Jira
4. The base url set in Confluence

Please obscure the domain(s) you've got in those, but let us know whether they are the same or different.  If, for example your answers for 1 and 4 would be http://ourdomain.org/jira and http://anotherdomain.org/confluence, then please tell us http://domain1.org/jira and http://domain2.org/confluence

[Diego Villagra]

Thanks for you reply

1. http://server.apcor.com.ar:8080 (jira)

2. http://server.apcor.com.ar:8090 (confluence)

3. the url base is configured with the correct (1)

4. the url base is configured with the correct (2)

is there any recommended configuration? to do it?

[Nic Brough -Adaptavist-]

Ok, that rules out a lot of stuff, but very much rules in the problem I suspect!

A lot of Java based web applications run with session cookies (called Jsession cookies if you want to go digging for them in your browser), and these are locked to the domain and url, not the port.  So the sessions for each application are both locked to http://server.apcore.com.ar and hence interfering.

Three solutions:

1.  Run the apps on different contexts -for example  http://server.apcore.com.ar:8080/jira and http://server.apcore.com.ar:8090/confluence

2.  A variation on 1, get a proxy in place and run them without ports at all - http://server.apcore.com.ar/jira and http://server.apcore.com.ar/confluence

3. (I think Jira is the same as this, but it's always felt easier in Confluence), nip on to the Confluence server, find the <confluence install>/conf/context.xml file and edit it.  Find the "context" tag and add to it (note - do NOT add a new context) so that; 

<Context sessionCookieName="CONFLUENCESESSIONID">

Then restart Confluence.  This should separate out the jsessions for everyone, although some of your people may need to go through one more "it's logged me out of the other one" cycle to clear out the old sessions.