Error upgrading from 3.0.1.1 to 4.0 - custom plugin related
We have a custom plugin for RTC. While upgrading from 3.0.1.1 to 4.0, our admins saw the following:
This error seems to be related this other post.
We got around it by removing the plugin's ini, update site, requesting a reset, restarting, shutting down and then running the upgrade script again. Once the upgrade was done, we re-installed the plugin and it worked okay.
Can someone explain what was causing this, and if there is a permanent fix that can be implemented to avoid adhoc workarounds?
Thanks,
Vivek
2012-08-03 10:03:28,063 The bundle org.eclipse.equinox.ds is STARTED. 2012-08-03 10:03:28,766 repotools-jazz -migration_ccm_updateConfigurationFiles applicationContextRoot=jazz jtsContextRoot=jts newApplicationHome=c:\RTC\RTC4-0\server\conf newJTSHome=C:\RTC\RTC4-0\server\conf oldApplicationHome=C:\RTC\RTC3-0-1-1\server\conf updateTomcatFiles=yes 2012-08-03 10:03:28,797 Change and Configuration Management - Core Libraries, Version 4.0 (RTC-I20120612-0919) Jazz Foundation - Core Libraries, Version 4.0 (RJF-I20120531-1400) 2012-08-03 10:03:36,486 CRJAZ1363I Loading the configuration from "bundleresource://364.fwk1053966034/teamserver.properties". 2012-08-03 10:03:36,548 Validating JTS configuration files... 2012-08-03 10:03:36,564 Checking the old application version... 2012-08-03 10:04:14,037 The version string "**** Activator !! <STOP METHOD>" is not properly formatted. java.lang.IllegalStateException: The version string "**** Activator !! <STOP METHOD>" is not properly formatted. at com.ibm.team.repotools.commands.upgrade.util.AbstractVersionChecker.getVersionStringFromOutput(AbstractVersionChecker.java:192) at com.ibm.team.repotools.commands.upgrade.util.AbstractVersionChecker.getVersionString(AbstractVersionChecker.java:125) at com.ibm.team.repotools.commands.upgrade.util.ApplicationVersionChecker.getOldApplicationVersion(ApplicationVersionChecker.java:66) at com.ibm.team.repotools.commands.upgrade.AbstractUpdateConfigurationFilesCommand.getOld30xApplicationVersionStringFromRepotools(AbstractUpdateConfigurationFilesCommand.java:2947) at com.ibm.team.repotools.commands.upgrade.ccm.CCMUpdateConfigurationFilesCommand.initializeOldApplicationVersion(CCMUpdateConfigurationFilesCommand.java:311) at com.ibm.team.repotools.commands.upgrade.AbstractUpdateConfigurationFilesCommand.validateOldApplicationVersion(AbstractUpdateConfigurationFilesCommand.java:810) at com.ibm.team.repotools.commands.upgrade.AbstractModelledApplicationUpdateConfigurationFiles.validatePreviousVersion(AbstractModelledApplicationUpdateConfigurationFiles.java:478) at com.ibm.team.repotools.commands.upgrade.AbstractUpdateConfigurationFilesCommand.validateJTSAndApplicationConfigurationFiles(AbstractUpdateConfigurationFilesCommand.java:1032) at com.ibm.team.repotools.commands.upgrade.AbstractModelledApplicationUpdateConfigurationFiles.validateJTSAndApplicationConfigurationFiles(AbstractModelledApplicationUpdateConfigurationFiles.java:84) at com.ibm.team.repotools.commands.upgrade.AbstractModelledApplicationUpdateConfigurationFiles.execute(AbstractModelledApplicationUpdateConfigurationFiles.java:34) 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:48) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:600) 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) 2012-08-03 10:04:14,037 CRJAZ1728E An unexpected error has been detected. See the log file "c:\RTC\RTC4-0\server\repotools-jazz_migration_ccm_updateConfigurationFiles.log" for more details.
This error seems to be related this other post.
We got around it by removing the plugin's ini, update site, requesting a reset, restarting, shutting down and then running the upgrade script again. Once the upgrade was done, we re-installed the plugin and it worked okay.
Can someone explain what was causing this, and if there is a permanent fix that can be implemented to avoid adhoc workarounds?
Thanks,
Vivek
Accepted answer
I am guessing that your custom plug-in prints the string
So assuming that's correct, the solution would be to remove all prints to the standard streams from you plug-in code (or perhaps turn them into debug log messages which would not appear by default).
"**** Activator !! "
to the standard output or error stream, probably in its bundle activator method. The upgrade script executes the "repotools -version" command to determine the old application version, and expects the output to be a version number. So if a plug-in loaded by repotools generates additional output, the code expecting just a version number will be surprised.
So assuming that's correct, the solution would be to remove all prints to the standard streams from you plug-in code (or perhaps turn them into debug log messages which would not appear by default).