Issue Details (XML | Word | Printable)

Key: CONF-7589
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Blocker Blocker
Assignee: Unassigned
Reporter: Agnes Ro [Atlassian]
Votes: 0
Watchers: 3
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
Confluence

Upgrade to 2.3 with MySQL causes error - Dialect class not found: bucket.dialect.MySQLDialect

Created: 07/Jan/07 11:41 PM   Updated: 07/Mar/07 05:23 PM
Component/s: Upgrade Manager
Affects Version/s: 2.3
Fix Version/s: 2.3.1

Time Tracking:
Not Specified

Issue Links:
Duplicate
 

Participants: Agnes Ro [Atlassian] and David Soul [Atlassian]
Since last comment: 2 years, 24 weeks, 2 days ago
Resolution Date: 15/Jan/07 10:55 PM
Labels:


 Description  « Hide
When upgrading to 2.3 with MySQL, the following error occurs:

2007-01-06 18:43:28,115 WARN [main] [sf.hibernate.cfg.SettingsFactory] buildSettings No dialect set - using GenericDialect: Dialect class not found: bucket.dialect.MySQLDialect
2007-01-06 18:43:31,965 FATAL [main] [com.atlassian.upgrade.AbstractUpgradeManager] upgradeSchema Could not update schema.
com.atlassian.config.ConfigurationException: Cannot update schema
at bucket.core.persistence.hibernate.schema.SchemaHelper.updateSchemaIfNeeded(SchemaHelper.java:159)
at bucket.core.persistence.hibernate.schema.SchemaHelper.updateSchemaIfNeeded(SchemaHelper.java:142)
at com.atlassian.upgrade.AbstractUpgradeManager.upgradeSchema(AbstractUpgradeManager.java:137)
at com.atlassian.upgrade.AbstractUpgradeManager.upgrade(AbstractUpgradeManager.java:46)
at com.atlassian.confluence.upgrade.impl.DefaultUpgradeManager.upgrade(DefaultUpgradeManager.java:57)
at com.atlassian.upgrade.UpgradeLauncherServletContextListener.contextInitialized(UpgradeLauncherServletContextListener.java:26)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3729)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4187)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:608)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:535)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:470)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1122)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1021)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
at org.apache.catalina.core.StandardService.start(StandardService.java:450)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
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:585)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)
Caused by: net.sf.hibernate.HibernateException: Dialect class not found: bucket.dialect.MySQLDialect
at net.sf.hibernate.dialect.Dialect.getDialect(Dialect.java:396)
at net.sf.hibernate.tool.hbm2ddl.SchemaUpdate.<init>(SchemaUpdate.java:40)
at net.sf.hibernate.tool.hbm2ddl.SchemaUpdate.<init>(SchemaUpdate.java:35)
at bucket.core.persistence.hibernate.schema.SchemaHelper.updateSchemaIfNeeded(SchemaHelper.java:155)
... 29 more
2007-01-06 18:43:32,000 WARN [main] [core.persistence.hibernate.HibernateVersionHistoryDao] getLatestBuildNumber Unable to determine build number from database. If you are upgrading from a Confluence version prior to 2.3, this is expected: Table 'confluence.CONFVERSION' doesn't exist
2007-01-06 18:43:32,291 ERROR [main] [sf.hibernate.util.JDBCExceptionReporter] logExceptions Table 'confluence.BANDANA' doesn't exist

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
[ Permalink | « Hide ]
Agnes Ro [Atlassian] added a comment - 08/Jan/07 12:04 AM
This is due to the package rename for the MySQLDialect class.

A workaround for now would be to edit the confluence.cfg.xml file (under the Confluence home directory) to fix the following property:

<property name="hibernate.dialect">com.atlassian.hibernate.dialect.MySQLDialect</property>


[ Permalink | « Hide ]
David Soul [Atlassian] added a comment - 15/Jan/07 09:32 PM
A user has reported that after applying the patch to their existing 2.2.9 confluence.cfg.xml file and performing a method 1 upgrade, the error was still occurring.

[ Permalink | « Hide ]
Agnes Ro [Atlassian] added a comment - 15/Jan/07 10:34 PM
The workaround should be applied before upgrading. If the upgrade process was completed and this error is shown, revert to your confluence home backup, edit the confluence.cfg.xml file and then try performing the upgrade again.

[ Permalink | « Hide ]
David Soul [Atlassian] added a comment - 15/Jan/07 10:55 PM
User was not restoring their DB when attempting upgrade, closing bug as patched.


Powered by Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.13.4-#354) - Bug/feature request - Atlassian news - Contact Administrators