[jboss-jira] [JBoss JIRA] (WFLY-10847) Multiple service modules in single EAR use same tracer instance

[Juraci Paixão Kröhling (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-10847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620027#comment-13620027 ] 

Juraci Paixão Kröhling commented on WFLY-10847:
-----------------------------------------------

I was just talking with [~mkouba] on IRC about this one, and he made me realize that we might actually indeed want only one tracer instance per EAR, if we deem the EAR as being the "service". Previously, I had in mind that each WAR would be a service on its own, given that people are explicitly packaging WARs into a single EAR is a hint that they see that as a single service.

[~objectiser], [~pilhuhn], what do you think? What makes more sense, one service per EAR, or one service per WAR (potentially having multiple services per EAR)?

> Multiple service modules in single EAR use same tracer instance
> ---------------------------------------------------------------
>
>                 Key: WFLY-10847
>                 URL: https://issues.jboss.org/browse/WFLY-10847
>             Project: WildFly
>          Issue Type: Bug
>          Components: MP OpenTracing
>            Reporter: Michal Jurc
>            Assignee: Juraci Paixão Kröhling
>            Priority: Blocker
>             Fix For: 14.0.0.CR1
>
>
> When deploying an EAR with two stand-alone JAX-RS services in stand-alone WAR modules, both of the services use the same {{Tracer}} instance.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)