Community Announcements have moved! To stay up to date, please join the new Community Announcements group today. Learn more
×we are rotating Database password with vault hourly and updating password in dbconfig.xml hourly. didn't restart application since first rotation, it happened 18 hours back. Application still working with out restart.
Any reason for this. How Atlassian Jira handles connections, when it kills old sessions, how long does it take to kill old sessions.
we are using datacenter 10.5 version
HI @Srikanth
Welcome. Why are you rotating the DB password every hour? Seems a bit frequent to have it change every hour.
I assume that since it's still running, the password must be still working with the database. Otherwise, no one can use the Jira system since every time a user navigate or tries to access...there will be a DB connection error.
@Benjamin we are planning to rotate passwords every week, for testing we rotated every hour, how application behaves.
when we are doping reindexing we are getting connection error but application behaving correctly except reindex part.
Can you suggest why its behaving like this.
when we verified Database Monitoring still 2 connections showing in pool since last 2 days.
anything changed in. data center version 10.5
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Seems a bit much though. It's not a typical production behavior to simulate for a test environment.
You may want to check the release notes to identify any related changes to what you are doing. Also, you may want to cross check the compatibility of your DB for version 10.5. Those are the areas I would check.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.