Not able to upgrade from 3.2 to 3.5 Confluence

I did follow the steps mentioned in the upgrade guide. I am on way to upgrade to 4.2 from 3.2. The process says that first I need to upgrade it to 3.5 and then to 4.2. However, I am facing issues in upgrading from 3.2 to 3.5. Every time it says Upgrade failed, check system logs for more details.

Also I posted my question to Q&A public section, however, did not get any reply. I am not sure what step I am missing in the upgrade process. If I switch back to the older confluence it works just perfect. Please find the logs for your reference.

root@web01 logs # tailf atlassian-confluence.log

012-08-24 09:30:59,419 INFO main springframework.web.context.ContextLoader initWebApplicationContext Root WebApplicationContext: initialization completed in 15211 ms

2012-08-24 09:31:01,150 ERROR main hibernate.tool.hbm2ddl.SchemaUpdate execute Unsuccessful: create index band_cont_key_idx on BANDANA (BANDANACONTEXT, BANDANAKEY)

2012-08-24 09:31:01,150 ERROR main hibernate.tool.hbm2ddl.SchemaUpdate execute Specified key was too long; max key length is 1000 bytes

2012-08-24 09:31:01,151 ERROR main hibernate.tool.hbm2ddl.SchemaUpdate execute could not complete schema update

com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was too long; max key length is 1000 bytes

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

at java.lang.reflect.Constructor.newInstance(Constructor.java:513)

at com.mysql.jdbc.Util.handleNewInstance(Util.java:406)

at com.mysql.jdbc.Util.getInstance(Util.java:381)

at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1051)

at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3563)

at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3495)

at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1959)

at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2113)

at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2687)

at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1647)

at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1566)

at com.mchange.v2.c3p0.impl.NewProxyStatement.executeUpdate(NewProxyStatement.java:64)

at net.sf.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:167)

at bucket.core.persistence.hibernate.schema.SchemaHelper.updateSchemaIfNeeded(SchemaHelper.java:161)

at bucket.core.persistence.hibernate.schema.SchemaHelper.updateSchemaIfNeeded(SchemaHelper.java:134)

at com.atlassian.confluence.upgrade.AbstractUpgradeManager.upgrade(AbstractUpgradeManager.java:91)

at com.atlassian.confluence.upgrade.impl.DefaultUpgradeManager.upgrade(DefaultUpgradeManager.java:140)

at com.atlassian.confluence.upgrade.UpgradeLauncherServletContextListener.contextInitialized(UpgradeLauncherServletContextListener.java:28)

at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4205)

at org.apache.catalina.core.StandardContext.start(StandardContext.java:4704)

at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)

at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)

at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)

at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)

at org.apache.catalina.core.StandardService.start(StandardService.java:525)

at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)

at org.apache.catalina.startup.Catalina.start(Catalina.java:595)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)

at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)

2012-08-24 09:31:01,160 ERROR main atlassian.confluence.upgrade.UpgradeLauncherServletContextListener contextInitialized 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:111)

at com.atlassian.confluence.upgrade.impl.DefaultUpgradeManager.upgrade(DefaultUpgradeManager.java:140)

at com.atlassian.confluence.upgrade.UpgradeLauncherServletContextListener.contextInitialized(UpgradeLauncherServletContextListener.java:28)

at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4205)

at org.apache.catalina.core.StandardContext.start(StandardContext.java:4704)

at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)

at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)

at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)

at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)

at org.apache.catalina.core.StandardService.start(StandardService.java:525)

at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)

at org.apache.catalina.startup.Catalina.start(Catalina.java:595)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)

at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)

Caused by: com.atlassian.config.ConfigurationException: Cannot update schema

at bucket.core.persistence.hibernate.schema.SchemaHelper.updateSchemaIfNeeded(SchemaHelper.java:165)

at bucket.core.persistence.hibernate.schema.SchemaHelper.updateSchemaIfNeeded(SchemaHelper.java:134)

at com.atlassian.confluence.upgrade.AbstractUpgradeManager.upgrade(AbstractUpgradeManager.java:91)

... 17 more

Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was too long; max key length is 1000 bytes

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

at java.lang.reflect.Constructor.newInstance(Constructor.java:513)

at com.mysql.jdbc.Util.handleNewInstance(Util.java:406)

at com.mysql.jdbc.Util.getInstance(Util.java:381)

at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1051)

at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3563)

at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3495)

at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1959)

at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2113)

at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2687)

at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1647)

at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1566)

at com.mchange.v2.c3p0.impl.NewProxyStatement.executeUpdate(NewProxyStatement.java:64)

at net.sf.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:167)

at bucket.core.persistence.hibernate.schema.SchemaHelper.updateSchemaIfNeeded(SchemaHelper.java:161)

... 19 more

2012-08-24 09:31:01,162 ERROR main atlassian.confluence.upgrade.UpgradeLauncherServletContextListener contextInitialized 1 errors were encountered during upgrade:

2012-08-24 09:31:01,163 ERROR main atlassian.confluence.upgrade.UpgradeLauncherServletContextListener contextInitialized 1: Cannot update schema

2012-08-24 09:31:02,561 INFO main com.atlassian.confluence.lifecycle init Confluence is ready to serve

2012-08-24 09:32:00,343 INFO main atlassian.plugin.manager.DefaultPluginManager shutdown Shutting down the plugin system

2012-08-24 09:32:00,552 INFO main com.atlassian.confluence.lifecycle contextDestroyed Stopping Confluence

2012-08-24 09:32:37,301 INFO main com.atlassian.confluence.lifecycle contextInitialized Starting Confluence 3.2 (build #1810)

2012-08-24 09:32:39,974 INFO main atlassian.plugin.manager.DefaultPluginManager init Initialising the plugin system

2012-08-24 09:32:40,215 INFO main atlassian.plugin.manager.DefaultPluginManager init Plugin system started in 0:00:00.240

2012-08-24 09:32:41,084 INFO main springframework.web.context.ContextLoader initWebApplicationContext Root WebApplicationContext: initialization started

root@web01 logs # tailf catalina.out

2012-08-23 17:20:24,242 INFO main atlassian.plugin.manager.DefaultPluginManager init Initialising the plugin system

2012-08-23 17:20:24,355 INFO main atlassian.plugin.manager.DefaultPluginManager init Plugin system started in 0:00:00.112

alter table cwd_app_dir_group_mapping add constraint fk_app_dir_group_dir foreign key (directory_id) references cwd_directory (id)

alter table CONTENT_PERM_SET add constraint FKBF45A7992CAF22C1 foreign key (CONTENT_ID) references CONTENT (CONTENTID)

alter table IMAGEDETAILS add constraint FKA768048734A4917E foreign key (ATTACHMENTID) references ATTACHMENTS (ATTACHMENTID)

create index band_cont_key_idx on BANDANA (BANDANACONTEXT, BANDANAKEY)

Aug 23, 2012 5:20:45 PM org.apache.coyote.http11.Http11Protocol start

INFO: Starting Coyote HTTP/1.1 on http-8080

Aug 23, 2012 5:20:45 PM org.apache.catalina.startup.Catalina start

INFO: Server startup in 25991 ms

Aug 24, 2012 9:29:58 AM org.apache.coyote.http11.Http11Protocol pause

INFO: Pausing Coyote HTTP/1.1 on http-8080

Aug 24, 2012 9:29:59 AM org.apache.catalina.core.StandardService stop

INFO: Stopping service Tomcat-Standalone

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application registered the JDBC driver org.hsqldb.jdbc.JDBCDriver but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application registered the JDBC driver org.postgresql.Driver but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application registered the JDBC driver com.mysql.jdbc.Driver but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named com.google.common.base.internal.Finalizer but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0 but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1 but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2 but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named QuartzScheduler_Worker-1 but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named QuartzScheduler_Worker-2 but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named QuartzScheduler_Worker-3 but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named QuartzScheduler_Worker-4 but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named QuartzScheduler_Worker-5 but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named QuartzScheduler_Worker-6 but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named QuartzScheduler_Worker-7 but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named QuartzScheduler_Worker-8 but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named QuartzScheduler_Worker-9 but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named QuartzScheduler_Worker-10 but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named Timer-3 but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0 but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1 but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2 but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named Resource Destroyer in BasicResourcePool.close() but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named Resource Destroyer in BasicResourcePool.close() but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap

SEVERE: The web application created a ThreadLocal with key of type java.lang.ThreadLocal (value java.lang.ThreadLocal@6a221968 ) and a value of type org.dom4j.DocumentFactory (value org.dom4j.DocumentFactory@64b23147 ) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap

SEVERE: The web application created a ThreadLocal with key of type com.atlassian.core.logging.ThreadLocalErrorCollection$2 (value com.atlassian.core.logging.ThreadLocalErrorCollection$2@59834848 ) and a value of type java.lang.Boolean (value false ) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap

SEVERE: The web application created a ThreadLocal with key of type com.atlassian.core.logging.ThreadLocalErrorCollection$1 (value com.atlassian.core.logging.ThreadLocalErrorCollection$1@3f38dd0 ) and a value of type java.util.LinkedList (value ) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap

SEVERE: The web application created a ThreadLocal with key of type com.atlassian.core.logging.ThreadLocalErrorCollection$2 (value com.atlassian.core.logging.ThreadLocalErrorCollection$2@59834848 ) and a value of type java.lang.Boolean (value false ) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.

Aug 24, 2012 9:29:59 AM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap

SEVERE: The web application created a ThreadLocal with key of type org.apache.log4j.helpers.ThreadLocalMap (value org.apache.log4j.helpers.ThreadLocalMap@73517a05 ) and a value of type java.util.Hashtable (value {} ) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.

log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading, using NOPLoggerRepository.

Aug 24, 2012 9:29:59 AM org.apache.coyote.http11.Http11Protocol destroy

INFO: Stopping Coyote HTTP/1.1 on http-8080

Aug 24, 2012 9:30:37 AM org.apache.tomcat.util.digester.SetPropertiesRule begin

WARNING: SetPropertiesRule {Server} Setting property 'debug' to '0' did not find a matching property.

Aug 24, 2012 9:30:37 AM org.apache.tomcat.util.digester.SetPropertiesRule begin

WARNING: SetPropertiesRule {Server/Service/Engine} Setting property 'debug' to '0' did not find a matching property.

Aug 24, 2012 9:30:37 AM org.apache.tomcat.util.digester.SetPropertiesRule begin

WARNING: SetPropertiesRule {Server/Service/Engine/Host} Setting property 'debug' to '0' did not find a matching property.

Aug 24, 2012 9:30:37 AM org.apache.tomcat.util.digester.SetPropertiesRule begin

WARNING: SetPropertiesRule {Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.

Aug 24, 2012 9:30:37 AM org.apache.coyote.http11.Http11Protocol init

INFO: Initializing Coyote HTTP/1.1 on http-8080

Aug 24, 2012 9:30:37 AM org.apache.catalina.startup.Catalina load

INFO: Initialization processed in 295 ms

Aug 24, 2012 9:30:37 AM org.apache.catalina.core.StandardService start

INFO: Starting service Tomcat-Standalone

Aug 24, 2012 9:30:37 AM org.apache.catalina.core.StandardEngine start

INFO: Starting Servlet Engine: Apache Tomcat/6.0.32

2012-08-24 09:30:40,790 INFO main com.atlassian.confluence.lifecycle contextInitialized Starting Confluence 3.5.16 (build #2172)

2012-08-24 09:30:42,941 INFO main atlassian.plugin.manager.DefaultPluginManager init Initialising the plugin system

2012-08-24 09:30:43,060 INFO main atlassian.plugin.manager.DefaultPluginManager init Plugin system started in 0:00:00.117

alter table cwd_app_dir_group_mapping add constraint fk_app_dir_group_dir foreign key (directory_id) references cwd_directory (id)

alter table CONTENT_PERM_SET add constraint FKBF45A7992CAF22C1 foreign key (CONTENT_ID) references CONTENT (CONTENTID)

alter table IMAGEDETAILS add constraint FKA768048734A4917E foreign key (ATTACHMENTID) references ATTACHMENTS (ATTACHMENTID)

create index band_cont_key_idx on BANDANA (BANDANACONTEXT, BANDANAKEY)

Aug 24, 2012 9:31:02 AM org.apache.coyote.http11.Http11Protocol start

INFO: Starting Coyote HTTP/1.1 on http-8080

Aug 24, 2012 9:31:02 AM org.apache.catalina.startup.Catalina start

INFO: Server startup in 24689 ms

Aug 24, 2012 9:31:59 AM org.apache.coyote.http11.Http11Protocol pause

INFO: Pausing Coyote HTTP/1.1 on http-8080

Aug 24, 2012 9:32:00 AM org.apache.catalina.core.StandardService stop

INFO: Stopping service Tomcat-Standalone

Aug 24, 2012 9:32:00 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application registered the JDBC driver org.hsqldb.jdbc.JDBCDriver but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

Aug 24, 2012 9:32:00 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application registered the JDBC driver org.postgresql.Driver but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

Aug 24, 2012 9:32:00 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application registered the JDBC driver com.mysql.jdbc.Driver but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

Aug 24, 2012 9:32:00 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named com.google.common.base.internal.Finalizer but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:32:00 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named QuartzScheduler_Worker-1 but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:32:00 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named Timer-3 but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:32:00 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0 but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:32:00 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1 but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:32:00 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2 but has failed to stop it. This is very likely to create a memory leak.

Aug 24, 2012 9:32:00 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application appears to have started a thread named Resource Destroyer in BasicResourcePool.close() but has failed to stop it. This is very likely to create a memory

2 answers

This widget could not be displayed.

Hi, it looks like you are using MySQL. Do you know if you are using the MyISAM engine instead of InnoDB? It'd give that a check. For full resolution refer to this knowledgebase article. It has instructions on how to change the engine and get this fixed.

For more information refer to Known Issues for MySQL.

This widget could not be displayed.

In adition to Harry's comment, I would also verify if you are using UTF-8, it seems to be a "bug" due that latin1 can't handle such values as UTF-8 does:

http://bugs.mysql.com/bug.php?id=4541

And here is a good documentation on how to create the database properly. But not forgeting Harry's comment, the InnoDB is required

https://confluence.atlassian.com/display/CONF42/Configuring+Database+Character+Encoding#ConfiguringDatabaseCharacterEncoding-CreatingaUTF-8database

Cheers,

Guilherme

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Monday in Confluence

Why start from scratch? Introducing four new templates for Confluence Cloud

Hi my Community friends!  For those who don't know me, I'm a product marketer on the Confluence Cloud team - nice to meet you! For those of you who do, you know that I've been all up in your Co...

398 views 4 6
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you