Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

configured features microProfile-3.0 and usr:opent racinqZipkin-0.31 include one or more features that cause the conflict #9954

Closed
thomassuedbroecker opened this issue Nov 26, 2019 · 2 comments

Comments

@thomassuedbroecker
Copy link

@thomassuedbroecker thomassuedbroecker commented Nov 26, 2019

1. Describe the bug

This Bug is related to the update from MicroProfile 2.1 to MicroProfile 3 with OpenLiberty 19.0.0.9 and OpenTracing 1.3.

First I got following message.

MicroProfile 3 and usr:opentracinqZipkin-0.31 features can't be loaded at the same time.

Console output:

.. loaded at the same time. The configured features microProfile-3.0 and usr:opent
racinqZipkin-0.31 include one or more features that cause the conflict,

when usr:opentracinqZipkin-0.31 feature is removed the following Error message appears:

ERROR ] CWMOT0008E: OpenTracing cannot track JAX-RS requests because an Opentracing
TracerFactory class was not provided.

Here is an image with screen shots:

2019-11-26_13-39-52

2. Steps to Reproduce

Update a Microservice from MicroProfile 2.1 to MicroProfile 3-0.

a) Changing the container images from
open-liberty:microProfile2-java11 to open-liberty:19.0.0.9-kernel-java11.

b) Changes in the server.xml:

  • From microProfile-2.1 and opentracingZipkin-0.31 in the server.xml
<featureManager>
        <feature>webProfile-8.0</feature>
        <feature>microProfile-2.1</feature>
        <feature>usr:opentracingZipkin-0.31</feature>     
    </featureManager>
  • To microProfile-3.0 and opentracingZipkin-0.31 in the server.xml
<featureManager>
        <feature>microProfile-3.0</feature>
        <feature>webProfile-8.0</feature>
        <!-- <feature>usr:opentracingZipkin-0.31</feature> -->
</featureManager>

3. Expected behavior

The Microservice should work as before.

4. Diagnostic information:

  • OpenLiberty Version: open-liberty:19.0.0.9-kernel-java11
  • server.xml configuration (WITHOUT sensitive information like passwords)
<?xml version="1.0" encoding="UTF-8"?>
<server description="OpenLiberty Server">
	
    <featureManager>
        <feature>microProfile-3.0</feature>
        <feature>webProfile-8.0</feature>
        <!-- <feature>usr:opentracingZipkin-0.31</feature> -->
    </featureManager>

    <httpEndpoint id="defaultHttpEndpoint" host="*" httpPort="8080" httpsPort="9443"/>
    
    <!--
    <logging traceSpecification="*=info:JCDI=all:com.ibm.ws.webbeans*=all:org.jboss.weld*=all:com.ibm.ws.cdi*=all:com.ibm.ws.microrprofile.config*=all"
        traceFileName="trace.log"
        traceFormat="BASIC" /> -->
    
    <logging traceSpecification="com.ibm.ws.opentracing.*=all:com.ibm.ws.microprofile.opentracing.*=all"/>

    <!-- the following configuration is only needed if the persistence datastore db2 is used -->
    <library id="DB2JCCLib">
        <fileset dir="${shared.resource.dir}" includes="jcc*.jar"/>
    </library>

    <dataSource id="articlejpadatasource"
              jndiName="jdbc/articlejpadatasource">
        <jdbcDriver libraryRef="DB2JCCLib" />
        <properties.db2.jcc databaseName="BLUDB"
            portNumber="50000"
            serverName="DB2-SERVER"         
            user="DB2-USER" 
            password="DB2-PASSWORD" />
  </dataSource>
</server>
  • Server image from Dockerhub
    open-liberty:19.0.0.9-kernel-java11

5. Additional context

Maybe this problem is related to the issue #8037.

@fmhwong

This comment has been minimized.

Copy link
Member

@fmhwong fmhwong commented Nov 26, 2019

MicroProfile 2.1 includes mpOpenTracing-1.2. MicroProfile 3.0 includes mpOpenTracing-1.3. Please make sure you are using the Zipkin sample built for mpOpenTracing-1.3. It can be downloaded at https://github.com/WASdev/sample.opentracing.zipkintracer/releases/tag/1.3

@thomassuedbroecker

This comment has been minimized.

Copy link
Author

@thomassuedbroecker thomassuedbroecker commented Nov 27, 2019

@fmhwong Thanks now it works with "old" configuration in the server.xml.

Very important link in that case: https://github.com/WASdev/sample.opentracing.zipkintracer/tags

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.