I’ll try to have a look into the issue. Are you positive that the apps are being deployed correctly? I think there are a few cases where there is a silent error and the app fails to deploy hence, you see the 404. If you have REST endpoints going deployed, it is easy to see if these are ok, since they show up in the log when deployed. Can you confirm?
> On 23 Jan 2019, at 18:32, j4fm <[email protected]> wrote: > > So progress is good, I feel like it's close to working with MP. Took the > SystemInstance parent failover line out and now it's dependent on this issue > being resolved https://issues.apache.org/jira/browse/TOMEE-2458 which was > why it was put in the first place. I've worked around by adding all the > context dependencies to common.loader which is not ideal with the amount of > dependencies that would then affect all other webapps in TomEE. > > I will keep an eye out for the OpenAPI bump. > > Now I'm at: > > Every context deploys successfully but webapps are inaccessible (404 error) > because of an issue with doFilter on the contextbean we have. It's a > convertException on the invoke. > > I believe I had similar to this a while back with the TomEE MP edition and > you mentioned to set geronimo.opentracing.filter.active=false. So I set > that, and the error is gone but still leaves me with 404 not found... just > no errors at all that I can find. I get the impression it's almost working. > > > > -- > Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
