Troubleshooting
Problem
Document Builder 6.0.6 or later versions cannot be deployed on the same application server profile as ELM (CLM). Document Builder has to be deployed on a separate profile.
Symptom
Error 400: RPENG license checkout failed.
Error is: javax/ws/rs/core/Response$Status$Family.familyOf(I)Ljavax/ws/rs/core/Response$Status$Family; (loaded from file:/C:/IBM/JazzTeamServer/server/liberty/wlp/lib/../dev/api/spec/com.ibm.websphere.javaee.jaxrs.1.1_1.0.20.jar by org.eclipse.osgi.internal.loader.EquinoxClassLoader@2fa6f102[com.ibm.websphere.javaee.jaxrs.1.1:1.0.20.cl180120180309-2209(id=140)]) called from class org.glassfish.jersey.message.internal.Statuses$StatusImpl (loaded from file:/C:/IBM/JazzTeamServer/server/liberty/servers/clm/workarea/org.eclipse.osgi/82/data/cache/com.ibm.ws.app.manager_230/.cache/.cache/rpeng.war/WEB-INF/lib/jersey-common.jar by com.ibm.ws.classloading.internal.AppClassLoader@3316db4c).
Cause
The issue is seen when both ELM (CLM) and Document Builder 6.0.6 or later versions are deployed within the same ELM (CLM) profile or server. Document Builder 6.0.6 or later versions cannot be deployed along with ELM (CLM) as ELM (CLM) includes Jersey 1.x version and Document Builder includes Jersey 2.x version, causing a conflict.
Environment
Document Builder deployed into the same profile that is used by Jazz Team Server.
Resolving The Problem
For WebSphere Application Server, create another profile in WebSphere Application Server and deploy Document Builder. For WebSphere Liberty, create a separate server and deploy Document Builder.
Product Synonym
Rational Publishing Engine; IBM Engineering Lifecycle Optimization - Publishing
Was this topic helpful?
Document Information
Modified date:
23 June 2020
UID
ibm10728091