Troubleshooting
Problem
Some bundles might not be resolved when Engineering Workflow Management v6.0.6.1 client (previously known as Rational Team Concert) is installed shell shared with IBM Developer for z/OS v14.x.
Problems have been reported with both Installation Manager or P2 packages.
Problem might also appear after the installation of an interim fix for Engineering Workflow Management, like iFix010.
Symptom
The following error is display in view "MyWork":
| An internal error occurred during: "Load My Work". 'com.ibm.team.apt.shared.ui.internal.quickquery.QuickQueryDefinition' is not a constructor |
Cause
The error in the EWM view "MyWork" is caused by a conflict between EWM v6.0.6.1 and IDz v14.x, known as "guava" incompatibility:
| org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.wst.jsdt.core [osgi.identity; osgi.identity="org.eclipse.wst.jsdt.core"; type="osgi.bundle"; version:Version="2.0.250.201809271650"; singleton:="true"] because it is exposed to package 'com.google.common.collect' from resources com.google.guava [osgi.identity; osgi.identity="com.google.guava"; type="osgi.bundle"; version:Version="15.0.0.v201403281430"] and com.google.common [osgi.identity; osgi.identity="com.google.common"; type="osgi.bundle"; version:Version="18.0.0.v20181221_2153"] via two dependency chains. |
The conflict prevents bundle com.ibm.team.apt.shared.ui from being resolved and is therefore not registered by bundle com.ibm.team.rtc.common.scriptengine, which populates the view MyWork.
When EWM v6.0.6.1 is installed without IDz, the following traces can be observed:
|
!ENTRY com.ibm.team.rtc.common.scriptengine 1 0 2020-06-04 10:40:39.621
!MESSAGE Registred Script Bundles: org.dojotoolkit.dojox: namespace: 'dojox.' basefolder: '/resources/' ... com.ibm.team.apt.shared.ui: namespace: 'com.ibm.team.apt.shared.ui.' basefolder: '/resources/' com.ibm.team.apt.shared.client: namespace: 'com.ibm.team.apt.shared.client.' basefolder: '/resources/' |
EWM client v6.0.6.1 includes bundle com.google.common, which exports version 18 of package com.google.common.collect.
IDz v14.x includes 2 versions, v15 and v21, of bundle com.google.guava, which also exports package com.google.common.collect.
v15 is required by some m2e bundles like org.eclipse.m2e.editor.xml.
When both products are installed, Eclipse P2 detects that the same package is exported by 2 different bundles and does not manage to resolve the conflict.
A ResolutionException is raised which interrupts the resolution process.
Eclipse P2 tries to resolve bundles in multiple iterations (or "batch").
Each time an iteration is interrupted (either because of timeout or out of memory or exception), then Eclipse P2 checks whether some bundles could still be resolved before the interruption.
If it did, then P2 starts a new iteration with the remaining unresolved bundles.
If it did not, then the resolution process stops, and some bundles might not be resolved.
If the iteration starts with a bundle raising a ResolutionException, then no more bundles are resolved, the resolution process stops and Eclipse starts with the bundles that have been resolved until then.
Diagnosing The Problem
Create a file (like c:\temp\p2debug.option) with the following useful P2 options:
|
# Displays the current root bundle which is being resolved
org.eclipse.osgi/resolver/roots=true
# Displays wiring information after the resolve process completes. org.eclipse.osgi/resolver/wiring = true # Displays the resolution report information. org.eclipse.osgi/resolver/report = true |
Then, run the Eclipse workbench with the command like:
eclipsec.exe -debug c:\temp\p2debug.option -consoleLog > c:\temp\console.log 2>&1
Log shows entries like:
|
Resolver: resolving 348 in batch.
..
Resolving root bundle: osgi.identity; osgi.identity="com.ibm.team.apt.shared.ui"; type="osgi.bundle"; version:Version="3.0.2100.v20191109_0318"; singleton:="true"
...
org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.wst.jsdt.core [osgi.identity; type="osgi.bundle"; version:Version="2.0.250.201809271650"; osgi.identity="org.eclipse.wst.jsdt.core"; singleton:="true"] because it is exposed to package 'com.google.common.collect' from resources com.google.guava [osgi.identity; type="osgi.bundle"; version:Version="15.0.0.v201403281430"; osgi.identity="com.google.guava"] and com.google.common [osgi.identity; type="osgi.bundle"; version:Version="18.0.0.v20181221_2153"; osgi.identity="com.google.common"] via two dependency chains.
... Resolver: resolved 3 bundles.
Resolved bundle: osgi.identity; osgi.identity="com.ibm.team.filesystem.cli.client"; type="osgi.bundle"; version:Version="3.2.1300.v20200421_0400"; singleton:="true" Resolved bundle: osgi.identity; osgi.identity="com.ibm.team.filesystem.cli.core"; type="osgi.bundle"; version:Version="3.2.1300.v20200122_0354"; singleton:="true" Resolved bundle: osgi.identity; type="osgi.bundle"; version:Version="3.1.1200.v20190114_1851"; osgi.identity="com.ibm.team.filesystem.cli.minimal" ... Resolver: resolving 106 in batch.
...
Resolving root bundle: osgi.identity; osgi.identity="com.ibm.team.apt.shared.ui"; type="osgi.bundle"; version:Version="3.0.2100.v20191109_0318"; singleton:="true"
...
RESOLVER: Resolution report
com.ibm.team.rtc.foundation.jdojo.stubs [2303] |
Resolving The Problem
Restart Eclipse with -clean option
Run the Engineering Workflow Management client with -clean option should resolve the missing bundles.
On Microsoft® Windows®, -clean should be run by using menu "Run as administrator" (specially if installed under c:\Program Files)
Some other less practical or less effective solutions:
Use OSGI console
- Run Eclipse with -console option
- Open the Console view and select the Host OSGI console
- Enter command: diag
- Search for bundle com.ibm.team.apt.shared.ui
- Start the bundle manually by using command: start 2277
(where 2277 is the bundle id find previously)
- Restart Eclipse and check whether view "My Work" is displayed without errors.
Install Engineering Workflow Management interim fix with option equinox.resolver.batch.timeout=5000
Another possible solution is to add the option -Dequinox.resolver.batch.timeout=5000 to eclipse.ini before installing the Engineering Workflow Management interim fix.
The Eclipse resolver process then stops iteration with a timeout rather than a final ResolutionException.
Document Location
Worldwide
[{"Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSJK49","label":"IBM Developer for z Systems"},"ARM Category":[{"code":"a8m0z00000009ClAAI","label":"IDz Family"}],"ARM Case Number":"TS003459921","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]
Was this topic helpful?
Document Information
Modified date:
02 October 2020
UID
ibm16325281