Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

cannot start Confluence version 6.2 and later using atlas-run

Jan Revis
Contributor
May 28, 2019

I'm experiencing a problem using atlas-run when confluence 6.2 or later is used.  Shortly after the tomcat server starts, I see the following error in the logging output:

 

Unable to resolve name [com.atlassian.hibernate.dialect.HSQL2Dialect] as strategy [org.hibernate.dialect.Dialect]

 

I located an article at https://confluence.atlassian.com/confkb/upgrade-to-confluence-6-or-above-fails-when-using-the-embedded-database-917963158.html, which states I need to change 

com.atlassian.hibernate.dialect.HSQL2Dialect 

to

org.hibernate.dialect.H2Dialect

How do I get amps to use the  the correct H2?

 

1 answer

0 votes
Shannon S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 3, 2019

Hello Jan,

Thank you for contacting us.

Can you let me know what you mean when you ask how to get "amps" to use the correct H2? The H2 database information is stored in your Confluence data files. Thus, when you update confluence.cfg.xml, it will automatically be able to find your existing H2 information.

You will need to migrate to an external database as soon as you can. The embedded H2 database is only supported to work with Confluence instances currently in evaluation, and should not be used on a production instance or through upgrades/migrations.

Secondly, we've had two security advisories lately. In order to avoid your instance becoming compromised, it's recommended you upgrade as soon as you can to the latest versions. Below you can read about those advisories:

My colleague Daniel has written an FAQ on the subject, in case you have any questions:

Thank you for your understanding! Let me know if you have any issues.

Regards,

Shannon

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events