I did upgreade and I have problem, I do not know how to fix it ?:
JIRA failed to establish a connection to your database.
This could be because:
There are several other solutions you can try, review our documentation and see what works for you
Hi @Paweł Popławski ,
Easiest way to fix this is to look at your backup dbconfig.xml and copy that back to your directory.
In the current config you have it set up with the H2 database, is this intended or are you using PostgreSQL or MSSQL or... ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ola @Paweł Popławski ,
Could you send me log folder from <installation path>/logs & <application data path>/log also dbconfig.xml.
send via https://www.file.io/
let me check for you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
<?xml version="1.0" encoding="UTF-8"?>
<jira-database-config>
<name>defaultDS</name>
<delegator-name>default</delegator-name>
<database-type>h2</database-type>
<schema-name>PUBLIC</schema-name>
<jdbc-datasource>
<url>jdbc:h2:file:C:\Program Files\Atlassian\Application Data\Jira/database/h2db</url>
<driver-class>org.h2.Driver</driver-class>
<username>sa</username>
<password></password>
<pool-min-size>20</pool-min-size>
<pool-max-size>20</pool-max-size>
<pool-max-wait>30000</pool-max-wait>
<min-evictable-idle-time-millis>4000</min-evictable-idle-time-millis>
<time-between-eviction-runs-millis>5000</time-between-eviction-runs-millis>
<pool-max-idle>20</pool-max-idle>
<pool-remove-abandoned>true</pool-remove-abandoned>
<pool-remove-abandoned-timeout>300</pool-remove-abandoned-timeout>
</jdbc-datasource>
</jira-database-config>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For me it looks like default config. But it is also like magic for me :|.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hmm okay, but i'm not sure only dbconfig.xml. Could you @Paweł Popławski share more log files as we said before. Because we want to see which one something error we could tackle ?
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.
windows OS G:\atlassian\jira\log and G:\atlassian\application-data\jira\logs. compress 1 folder log and 1 folder logs into zip file and send to me.
if you're use linux
/opt/atlassian/jira/log and /var/atlassian/jira/logs. compress into zip file and send to me.
it depends where you installed jira path @Paweł Popławski
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
May you @Paweł Popławski repeat again to send that file because temporary file.io has been deleted?
it's ok, it's safe
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.
Thanks @Paweł Popławski , let's take a look in your logs says ;
11-Jan-2022 08:15:42.402 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ROOT] registered the JDBC driver [org.h2.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
11-Jan-2022 08:15:42.465 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ROOT] created a ThreadLocal with key of type [webwork.action.ActionContext$1] (value [webwork.action.ActionContext$1@167a1999]) and a value of type [webwork.action.ActionContext] (value [webwork.action.ActionContext@26225e03]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
Looks like your DB is not config correctly,
Is this Jira production or development ? because we cannot recommend the user use the H2 database. You should move into another database like Oracle, PostgreSQL, or SQL Server.
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.
This article may help you @Paweł Popławski https://confluence.atlassian.com/adminjiraserver/rolling-back-a-jira-application-upgrade-938846960.html .
In my personal experience, I will replace my snapshot Jira virtual server backup like a bread sandwich. it's pretty simple
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Bread and sandwich is not working:
We couldn't start the following plugins:
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.
I would like to summarize all that I have problem.
1. I can not upgreade Jira 8.7.1 to Jira 8.21.0.
2. I can not do that because of H2 database.
3. There is no way to do that or there is ?
Best regards Paweł.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.