It's all about the answers!

Ask a question

Update RQM from 3.0.1.2 to 4.0.1 RC3 Fails with "Workflow constraint migration failed " in step 1


Robert Ducharme (93128) | asked Nov 15 '12, 11:47 a.m.
While upgrading a single server (linux) environment from CLM 3.0.1.2 to 4.0.1 RC3, I get an error while running the upgrade/qm_upgrade.sh script.  See below. Any ideas?

The scripts for jts and ccm worked without seeming to cause any failures.  The parameter files were edited with the old and new environment information like the jts and ccm parameters.

The error message in step 1 is:
2012-11-15 08:08:38,335 performing workflow permissions migration
2012-11-15 08:08:38,340 performing workflow advisor migration
2012-11-15 08:08:38,360 Workflow constraint migration failed for [webTA (Quality Management)] error occured see log
com.ibm.team.repository.common.TeamRepositoryException: Element type "precondition" must be followed by either attribute specifications, ">" or "/>".

        at com.ibm.rqm.planning.service.migration.PlanningProcessMigrationUtil.createSpecificationModel(PlanningProcessMigrationUtil.java:711)
        at com.ibm.rqm.planning.service.migration.PlanningProcessMigrationUtil.addTeamPrecondition(PlanningProcessMigrationUtil.java:199)
        at com.ibm.rqm.planning.service.migration.PlanningProcessMigrationHelper2012.applyWorkflowPreconditions(PlanningProcessMigrationHelper2012.java:857)
        at com.ibm.rqm.planning.service.migration.PlanningProcessMigrationHelper2012.performWorkflowAdvisorMigration(PlanningProcessMigrationHelper2012.java:595)
        at com.ibm.rqm.planning.service.migration.PlanningProcessMigrationHelper2012.migrateSpecification(PlanningProcessMigrationHelper2012.java:92)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:611)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
        at $Proxy3672.migrateSpecification(Unknown Source)
        at com.ibm.team.process.internal.service.migration.ProcessSettingsMigrationUtil.migrateProcessSpecification(ProcessSettingsMigrationUtil.java:134)
        at com.ibm.team.process.internal.service.migration.ProcessSettingsMigrationUtil.migrateProcessSettings(ProcessSettingsMigrationUtil.java:89)
        at com.ibm.team.process.internal.service.migration.ProcessMigrationHandlerTo21.migrateContent(ProcessMigrationHandlerTo21.java:336)
        at com.ibm.team.process.internal.service.migration.ProcessMigrationHandlerTo21.postAddTables(ProcessMigrationHandlerTo21.java:467)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:611)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
        at $Proxy3653.postAddTables(Unknown Source)
        at com.ibm.team.repository.migration.internal.service.MigrationHandlerDispatcher.doPostAddTables(MigrationHandlerDispatcher.java:688)
        at com.ibm.team.repository.migration.internal.service.MigrationHandlerDispatcher.postAddTables(MigrationHandlerDispatcher.java:680)
        at com.ibm.team.repository.service.internal.rdb.DatabaseMaintenanceService.performPostAddTables(DatabaseMaintenanceService.java:1456)
        at com.ibm.team.repository.service.internal.rdb.DatabaseMaintenanceService.performPostAddTables(DatabaseMaintenanceService.java:341)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:611)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
        at $Proxy186.performPostAddTables(Unknown Source)
        at com.ibm.team.repotools.commands.local.internal.AddTablesCommand$1.run(AddTablesCommand.java:85)
        at com.ibm.team.repotools.commands.local.internal.AddTablesCommand$1.run(AddTablesCommand.java:1)
        at com.ibm.team.repository.service.internal.TeamServiceContext.runAsAdmin(TeamServiceContext.java:141)
        at com.ibm.team.repotools.commands.local.internal.AddTablesCommand.addTables(AddTablesCommand.java:60)
        at com.ibm.team.repotools.commands.local.internal.AddTablesCommand.execute(AddTablesCommand.java:166)
        at com.ibm.team.repotools.command.AbstractCommand.execute(AbstractCommand.java:66)
        at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.run(RepositoryToolsApplication.java:768)
        at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.start(RepositoryToolsApplication.java:843)
        at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:611)
        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
        at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
        at org.eclipse.equinox.launcher.Main.main(Main.java:1384)
Caused by: org.xml.sax.SAXParseException: Element type "precondition" must be followed by either attribute specifications, ">" or "/>".
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
        at com.ibm.team.process.internal.common.model.ModelGenerator.generate(ModelGenerator.java:88)
        at com.ibm.team.process.internal.common.model.AbstractModel.initialize(AbstractModel.java:86)
        at com.ibm.rqm.planning.service.migration.PlanningProcessMigrationUtil.createSpecificationModel(PlanningProcessMigrationUtil.java:705)
        ... 57 more
2012-11-15 08:08:38,363 performing artifact lock migration

One answer



permanent link
Rosa Naranjo (2.9k11723) | answered Nov 15 '12, 12:41 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
Hello
Please file a workitem against RQM and attach the log files for the repotools scripts that qm_upgrade script is running.  They are located in the 'server' directory.  I looked and could not find a similar stack trace but I did see issues reported in the past with other SAXParse issues.

Someone from the RQM or JFS team will reply. 

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.