Forums

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

Jira doesn't open due to error shown below

Fondazione09
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 16, 2020

Hi all,

hope someone can help. We used Jira for more than 2 years. From days now we are not able to open it due to the following error:

 

Setup: Your memory allocation pool settings need attention

JIRA runs in a Java virtual machine (JVM), and this JVM is allocated an amount of memory to enable JIRA to run. These amounts can be manually configured.

 

  • The initial memory allocation pool (-Xms) is recommended to be at least 384m.

 

Maggiori informazioniDescrizioneTempoLivelloEccezione

Unexpected exception during JIRA startup. This JIRA instance will not be able to recover. Please check the logs for details
2020-07-15 11:54:35fatalcom.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:DELETE FROM PUBLIC.rundetails WHERE START_TIME < ? (General error: "java.lang.NullPointerException"; SQL statement: DELETE FROM PUBLIC.rundetails WHERE START_TIME < ? [50000-185]) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.removeByCondition(DefaultOfBizDelegator.java:144) at com.atlassian.jira.ofbiz.WrappingOfBizDelegator.removeByCondition(WrappingOfBizDelegator.java:136) at com.atlassian.jira.entity.Delete$DeleteWhereContext.execute(Delete.java:154) at com.atlassian.jira.entity.EntityEngineImpl.delete(EntityEngineImpl.java:55) at com.atlassian.jira.entity.Delete$DeleteWhereContext.execute(Delete.java:136) at com.atlassian.jira.scheduler.OfBizRunDetailsDao.purgeHistory(OfBizRunDetailsDao.java:130) at com.atlassian.jira.scheduler.OfBizRunDetailsDao.start(OfBizRunDetailsDao.java:70) at com.atlassian.jira.scheduler.JiraCaesiumSchedulerService.startRunDetailsDao(JiraCaesiumSchedulerService.java:71) at com.atlassian.jira.scheduler.JiraCaesiumSchedulerService.startImpl(JiraCaesiumSchedulerService.java:35) at com.atlassian.scheduler.core.AbstractSchedulerService.start(AbstractSchedulerService.java:180) at com.atlassian.jira.scheduler.JiraSchedulerLauncher.proceedIfAllClear(JiraSchedulerLauncher.java:36) at com.atlassian.jira.scheduler.JiraSchedulerLauncher.start(JiraSchedulerLauncher.java:22) at com.atlassian.jira.startup.ActiveServicesLauncher.start(ActiveServicesLauncher.java:56) at com.atlassian.jira.startup.DefaultJiraLauncher.postDBActivated(DefaultJiraLauncher.java:170) at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postDbLaunch$2(DefaultJiraLauncher.java:144) at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:304) at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(DatabaseConfigurationManagerImpl.java:199) at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:135) at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$0(DefaultJiraLauncher.java:102) at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31) at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:100) at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:154) at java.lang.Thread.run(Thread.java:745) Caused by: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:DELETE FROM PUBLIC.rundetails WHERE START_TIME < ? (General error: "java.lang.NullPointerException"; SQL statement: DELETE FROM PUBLIC.rundetails WHERE START_TIME < ? [50000-185]) at org.ofbiz.core.entity.jdbc.SQLProcessor.executeUpdate(SQLProcessor.java:570) at org.ofbiz.core.entity.GenericDAO.deleteByCondition(GenericDAO.java:1238) at org.ofbiz.core.entity.GenericHelperDAO.removeByCondition(GenericHelperDAO.java:244) at org.ofbiz.core.entity.GenericDelegator.removeByCondition(GenericDelegator.java:1370) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.removeByCondition(DefaultOfBizDelegator.java:142) ... 22 more Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.NullPointerException"; SQL statement: DELETE FROM PUBLIC.rundetails WHERE START_TIME < ? [50000-185] at org.h2.message.DbException.getJdbcSQLException(DbException.java:345) at org.h2.message.DbException.get(DbException.java:168) at org.h2.message.DbException.convert(DbException.java:295) at org.h2.command.Command.executeUpdate(Command.java:262) at org.h2.jdbc.JdbcPreparedStatement.executeUpdateInternal(JdbcPreparedStatement.java:157) at org.h2.jdbc.JdbcPreparedStatement.executeUpdate(JdbcPreparedStatement.java:143) at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:98) at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:98) at org.ofbiz.core.entity.jdbc.SQLProcessor.executeUpdate(SQLProcessor.java:562) ... 26 more Caused by: java.lang.NullPointerException at org.h2.mvstore.db.MVPrimaryIndex.getRow(MVPrimaryIndex.java:215) at org.h2.mvstore.db.MVTable.getRow(MVTable.java:394) at org.h2.mvstore.db.MVSecondaryIndex$MVStoreCursor.get(MVSecondaryIndex.java:490) at org.h2.index.IndexCursor.get(IndexCursor.java:260) at org.h2.table.TableFilter.get(TableFilter.java:449) at org.h2.command.dml.Delete.update(Delete.java:74) at org.h2.command.CommandContainer.update(CommandContainer.java:78) at org.h2.command.Command.executeUpdate(Command.java:254) ... 31 more

Jira server is in a Virtual Machine (VmWare); we tried to increase the memory but the error remains the same. I found a post from the community that seems to be very similar and the answer was to drop "rundetails" and create it againg. We have Embedded H2 Database but I'm not an expert with this kind of DB so, assuming this could be the solution, I know how to drop the table but I don't know how to re-create it.

Can someone Help me?

Thanks in Advance

1 answer

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 16, 2020

I'm afraid dropping and recreating the table is unlikely to help you here.   I suspect your database is damaged,as h2 is known to fail without warning.

If you do want to try recreating it, then the definition is below

Column Type Not Null Default Constraints 
id numeric(18,0)  NOT NULL  Primary Key
job_id character varying(255)
start_time timestamp with time zone
run_duration numeric(18,0)
run_outcome character(1)
info_message character varying(255)

 If that does not help, then I'd be looking for the latest backup.

Julian C_
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 7, 2021

Can you explain how did you open the database?
I'm getting the error below:

File corrupted while reading record: null. Possible solution:
use the recovery tool [90030-197]

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events