Session frequently timed out

When I try to do some actions in JIRA (v5.0.1), for example:

  • Save a new filter
  • Bulk edit of some issues
  • many more

Session expires after a few seconds (seems like 3) and basically I can't do them. Note that I've also checked the "Remember me" checkbox logging in. I've tried to change the default timeout to "3000" but without success. Unfortunately, some necessary features are nearly unusable because of this problem.

Here is a couple of lines from the log file that are maybe relevant:

2012-10-01 11:07:06,355 http-8080-15 WARN <MY_USERNAME> 667x19093x2 g411ns <MY_IP> /secure/views/bulkedit/BulkChooseOperation.jspa [action.issue.bulkedit.BulkChooseOperation] Bulk edit bean unexpectedly null. Perhaps session was lost (e.g. when URL used is different to base URL in General Configuration)?
2012-10-01 11:10:35,474 http-8080-1 WARN <MY_USERNAME> 670x19142x3 1438g2d <MY_IP> /plugins/servlet/gadgets/makeRequest [http.impl.client.DefaultRequestDirector] Authentication error: Unable to respond to any of these challenges: {oauth=WWW-Authenticate: OAuth realm="http%3A%2F%2F<SERVER_IP>%3A8090", oauth_problem="consumer_key_unknown"}

Note that base URL used is the same configured in General Configuration.

On the same server are also installed Confluence and Bamboo, and the same problem applies to them too. For example, when I edit a page in Confluence I have to save it 2-3 times because the sessions seems expired.

2 answers

1 accepted

How have you got your instances set up? port numbers and contexts? You may be suffering from the cookies overwriting each other from the different servers.

It's been talked about here as well. It's two Jira instances the : https://answers.atlassian.com/questions/15477/logging-into-one-instance-of-jira-logs-me-out-of-a-second-instance

https://confluence.atlassian.com/display/DOC/Installing+Confluence+and+JIRA+Together

https://jira.atlassian.com/browse/JRA-11915

if all your apps are just on different ports and all on the root context ('/') then you will need to move them to different contexts

e.g.

  • server.com:8080/jira
  • server.com:8081/confluence

Thank you very much!

I apologize, Manuel, can you please confirm that using contexts completely solve this issue. Thanks for answer and have a good day.

Yes, I confirm that contexts completely solved the problem.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published yesterday in Jira

Mission-critical battery manufacturer fulfills FAA software requirements with Commit Policy Plugin

EaglePicher Technologies is a leading manufacturer of battery systems for diverse industries like defense, aviation, space or medical. As they operate in highly regulated industries, keeping a clear ...

127 views 0 2
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you