It's all about the answers!

Ask a question

Error upgrading from to 4.0 - custom plugin related

Vivek Iyer (15212527) | asked Aug 03 '12, 4:14 p.m.
retagged Aug 06 '12, 1:17 p.m. by Chris Goldthorpe (4287)
We have a custom plugin for RTC. While upgrading from to 4.0, our admins saw the following:

 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/". 
 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 org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication( 
     at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start( 
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
     at sun.reflect.NativeMethodAccessorImpl.invoke( 
     at sun.reflect.DelegatingMethodAccessorImpl.invoke( 
     at java.lang.reflect.Method.invoke( 
     at org.eclipse.equinox.launcher.Main.invokeFramework( 
     at org.eclipse.equinox.launcher.Main.basicRun( 
     at org.eclipse.equinox.launcher.Main.main( 
 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?



Accepted answer

permanent link
John Vasta (2.6k15) | answered Aug 13 '12, 11:50 a.m.
I am guessing that your custom plug-in prints the string "**** 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).
Vivek Iyer selected this answer as the correct answer

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.