JIRA Fails to Start due to Invalid Database Configuration
Symptoms
JIRA fails to start, either after configuring a database or improper shutdown. The following appears in the logs:
Caused by: java.lang.UnsupportedOperationException: Database is locked
at org.ofbiz.core.entity.LockedDatabaseGenericDelegator.findByAnd(LockedDatabaseGenericDelegator.java:168)
at com.opensymphony.module.propertyset.ofbiz.OFBizPropertySet.getKeys(OFBizPropertySet.java:87)
at com.opensymphony.module.propertyset.AbstractPropertySet.getKeys(AbstractPropertySet.java:292)
at com.atlassian.jira.propertyset.PropertySetCache.bulkLoad(PropertySetCache.java:301)
at com.atlassian.jira.propertyset.JiraCachingPropertySet.init(JiraCachingPropertySet.java:834)
at com.opensymphony.module.propertyset.PropertySetManager.getInstance(PropertySetManager.java:45)
at com.opensymphony.module.propertyset.PropertySetManager.getInstance(PropertySetManager.java:22)
Cause
There are multiple causes for this issue. If installing a new database, entityengine.xml may be configured incorrectly. Alternatively, in rarer circumstances, the database may require repair.
Resolution
- JIRA is locked. See JIRA applications are locked.
- Check
entityengine.xml. Refer to the database-specific guide from Connecting JIRA to a Database. - If it's accurate, check your database vendor's guide on repairing tables. For example, see the MySQL guide for table repair.
Last modified on Mar 30, 2016
Powered by Confluence and Scroll Viewport.