Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Error on atlas-debug server app - Database: JIRA couldn't connect to your database

Hello everyone,


I'm trying atlas-debug for an existing JIRA plugin I have. Unfortunately, I'm getting:Screen Shot 2022-08-22 at 16.21.29.png

What I can find in atlassian-jira.log is:

2022-08-22 16:09:53,436+0300 main ERROR [c.a.config.bootstrap.DefaultAtlassianBootstrapManager] Couldn't open a connection on Datasource (java:comp/env/jdbc/JiraDS):
java.sql.SQLException: Cannot create PoolableConnectionFactory (General error: "java.lang.IllegalStateException: Unable to read the page at position 181694296676423 [1.4.200/6]" [50000-200])
at org.apache.tomcat.dbcp.dbcp2.BasicDataSource.createPoolableConnectionFactory(
at org.apache.tomcat.dbcp.dbcp2.BasicDataSource.createDataSource(
at org.apache.tomcat.dbcp.dbcp2.BasicDataSource.getConnection(
at com.atlassian.config.bootstrap.DefaultAtlassianBootstrapManager.getTestDatasourceConnection(
at com.atlassian.jira.config.database.JndiDatasource.getConnection(
at com.atlassian.jira.config.database.DatabaseConfig.testConnection(
at java.util.Iterator.forEachRemaining(
at java.util.Spliterators$IteratorSpliterator.forEachRemaining(
at com.atlassian.jira.startup.BootstrapContainerLauncher.start(
at com.atlassian.jira.startup.DefaultJiraLauncher.preDbLaunch(
at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$0(
at com.atlassian.jira.startup.DefaultJiraLauncher.start(
at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(
at com.atlassian.jira.startup.LauncherContextListener.initSlowStuffInBackground(
at com.atlassian.jira.startup.LauncherContextListener.contextInitialized(
... 8 filtered
at java.util.concurrent.Executors$
at org.apache.tomcat.util.threads.InlineExecutorService.execute(
at java.util.concurrent.AbstractExecutorService.submit(
... 12 filtered
at org.apache.tomcat.util.threads.InlineExecutorService.execute(
at java.util.concurrent.AbstractExecutorService.submit(
... 11 filtered
at java.lang.reflect.Method.invoke(
... 2 filtered
Caused by: org.h2.jdbc.JdbcSQLNonTransientException: General error: "java.lang.IllegalStateException: Unable to read the page at position 181694296676423 [1.4.200/6]" [50000-200]
at org.h2.message.DbException.getJdbcSQLException(
at org.h2.message.DbException.getJdbcSQLException(
at org.h2.message.DbException.get(
at org.h2.message.DbException.convert(
at org.h2.engine.Database.openDatabase(
... 2 filtered
at org.h2.engine.Engine.openSession(
at org.h2.engine.Engine.openSession(
at org.h2.engine.Engine.createSessionAndValidate(
at org.h2.engine.Engine.createSession(
at org.h2.engine.Engine.createSession(
at org.h2.engine.SessionRemote.connectEmbeddedOrServer(
at org.h2.jdbc.JdbcConnection.<init>(
at org.h2.jdbc.JdbcConnection.<init>(
at org.h2.Driver.connect(
at org.apache.tomcat.dbcp.dbcp2.DriverConnectionFactory.createConnection(
at org.apache.tomcat.dbcp.dbcp2.PoolableConnectionFactory.makeObject(
at org.apache.tomcat.dbcp.dbcp2.BasicDataSource.validateConnectionFactory(
at org.apache.tomcat.dbcp.dbcp2.BasicDataSource.createPoolableConnectionFactory(
... 73 more
Caused by: java.lang.IllegalStateException: Unable to read the page at position 181694296676423 [1.4.200/6]
at org.h2.mvstore.DataUtils.newIllegalStateException(
at org.h2.mvstore.MVStore.readPage(
at org.h2.mvstore.MVMap.readPage(
at org.h2.mvstore.MVMap.readOrCreateRootPage(
at org.h2.mvstore.MVMap.setRootPos(
at org.h2.mvstore.MVStore.openMap(
at org.h2.mvstore.MVStore.openMap(
at org.h2.mvstore.MVStore.removeMap(
at org.h2.engine.Database.handleUpgradeIssues(
at org.h2.engine.Database.openDatabase(
... 87 more
Caused by: java.lang.IllegalStateException: Unsupported type 17 [1.4.200/3]
at org.h2.mvstore.DataUtils.newIllegalStateException(
at org.h2.mvstore.type.ObjectDataType.newType(
at org.h2.mvstore.MVStore.readPage(
... 97 more
2022-08-22 16:09:53,489+0300 main ERROR [] JIRA couldn't connect to your database
2022-08-22 16:09:53,489+0300 main ERROR [] JIRA failed to establish a connection to your database.
This could be because:
- Your database isn't running
- The configuration of your dbconfig.xml file is incorrect (user, password, or database URL etc.)
- There is a network issue between JIRA and your database (e.g. firewall, database doesn't allow remote access etc.)

There are several other solutions you can try, review our documentation and see what works for you.

no other error written. Any ideas anyone?

2 answers

@Vladimir Yakimov It seems you have next in your pom.xml


 Which you added according to but it was generated for the previous versions of H2.

After we remove it we were able to start Jira using atlas-debug

0 votes

Welcome to the Atlassian Community!

The possible faults in the error message are all valid things that could cause this, but there is another one that is not listed.

You are using an h2 database.  This is a file and memory based database that is Atlassian use to get stuff up and running quickly when you're using a throw-away system.  It means you don't have to set up a proper database server every time you want to do a bit of development, a demo, or a quick test.

H2 databases are unsuitable for any system that you're not going to throw away in a few days.

They do not scale, and they have little fault tolerance.  If you've got a large Jira, or run out of memory, or you kill the Jira process without shutting it down, the database will fail, and it will fail catastrophically.  It's also prone to random corruptions that won't quite destroy it, but render it pretty much useless.

I suspect you've had a total failure.  

Your choices are to go look for a backup (either of the database files, or the regular XML files), or start clean.  (If you have a backup, you'll need to start with a clean install and restore the backup into it)

Thanks @Nic Brough _Adaptavist_ 


In my case the failure is on the very first start after building the app. So the h2 db is supposed to be created upon atlas-debug, so nothing to restore there. Or am I missing something? Furthermore for a quick debug h2 should be fine.




Yes, h2 is suitable for that, but it can fail at the point of creation!

Try deleting (well, moving to a safe place), the files under the jira home directory in the "database" directory.  This should make Jira try to recreate clean h2 files.

@Nic Brough _Adaptavist_ 


We are trying to migrate our plugin to Jira 9.x. And it's a big problem to debug it using: atlas-clean && atlas-debug

It works for Jira 8.x but not for Jira 9.x

Following error looks like misconfiguration between H2 driver and configuration XML db files 

Caused by: java.lang.IllegalStateException: Unsupported type 17 [1.4.200/3]

Jira 8.x has h2 version = 1.4.185, Jira 9.x has h2 version = 1.4.200

Could you provide any advise how to start Jira 9.x using atlas-debug.


P.S. atlas-run-standalone starts Jira 9.x without any issues.

I don't know why that might be happening, I've not tried to debug anything in Jira 9 code yet (the code I have looked at could be tested in standalone, it didn't need debugging at that level)

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Online AMA this week: Your project management questions answered by Jira Design Lead James Rotanson

We know that great teams require amazing project management chops. It's no surprise that great teams who use Jira have strong project managers, effective workflows, and secrets that bring planning ...

197 views 1 6
Read article

Atlassian Community Events