CRJAZ0683I Error executing the post-import handler
Hi,
I'm getting CRJAZ0683I Error when importing repository to RQM201 from RQM20. I tried to change the memory setting in reportools - VMARGS as suggested in few posts I found but it didn't help.
Does anyone have any suggestions? Thanks in advance
Running post import for "com.ibm.team.process" component...
2011-05-29 13:47:15,659 CRJAZ0683I Error executing the post-import handler for the "com.ibm.team.process" namespace.
java.lang.NullPointerException
at com.ibm.rqm.requirement.service.migration.RequirementProcessMigrationHelper.migrateCustomAttributes(RequirementProcessMigrationHelper.java:147)
at com.ibm.rqm.requirement.service.migration.RequirementProcessMigrationHelper.migrateProcess(RequirementProcessMigrationHelper.java:135)
at com.ibm.rqm.process.migration.RQMProcessMigrationHelper$1.execute(RQMProcessMigrationHelper.java:220)
at com.ibm.rqm.process.migration.RQMProcessMigrationHelper$1.execute(RQMProcessMigrationHelper.java:1)
at com.ibm.rqm.process.migration.RQMProcessMigrationHelper.computeVersionAndExecute(RQMProcessMigrationHelper.java:286)
at com.ibm.rqm.process.migration.RQMProcessMigrationHelper.migrateSpecification(RQMProcessMigrationHelper.java:218)
at com.ibm.team.process.internal.service.migration.ProcessSettingsMigrationUtil.migrateProcessSpecification(ProcessSettingsMigrationUtil.java:240)
at com.ibm.team.process.internal.service.migration.ProcessSettingsMigrationUtil.migrateProcessSettings(ProcessSettingsMigrationUtil.java:83)
at com.ibm.team.process.internal.service.migration.ProcessMigrationHandlerTo11.migrateContent(ProcessMigrationHandlerTo11.java:527)
at com.ibm.team.process.internal.service.migration.ProcessMigrationHandlerTo11.postImport(ProcessMigrationHandlerTo11.java:357)
at com.ibm.team.repository.migration.AbstractMigrationHandler.postImport(AbstractMigrationHandler.java:293)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy916.postImport(Unknown Source)
at com.ibm.team.repository.migration.internal.service.MigrationHandlerDispatcher.postImport(MigrationHandlerDispatcher.java:469)
at com.ibm.team.repository.migration.internal.service.MigrationHandlerDispatcher.postImport(MigrationHandlerDispatcher.java:460)
at com.ibm.team.repository.migration.internal.service.AbstractMigrationService.performPostImport(AbstractMigrationService.java:1148)
at com.ibm.team.repository.migration.internal.service.AbstractMigrationService.importRepositoryOptionalVerifyPreserve(AbstractMigrationService.java:718)
at com.ibm.team.repository.migration.internal.service.AbstractMigrationService.importRepositoryOptionalVerify(AbstractMigrationService.java:662)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy664.importRepositoryOptionalVerify(Unknown Source)
at com.ibm.team.repotools.commands.local.internal.ImportCommand.importData(ImportCommand.java:162)
at com.ibm.team.repotools.commands.local.internal.ImportCommand.execute(ImportCommand.java:123)
at com.ibm.team.repotools.command.AbstractCommand.execute(AbstractCommand.java:48)
at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.run(RepositoryToolsApplication.java:727)
at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.start(RepositoryToolsApplication.java:764)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
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:386)
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:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
I'm getting CRJAZ0683I Error when importing repository to RQM201 from RQM20. I tried to change the memory setting in reportools - VMARGS as suggested in few posts I found but it didn't help.
Does anyone have any suggestions? Thanks in advance
Running post import for "com.ibm.team.process" component...
2011-05-29 13:47:15,659 CRJAZ0683I Error executing the post-import handler for the "com.ibm.team.process" namespace.
java.lang.NullPointerException
at com.ibm.rqm.requirement.service.migration.RequirementProcessMigrationHelper.migrateCustomAttributes(RequirementProcessMigrationHelper.java:147)
at com.ibm.rqm.requirement.service.migration.RequirementProcessMigrationHelper.migrateProcess(RequirementProcessMigrationHelper.java:135)
at com.ibm.rqm.process.migration.RQMProcessMigrationHelper$1.execute(RQMProcessMigrationHelper.java:220)
at com.ibm.rqm.process.migration.RQMProcessMigrationHelper$1.execute(RQMProcessMigrationHelper.java:1)
at com.ibm.rqm.process.migration.RQMProcessMigrationHelper.computeVersionAndExecute(RQMProcessMigrationHelper.java:286)
at com.ibm.rqm.process.migration.RQMProcessMigrationHelper.migrateSpecification(RQMProcessMigrationHelper.java:218)
at com.ibm.team.process.internal.service.migration.ProcessSettingsMigrationUtil.migrateProcessSpecification(ProcessSettingsMigrationUtil.java:240)
at com.ibm.team.process.internal.service.migration.ProcessSettingsMigrationUtil.migrateProcessSettings(ProcessSettingsMigrationUtil.java:83)
at com.ibm.team.process.internal.service.migration.ProcessMigrationHandlerTo11.migrateContent(ProcessMigrationHandlerTo11.java:527)
at com.ibm.team.process.internal.service.migration.ProcessMigrationHandlerTo11.postImport(ProcessMigrationHandlerTo11.java:357)
at com.ibm.team.repository.migration.AbstractMigrationHandler.postImport(AbstractMigrationHandler.java:293)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy916.postImport(Unknown Source)
at com.ibm.team.repository.migration.internal.service.MigrationHandlerDispatcher.postImport(MigrationHandlerDispatcher.java:469)
at com.ibm.team.repository.migration.internal.service.MigrationHandlerDispatcher.postImport(MigrationHandlerDispatcher.java:460)
at com.ibm.team.repository.migration.internal.service.AbstractMigrationService.performPostImport(AbstractMigrationService.java:1148)
at com.ibm.team.repository.migration.internal.service.AbstractMigrationService.importRepositoryOptionalVerifyPreserve(AbstractMigrationService.java:718)
at com.ibm.team.repository.migration.internal.service.AbstractMigrationService.importRepositoryOptionalVerify(AbstractMigrationService.java:662)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy664.importRepositoryOptionalVerify(Unknown Source)
at com.ibm.team.repotools.commands.local.internal.ImportCommand.importData(ImportCommand.java:162)
at com.ibm.team.repotools.commands.local.internal.ImportCommand.execute(ImportCommand.java:123)
at com.ibm.team.repotools.command.AbstractCommand.execute(AbstractCommand.java:48)
at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.run(RepositoryToolsApplication.java:727)
at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.start(RepositoryToolsApplication.java:764)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
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:386)
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:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
3 answers
I did a search of the RQM project for any related defects, but didn't find anything that seemed connected to your issue. I'll give you some info, but if you have trouble solving the issue you should create a support ticket against RQM for this issue...
I think there is something wrong with one of your project area's process configuration that is causing this exception in during migration. I would start your RQM 2.0 server and connect to it using the RTC Eclipse client. I can't recall which version of the RTC eclipse client is compatible with RQM 2.0, but I would guess RTC 1.0. Once you have created a repository connection to your RQM server, you will want to "manage your connected project areas" and connect to all of them, even select the option to include archived project areas. Then right click each project area, open it and go to the process configuration tab. Then go under Project Configuration, Configuration Data. And make sure something is defined under the configuration data. For your migration issue, it doesn't matter what's defined under Configuration Data, just so long as the configuration data isn't empty. Looks like the migration code is assuming that all projects must have Configuration Data, else it will hit this issue. Typically, I think they would all have Configuration Data, but looking at the line of Code with the NPE indicates one of your projects doesn't have any Configuration Data.
I think there is something wrong with one of your project area's process configuration that is causing this exception in during migration. I would start your RQM 2.0 server and connect to it using the RTC Eclipse client. I can't recall which version of the RTC eclipse client is compatible with RQM 2.0, but I would guess RTC 1.0. Once you have created a repository connection to your RQM server, you will want to "manage your connected project areas" and connect to all of them, even select the option to include archived project areas. Then right click each project area, open it and go to the process configuration tab. Then go under Project Configuration, Configuration Data. And make sure something is defined under the configuration data. For your migration issue, it doesn't matter what's defined under Configuration Data, just so long as the configuration data isn't empty. Looks like the migration code is assuming that all projects must have Configuration Data, else it will hit this issue. Typically, I think they would all have Configuration Data, but looking at the line of Code with the NPE indicates one of your projects doesn't have any Configuration Data.
Thanks for help. I have found one archived project area that didn't have
Configuration Data defined (also no roles) and I have fixed it. But unfortunately it didn't help. I still get the same error.
But I just start to think about the importance of it. The whole import finishes and I the data integration test passes on each of the 10 levels. I run it manually.
Is it possible that I don't miss any data even thought I'm getting that error?
Other question is, can I actually point to the old db for the new installation instead of running export-import with repotools? I did the addTables with reportools before importing to .tar wouldn't that be enough to get the db schema adjusted with the 2.0.1.1 installation?
Thanks in advance for help.
Configuration Data defined (also no roles) and I have fixed it. But unfortunately it didn't help. I still get the same error.
But I just start to think about the importance of it. The whole import finishes and I the data integration test passes on each of the 10 levels. I run it manually.
Is it possible that I don't miss any data even thought I'm getting that error?
Other question is, can I actually point to the old db for the new installation instead of running export-import with repotools? I did the addTables with reportools before importing to .tar wouldn't that be enough to get the db schema adjusted with the 2.0.1.1 installation?
Thanks in advance for help.
I did a search of the RQM project for any related defects, but didn't find anything that seemed connected to your issue. I'll give you some info, but if you have trouble solving the issue you should create a support ticket against RQM for this issue...
I think there is something wrong with one of your project area's process configuration that is causing this exception in during migration. I would start your RQM 2.0 server and connect to it using the RTC Eclipse client. I can't recall which version of the RTC eclipse client is compatible with RQM 2.0, but I would guess RTC 1.0. Once you have created a repository connection to your RQM server, you will want to "manage your connected project areas" and connect to all of them, even select the option to include archived project areas. Then right click each project area, open it and go to the process configuration tab. Then go under Project Configuration, Configuration Data. And make sure something is defined under the configuration data. For your migration issue, it doesn't matter what's defined under Configuration Data, just so long as the configuration data isn't empty. Looks like the migration code is assuming that all projects must have Configuration Data, else it will hit this issue. Typically, I think they would all have Configuration Data, but looking at the line of Code with the NPE indicates one of your projects doesn't have any Configuration Data.
It's not safe to assume that since the error happened in postImport that the data integrity of the migrated repo hasn't been jeopardized. It depends on what the RQM migration code is doing during postImport. Some times the migration code will modifying existing records or create new records, which could be prevented from happening if errors occurred during postImport.
Also, the upgrade instructions when going from 2.0 to 2.0.1 require that you do a repotools -export/-import. Just doing addTables and pointing to the old 2.0 database is not sufficient.
Also, the upgrade instructions when going from 2.0 to 2.0.1 require that you do a repotools -export/-import. Just doing addTables and pointing to the old 2.0 database is not sufficient.