Our JIRA instance is using one of our production Oracle databases, along with other support services. From time to time the DBA's need to restart that database. As a result, the open db connections start throwing broken pipe errors. It appears that JIRA (probably Tomcat) closes these as they throw errors with use and open new connections. As a pro-active measure, we have restarted JIRA to clean these connections out. We would rather leave the JIRA instance alone and only address refreshing the connection pool. I am not seeing anything in JIRA to do this. Also, I am reluctant to go poking around in that Atlassain configured Tomcat install without some Atlassain documentation to back up this approach. (unless someone else has already) Ideally, we are looking for a CLI answer and possibly cron this task.
Thanks, I see that now. And I see the same thing for Confluence, and I will use that there too. This feautre lines up with the behaviour we were seeing were the 'bad' connections seem to dissapear over time. With this, the user never sees an error.
It is no fault of the DBA's as they are under the same artifical constructs created by the archetypal obstinance of management as the rest of us.
Hrm, so they say.
There is a cost to this. Indexing on my oracle instance takes 3 hours without the validation query, and 4 hours with. In a 2 hour period during the indexing, the validation query was seen to run 4 billion times. Unless you have very low latency you are going to feel the effects of that.
Anyway, last weekend I moved from oracle to postgres, and now it's all gravy. Annoyingly though, I see Atlassian are just starting to fix some of the oracle-specific bugs.
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot