repotools error on export
exporting from 1.0.1.1 to file I'm getting this error:
C:\Program Files\IBM\JazzTeamServer\server>repotools -export toFile=e:\export.ta r 2009-08-12 19:47:19.691 - FrameworkManager: (SAT-110.1101) A framework e rror has occurred. org.osgi.framework.BundleException: The bundle could not be resolved. Reason: An other singleton version selected: com.ibm.team.repository.servlet_0.6.1.M2008111 02216 at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(Bundl eHost.java:305) at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(Abstra ctBundle.java:350) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Frame work.java:1118) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBund les(StartLevelManager.java:634) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(St artLevelManager.java:508) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStart Level(StartLevelManager.java:282) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEv ent(StartLevelManager.java:468) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventM anager.java:195) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(Even tManager.java:297) 2009-08-12 19:47:19.707 - FrameworkManager: (SAT-110.1101) A framework e rror has occurred. org.osgi.framework.BundleException: The bundle could not be resolved. Reason: An other singleton version selected: com.ibm.team.repository.service.monitoring_0.6 ..1.M200811072039 at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(Bundl eHost.java:305) at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(Abstra ctBundle.java:350) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Frame work.java:1118) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBund les(StartLevelManager.java:634) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(St artLevelManager.java:508) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStart Level(StartLevelManager.java:282) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEv ent(StartLevelManager.java:468) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventM anager.java:195) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(Even tManager.java:297) 2009-08-12 19:47:19.723 - FrameworkManager: (SAT-110.1101) A framework e rror has occurred. org.osgi.framework.BundleException: The bundle could not be resolved. Reason: An other singleton version selected: com.ibm.team.repository.jdbcdriver.oracle_0.6. 1.M200811072039 at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(Bundl eHost.java:305) at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(Abstra ctBundle.java:350) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Frame work.java:1118) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBund les(StartLevelManager.java:634) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(St artLevelManager.java:508) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStart Level(StartLevelManager.java:282) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEv ent(StartLevelManager.java:468) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventM anager.java:195) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(Even tManager.java:297) Repo Tools, Version 1.0.1.1 - M20090225-1543 Provisioning using "C:\Program Files\IBM\JazzTeamServer\server\\provision_profil es". CRJAZ1218I The bundle "com.ibm.team.repository.servlet" with the id 51 is invali d, it is not "RESOLVED". CRJAZ1218I The bundle "com.ibm.team.repository.service.monitoring" with the id 5 2 is invalid, it is not "RESOLVED". CRJAZ1218I The bundle "com.ibm.team.repository.jdbcdriver.oracle" with the id 55 is invalid, it is not "RESOLVED". To ignore invalid bundles, re-run repotools with the following property definiti on enabled in the script: -Dcom.ibm.team.repotools.rcp.allowInvalidBundles=true CRJAZ1225I Migration failed. |
7 answers
I believe you updated from a previous version of RTC. The update did not completely clean up the configuration.
Please run repotools -clean before running an export. --- Balaji Jazz Server Team Thanks Robert, I used the workaround too, but am still concerned about the significance of the framework errors. The messages are rather cryptic.
My question remains. What effect might ignoring invalid bundles have in the future? If a development team member tells me it's insignificant, I'm happy to proceed without concern. Paul Sims, Agile Development Coach IBM WebSphere Commerce |
try
repotools -clean -isServerRunning |
Hi Tony, I'm getting the same error. Have you made progress? Did you try ignoring invalid bundles as the message suggests?
Can someone tell us the significance of this error and what effect ignoring invalid bundles might have? Paul Sims, Agile Development Coach IBM WebSphere Commerce |
Hi Tony, I'm getting the same error. Have you made progress? Did you try ignoring invalid bundles as the message suggests? We ran into the same problem. When you look into the corresponding repotools_*.log, you will find a suggestion how to solve that problem. Add set DEFINE=%DEFINE% -Dcom.ibm.team.repotools.rcp.allowInvalidBundles=true to the repotools.bat There will be still warnings at the beginning, but afterwards repotools will continue with the work. Greetings |
Thanks Robert, I used the workaround too, but am still concerned about the significance of the framework errors. The messages are rather cryptic.
My question remains. What effect might ignoring invalid bundles have in the future? If a development team member tells me it's insignificant, I'm happy to proceed without concern. Paul Sims, Agile Development Coach IBM WebSphere Commerce |
Thanks Balaji, I will run a clean first and let you know what happens afterwards.
Paul Sims, Agile Development Coach IBM WebSphere Commerce |
Hi Balaji, I just ran repotools -clean on V1.0.1.1 and found that "-clean" is not a valid option. Please advise.
D:\Program Files\IBM\JazzTeamServer\server>repotools -clean Repo Tools, Version 1.0.1.1 - M20090225-1543 Usage: repotools <addTables> -addTables --Add database tables. --Path to the teamserver.properties file. --Path to the log file. -clone --Create a clone of a repository (special purpose). See the product documentation for details. toFile=<value> --Path to the TAR file. target.teamserver.properties=<value> --Path to the target teamserver.properties file. --Path to the source teamserver.properties file. --Path to the log file. --Whether to overwrite an existing TAR file. --Do not prompt before creating the tables prior to importing. --Do not perform imported data verification. -convertTomcatUsers --Convert a tomcat-users.xml to encrypted passwords. --The path to the tomcat users file. --Path to the log file. -copy --Copy data from one database to another, via a TAR file. toFile=<value> --Path to the TAR file. target.teamserver.properties=<value> --Path to the target teamserver.properties file. --Path to the source teamserver.properties file. --Path to the log file. --Whether to overwrite an existing TAR file. --Do not prompt before creating the tables prior to importing. --Do not perform imported data verification. -createTables --Create the database tables. --Path to the teamserver.properties file. --Path to the log file. --Do not prompt before creating the tables. -dropTables --Drop the database tables. --Path to the teamserver.properties file. --Path to the log file. --Do not prompt before dropping the tables. -export --Export the contents of the database tables to a TAR files. toFile=<value> --Path to the TAR file. --Path to the teamserver.properties file. --Path to the log file. --Whether to overwrite an existing TAR file. -import --Import the contents of a TAR into newly create database tables. fromFile=<value> --Path to the TAR file. --Path to the teamserver.properties file. --Path to the log file. --Do not prompt before creating the tables prior to importing. --Do not perform imported data verification. -isServerRunning --Check to see if the server is running. --Path to the teamserver.properties file. --Path to the log file. -rebuildIndices --Rebuild the database's indices. --Path to the teamserver.properties file. --Path to the log file. -rebuildTextIndices --Rebuild text indices. --Path to the teamserver.properties file. --Path to the log file. -verify --Verify the integrity of the database tables. --Path to the teamserver.properties file. --Path to the log file. --The level at which to perform verification. Examples: repotools -addTables repotools -clone toFile=/export.tar target.teamserver.properties=db.properties repotools -convertTomcatUsers tomcatUsersPath=tomcat/conf/tomcat-users.xml repotools -copy toFile=/export.tar target.teamserver.properties=db.properties repotools -createTables repotools -dropTables repotools -export toFile=/export.tar repotools -import fromFile=/export.tar repotools -isServerRunning repotools -rebuildIndices repotools -rebuildTextIndices repotools -verify level=5 Paul Sims, Agile Development Coach IBM WebSphere Commerce |
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.