Active database connections are not expected to close. Only inactive database connections will eventually be closed. If an end user were to forcibly close a database connection, this would likely cause a failure in the Jira application itself. Jira is expected to manage its own database connection pool, and it does that.
There is not a means to force the active database connections to close short of restarting Jira. However I would suggest taking a closer look at our guide in Tuning database connections. Please read this document before you make any changes.
That said, it does explain how you can adjust certain settings in the dbconfig.xml file in order to change various settings in regards to how Jira manages its database connections.
To try to answer your second question, there is not a clear delineation between which user caused a database connection(s) to open and the connections Jira has open. If Jira opens these connections, it is because it currently has the need to read/write data to and from the database. You might be able to get some more clues about which thread or class of code is actively working at a given time by Generating a thread dump. This could give you some clues as to why Jira might suddenly spike in database connections, but you would have to generate the thread dump during the spike itself in order to try to see which pieces of the code might be seeking numerous database connections. It becomes significantly more difficult to figure out which specific user might have caused connections to happen through that code.
So my question to you is, why do you want to be able to terminate the active connections?
Are you seeing some kind of performance problem on Jira or MS SQL that relates to this?
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.