It's all about the answers!

Ask a question

repotools error on export


Anthony Giordano (2762615) | asked Aug 12 '09, 7:58 p.m.
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



permanent link
Krzysztof Ka┼║mierczyk (7.4k34693) | answered Oct 07 '10, 9:30 a.m.
try
repotools -clean -isServerRunning

permanent link
Paul Sims (31513321) | answered Sep 12 '09, 2:32 p.m.
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

permanent link
Robert Studera (4151) | answered Sep 14 '09, 10:27 a.m.
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


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

permanent link
Paul Sims (31513321) | answered Sep 14 '09, 10:57 a.m.
Thanks Robert, I used the workaround too, but am still concerned about the significance of the framework errors. The messages are rather cryptic.


2009-09-12 14:22:37.062 - FrameworkManager: (SAT-110.1101) A framework error has occurred.
org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Another singleton version selected: com.ibm.team.repos
itory.servlet_0.6.1.M200811102216
2009-09-12 14:22:37.109 - FrameworkManager: (SAT-110.1101) A framework error has occurred.
org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Another singleton version selected: com.ibm.team.repos
itory.service.monitoring_0.6.1.M200811072039
2009-09-12 14:22:37.140 - FrameworkManager: (SAT-110.1101) A framework error has occurred.
org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Another singleton version selected: com.ibm.team.repos
itory.jdbcdriver.oracle_0.6.1.M200811072039
2009-09-12 14:22:37.171 - FrameworkManager: (SAT-110.1101) A framework error has occurred.
org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Another singleton version selected: com.ibm.team.repos
itory.jdbcdriver.sqlserver_0.6.1.M200902052204
CRJAZ1218I The bundle "com.ibm.team.repository.servlet" with the id 45 is invalid, it is not "RESOLVED".
CRJAZ1218I The bundle "com.ibm.team.repository.service.monitoring" with the id 46 is invalid, it is not "RESOLVED".
CRJAZ1218I The bundle "com.ibm.team.repository.jdbcdriver.oracle" with the id 49 is invalid, it is not "RESOLVED".
CRJAZ1218I The bundle "com.ibm.team.repository.jdbcdriver.sqlserver" with the id 51 is invalid, it is not "RESOLVED".



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

permanent link
Balaji Krish (1.8k12) | answered Sep 16 '09, 5:23 p.m.
JAZZ DEVELOPER
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.


2009-09-12 14:22:37.062 - FrameworkManager: (SAT-110.1101) A framework error has occurred.
org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Another singleton version selected: com.ibm.team.repos
itory.servlet_0.6.1.M200811102216
2009-09-12 14:22:37.109 - FrameworkManager: (SAT-110.1101) A framework error has occurred.
org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Another singleton version selected: com.ibm.team.repos
itory.service.monitoring_0.6.1.M200811072039
2009-09-12 14:22:37.140 - FrameworkManager: (SAT-110.1101) A framework error has occurred.
org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Another singleton version selected: com.ibm.team.repos
itory.jdbcdriver.oracle_0.6.1.M200811072039
2009-09-12 14:22:37.171 - FrameworkManager: (SAT-110.1101) A framework error has occurred.
org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Another singleton version selected: com.ibm.team.repos
itory.jdbcdriver.sqlserver_0.6.1.M200902052204
CRJAZ1218I The bundle "com.ibm.team.repository.servlet" with the id 45 is invalid, it is not "RESOLVED".
CRJAZ1218I The bundle "com.ibm.team.repository.service.monitoring" with the id 46 is invalid, it is not "RESOLVED".
CRJAZ1218I The bundle "com.ibm.team.repository.jdbcdriver.oracle" with the id 49 is invalid, it is not "RESOLVED".
CRJAZ1218I The bundle "com.ibm.team.repository.jdbcdriver.sqlserver" with the id 51 is invalid, it is not "RESOLVED".



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

permanent link
Paul Sims (31513321) | answered Sep 17 '09, 7:11 a.m.
Thanks Balaji, I will run a clean first and let you know what happens afterwards.

Paul Sims, Agile Development Coach
IBM WebSphere Commerce

permanent link
Paul Sims (31513321) | answered Sep 28 '09, 3:36 p.m.
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


Register or to post your answer.