Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Configuring Jira Data Center with Netscaler as Load Balancer Edited

Hi All,

Could I ask for some advice from anyone who has successfully set up Jira Data Centre using Netscaler as the load balancer?

The problem we're having is that when a user successfully completes authentication on one of the nodes, they are quite often redirected to another node on a new anonymous session and asked to authenticate again. Basically, session stickiness isn't working.

We believe that the problem relates to how we've attempted to set up cookie-based session affinity as described in the installation instructions. In particular we're struggling with the description of the jira.node.id property in the cluster.properties file: "This unique ID must match the username and the BalanceMember entry in the Apache configuration".

We've not been able to find a direct equivalent of this in the configuration for Netscaler, so this is where we believe that the problem is occurring. We've just set this value to be the fully qualified host name of the node.

Our tests have shown that the for the JSESSIONID cookie, a new value is written to this after a successful authentication. In spite of the fact that we're appending the "node name" to the cookie by setting the -DjvmRoute startup parameter, as described in the example 2 of this documentation.

I think there has to be something we're missing in the Netscaler configuration that tells it how to route traffic to those node names.

So far we've managed to work around this by using source IP-based persistence instead, but since all of Atlassian's documentation seems to be geared up towards cookie based session affinity, we'd be quite keen to get this working.

Any suggestions on where we might be going wrong would be much appreciated.

 

Many thanks

Darren

 

1 answer

1 accepted

0 votes
Answer accepted

We've managed to fix this issue now. The nearest equivalent we can find to what is described in Atlassian's documentation is COOKIEINSERT, as described here.

This gives us a similar solution to that described in example 1 of the load balancer examples (Specific load balancing cookie).

 

I hope that helps someone else!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Data Center

Introducing Data Center Community licenses

I'm Alison Huselid, Head of Product for Data Center at Atlassian. As we shared in our last post, we’ve been working on a solution for those of you who work for charitable non-profit organizations tha...

3,606 views 26 83
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you