Error occurred during export before upgrade from version 4.1 to 4.4.3

[rsingh]

When upgrading from version 4.1 to 4.4.3 I get the following error in the logs

2011-12-29 11:13:24,901 Thread-1 INFO jira.bc.dataimport.DefaultExportService Attempting to save the Active Objects Backup

2011-12-29 11:13:24,917 Thread-1 ERROR atlassian.jira.upgrade.UpgradeManagerImpl Error occurred during export before upgrade: com.atlassian.activeobjects.internal.DatabaseProviderNotFoundException: Could not find database provider for data source which uses JDBC driver <ibm db2="" jdbc="" universal="" driver="" architecture="">. If necessary, auto-export can be disabled; see http://www.atlassian.com/software/jira/docs/latest/upgrade/autoexport.html

com.atlassian.activeobjects.internal.DatabaseProviderNotFoundException: Could not find database provider for data source which uses JDBC driver <ibm db2="" jdbc="" universal="" driver="" architecture="">

at com.atlassian.activeobjects.internal.JdbcDriverDatabaseProviderFactory.getDatabaseProvider(JdbcDriverDatabaseProviderFactory.java:49)

at com.atlassian.activeobjects.backup.ActiveObjectsBackup$1.get(ActiveObjectsBackup.java:69)

at com.atlassian.activeobjects.backup.ActiveObjectsBackup$1.get(ActiveObjectsBackup.java:65)

at com.atlassian.activeobjects.backup.ActiveObjectsBackup.save(ActiveObjectsBackup.java:95)

at com.atlassian.jira.bc.dataimport.DefaultExportService.export(DefaultExportService.java:91)

at com.atlassian.jira.bc.dataimport.DefaultExportService.export(DefaultExportService.java:53)

at com.atlassian.jira.bean.export.AutoExportImpl.exportData(AutoExportImpl.java:95)

at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeeded(UpgradeManagerImpl.java:348)

at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeededAndAllowed(UpgradeManagerImpl.java:309)

at com.atlassian.jira.upgrade.UpgradeLauncher.checkIfUpgradeNeeded(UpgradeLauncher.java:100)

at com.atlassian.jira.upgrade.UpgradeLauncher.start(UpgradeLauncher.java:49)

at com.atlassian.jira.startup.DefaultJiraLauncher$3.run(DefaultJiraLauncher.java:103)

at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:250)

at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(DatabaseConfigurationManagerImpl.java:149)

at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:94)

at com.atlassian.jira.startup.DefaultJiraLauncher.access$100(DefaultJiraLauncher.java:24)

at com.atlassian.jira.startup.DefaultJiraLauncher$1.run(DefaultJiraLauncher.java:61)

at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:33)

at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:56)

at com.atlassian.jira.startup.LauncherContextListener$1.create(LauncherContextListener.java:68)

at com.atlassian.jira.startup.LauncherContextListener$1.create(LauncherContextListener.java:63)

at com.atlassian.multitenant.impl.MultiTenantComponentMapImpl.get(MultiTenantComponentMapImpl.java:121)

at com.atlassian.multitenant.impl.MultiTenantComponentMapImpl.onTenantStart(MultiTenantComponentMapImpl.java:165)

at com.atlassian.multitenant.impl.DefaultMultiTenantManager$1.consume(DefaultMultiTenantManager.java:134)

at com.atlassian.multitenant.impl.DefaultMultiTenantManager$1.consume(DefaultMultiTenantManager.java:131)

at com.atlassian.multitenant.impl.DefaultMultiTenantManager.runForEachListener(DefaultMultiTenantManager.java:256)

at com.atlassian.multitenant.impl.DefaultMultiTenantManager.startTenant(DefaultMultiTenantManager.java:130)

at com.atlassian.multitenant.impl.DefaultMultiTenantManager.startAll(DefaultMultiTenantManager.java:203)

at com.atlassian.jira.startup.LauncherContextListener.contextInitialized(LauncherContextListener.java:96)

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

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

at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)

at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)

at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)

at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:630)

at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:556)

at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:491)

at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1206)

at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:314)

at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)

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

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

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

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

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

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

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

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:288)

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

2011-12-29 11:13:32,026 Thread-1 INFO atlassian.jira.scheduler.JiraSchedulerLauncher JIRA Scheduler not started: Johnson events detected.

I followed the steps mentioned in http://www.ricksoft.jp/document/display/JIRA/Connecting+JIRA+to+DB2

My config files are as shown below:

1. JIRA.xml

<context path="/JIRA" docbase="D:" apache="" tomcat="" 6.0="" profiles="" jira="" webapps="" jira="" debug="0" usehttponly="true">

<resource name="jdbc/JiraDS" auth="Container" type="javax.sql.DataSource&lt;/p">

username=jira_DB

password=n3v3ragain

driverClassName=com.ibm.db2.jcc.DB2Driver

url=jdbc:db2://cpaus-db2test.creata.com:50002/JIRA4_1T

/>

<resource name="UserTransaction" auth="Container" type="javax.transaction.UserTransaction&lt;/p">

factory=org.objectweb.jotm.UserTransactionFactory jotm.timeout=60/>

<manager pathname="/">

</context>

2. entityengine.xml added the following lines

<datasource name="defaultDS" field-type-name="db2&lt;/p">

schema-name=JIRA_DB

helper-class=org.ofbiz.core.entity.GenericHelperDAO

check-on-start=true

use-foreign-keys=false

use-foreign-key-indices=false

check-fks-on-start=false

check-fk-indices-on-start=false

add-missing-on-start=true

check-indices-on-start=true

constraint-name-clip-length=15>

<jndi-jdbc jndi-server-name="default" jndi-name="java:comp/env/jdbc/JiraDS/">

3. dbconfig.xml is generated with the following

<jira-database-config>

<name>defaultDS</name>

<delegator-name>default</delegator-name>

<database-type>db2</database-type>

<schema-name>JIRA_DB</schema-name>

<jndi-datasource>

<jndi-name>java:comp/env/jdbc/JiraDS</jndi-name>

</jndi-datasource>

</jira-database-config>

Let me know if you need any more information

[ChrisA · Accepted solution]

Unfortunately this is because JIRA does not support running on the DB2 platform:

http://confluence.atlassian.com/display/JIRA044/Supported+Platforms

What's happening here is during the upgrade process, JIRA will create an xml export. This process fails because the Active Objects library is failing completely on that process and the backup stops. There logs provide a link to a page that shows you how to disable that auto-export, which will allow the upgrade to continue.

However, this is just the tip of the iceberg really. From here, it will continue to experience issues with Active Objects, preventing you from being able to perform an xml backup, or use any features that rely on Active Objects such as the new GreenHopper Rapid Board. Additionally, since we don't test against DB2, there may be any number of unknown and undocumented errors with JIRA itself.