Re: TomEE 8 M1 - MP

In the current state it is a bug. It should be enabled by default, but the app should deploy properly and you should keep access to all the usual stuff: console, docs, etc. I’ll open up an issue. Thank you! Cheers, Roberto > On 5 Nov 2018, at 12:30, j4fm wrote: > > That works. Is this

Re: TomEE 8 M1 - MP

That works. Is this something that will be made default and then an app can enable when it wants to use opentracing? Thank you -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: TomEE 8 M1 - MP

The built-in apps should have a MP config entry with the value geronimo.opentracing.filter.active=false, you can workaround it adding in the exploded webapp a WEB-INF/classes/META-INF/microprofile-config.properties with this value Romain Manni-Bucau @rmannibucau

Re: TomEE 8 M1 - MP

Tested with an app and without an app present. Without an app, shouldn't I still be able to reach the tomee status/manager pages? If I remove MP opentracing jars, status/manager pages are reachable both with and without an app. Thanks -- Sent from:

Re: TomEE 8 M1 - MP

Hi James, You are deploying an app with it, right? > On 2 Nov 2018, at 11:32, j4fm wrote: > > I ran the tomee:8-jre-8.0.0-M1-microprofile Docker container. Although TomEE > starts up just fine, I cannot access it because of the following error (I > don't think this is Docker specific). If I

TomEE 8 M1 - MP

I ran the tomee:8-jre-8.0.0-M1-microprofile Docker container. Although TomEE starts up just fine, I cannot access it because of the following error (I don't think this is Docker specific). If I move the Microprofile tracing JARs out of the lib folder before start, then I can access TomEE fine.