Confluence Server doesn't start after upgrade 6.14.0->6.15.3
Asked by OVANES OGANYAN:

I have an error in atlassian-confluence.log after upgrade

```
2019-04-29 16:21:43,333 ERROR [Catalina-utility-1] [atlassian.confluence.plugin.PluginFrameworkContextListener] launchUpgrades Upgrade failed, application will not start: com.atlassian.config.ConfigurationException: Cannot update schema
com.atlassian.confluence.upgrade.UpgradeException: com.atlassian.config.ConfigurationException: Cannot update schema
at com.atlassian.confluence.upgrade.AbstractUpgradeManager.upgrade(AbstractUpgradeManager.java:135)
at com.atlassian.confluence.plugin.PluginFrameworkContextListener.launchUpgrades(PluginFrameworkContextListener.java:119)
at com.atlassian.confluence.plugin.PluginFrameworkContextListener.contextInitialized(PluginFrameworkContextListener.java:79)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4682)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5150)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1377)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1367)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Unknown Source)
Caused by: com.atlassian.config.ConfigurationException: Cannot update schema
at com.atlassian.confluence.impl.core.persistence.hibernate.schema.ConfluenceSchemaHelper.validateSchemaUpdateIfNeeded(ConfluenceSchemaHelper.java:117)
at com.atlassian.confluence.upgrade.impl.DefaultUpgradeManager.validateSchemaUpdateIfNeeded(DefaultUpgradeManager.java:73)
at com.atlassian.confluence.upgrade.AbstractUpgradeManager.upgrade(AbstractUpgradeManager.java:120)
... 14 more
Caused by: org.hibernate.boot.model.naming.IllegalIdentifierException: Identifier text should not contain quote markers (` or ")
at org.hibernate.boot.model.naming.Identifier.<init>(Identifier.java:110)
at org.hibernate.boot.model.naming.DatabaseIdentifier.<init>(DatabaseIdentifier.java:23)
at org.hibernate.boot.model.naming.DatabaseIdentifier.toIdentifier(DatabaseIdentifier.java:30)
at org.hibernate.tool.schema.extract.internal.InformationExtractorJdbcDatabaseMetaDataImpl.getIndexes(InformationExtractorJdbcDatabaseMetaDataImpl.java:734)
at org.hibernate.tool.schema.extract.internal.TableInformationImpl.indexes(TableInformationImpl.java:122)
at org.hibernate.tool.schema.extract.internal.TableInformationImpl.getIndex(TableInformationImpl.java:138)
at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.findMatchingIndex(AbstractSchemaMigrator.java:340)
at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.applyIndexes(AbstractSchemaMigrator.java:324)
at org.hibernate.tool.schema.internal.IndividuallySchemaMigratorImpl.performTablesMigration(IndividuallySchemaMigratorImpl.java:84)
at com.atlassian.confluence.impl.hibernate.ConfluenceHibernateSchemaManagementTool$3.performTablesMigration(ConfluenceHibernateSchemaManagementTool.java:110)
at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.performMigration(AbstractSchemaMigrator.java:203)
at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.doMigration(AbstractSchemaMigrator.java:110)
at org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:87)
at org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:58)
at com.atlassian.confluence.impl.core.persistence.hibernate.schema.ConfluenceSchemaHelper.validateSchemaUpdateIfNeeded(ConfluenceSchemaHelper.java:114)
... 16 more
2019-04-29 16:21:43,341 ERROR [Catalina-utility-1] [atlassian.confluence.plugin.PluginFrameworkContextListener] launchUpgrades 1 errors were encountered during upgrade:
2019-04-29 16:21:43,341 ERROR [Catalina-utility-1] [atlassian.confluence.plugin.PluginFrameworkContextListener] launchUpgrades 1: Cannot update schema
```


Answers:
author: Diego
body: Hello there!

Ovanes, this trace takes us to a problem with the database during the upgrade. So, first thing we could start by checking is:
> 1. Database compatibility
> 2. Database Driver
> 3. Connection string that points to the database
> 4. Your server.xml file maxThreads value (and all other parameters context)

We have seen this situation before. There were two situations where this error popped up:

* Unsupported database
* Missing maxThreads parameter

Further, never forget to back up **\<confluence-home\> and \<confluence-install\> folders** as well as your **database** prior to any upgrade.

Also, upgrades should always be tested on a test instance before applying them to the production instance.

You will want to look into these:
> * **[Supported Platforms - Confluence 6.15](https://confluence.atlassian.com/doc/supported-platforms-207488198.html)**
> * **[Database JDBC drivers](https://confluence.atlassian.com/doc/database-jdbc-drivers-171742.html)**

Looking forward to your reply Ovanes!

comments: author: OVANES OGANYAN
body: Thanks for help.

Certainly, I've made back up \<confluence-home\> and \<confluence-install\> folders and database.  
In that problem case, I used back up and upgraded 6.14.0-\>6.14.3. It's enough for CVE-2019-3396 now.


author: Diego
body: Hello there! You are correct, both CVEs are addressed on Connie 6.14.3:

**[Confluence Security Advisory - 2019-04-17 \| Confluence - Path traversal vulnerability - CVE-2019-3398](https://confluence.atlassian.com/doc/confluence-security-advisory-2019-04-10-968660855.html)**

[**Confluence Security Advisory - 2019-03-20 \| March 2019 Confluence Server Advisory - WebDAV and Widget Connector vulnerabilities**](https://confluence.atlassian.com/doc/confluence-security-advisory-2019-03-20-966660264.html)

Is your instance working as expected now?

Let us know!


author: OVANES OGANYAN
body: Yes, everything is ok now.  
Issue is closed.

I'll plan next upgrade more accuracy :)


author: Diego
body: Thanks for the feedback!


Tags: confluence-server

server