[JBoss JIRA] (WFLY-10967) Jaeger Tracing: No sender found
by Harald Wellmann (JIRA)
Harald Wellmann created WFLY-10967:
--------------------------------------
Summary: Jaeger Tracing: No sender found
Key: WFLY-10967
URL: https://issues.jboss.org/browse/WFLY-10967
Project: WildFly
Issue Type: Bug
Components: MP OpenTracing
Affects Versions: 14.0.0.Final
Reporter: Harald Wellmann
I'm not really sure what the intended behaviour is, but is seems that MicroProfile OpenTracing does not work out of the box.
When deploying a JAX-RS + CDI application, I get the following warning
{noformat}
16:37:49,023 WARN [io.jaegertracing.internal.senders.SenderResolver] (ServerService Thread Pool -- 73) No suitable sender found. Using NoopSender, meaning that data will not be sent anywhere!
{noformat}
My guess is that the module configuration is not quite correct. After adding the following dependencies, things look better:
module io.jaegertracing.jaeger-core:
{code:xml}
<module name="io.jaegertracing.jaeger-thrift" services="import"/>
{code}
module io.jaegertracing.jaeger-thrift:
{code:xml}
<module name="org.apache.thrift"/>
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
- 1
- 0
[JBoss JIRA] (WFLY-10966) Add version 8 of the Undertow subsystem schema and model
by Darran Lofthouse (JIRA)
Darran Lofthouse created WFLY-10966:
---------------------------------------
Summary: Add version 8 of the Undertow subsystem schema and model
Key: WFLY-10966
URL: https://issues.jboss.org/browse/WFLY-10966
Project: WildFly
Issue Type: Task
Components: Web (Undertow)
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 15.0.0.Alpha1
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
- 1
- 0
[JBoss JIRA] (WFLY-10829) Exclude ironjacamar-spec-api from the transitive depenencies
by Lin Gao (JIRA)
[ https://issues.jboss.org/browse/WFLY-10829?page=com.atlassian.jira.plugin... ]
Lin Gao reassigned WFLY-10829:
------------------------------
Assignee: Lin Gao (was: Stefano Maestri)
> Exclude ironjacamar-spec-api from the transitive depenencies
> ------------------------------------------------------------
>
> Key: WFLY-10829
> URL: https://issues.jboss.org/browse/WFLY-10829
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Reporter: Kabir Khan
> Assignee: Lin Gao
>
> Although not part of the server runtime, the ironjacamar-spec-api is included as a transitive dependency. This fixes it:
> {code}
> --- pom.xml
> +++ pom.xml
> @@ -4314,6 +4326,10 @@
> <version>\${version.org.jboss.ironjacamar}</version>
> <exclusions>
> <exclusion>
> + <artifactId>ironjacamar-spec-api</artifactId>
> + <groupId>org.jboss.ironjacamar</groupId>
> + </exclusion>
> + <exclusion>
> <artifactId>jbossxb</artifactId>
> <groupId>org.jboss</groupId>
> </exclusion>
> @@ -4346,6 +4362,10 @@
> <version>\${version.org.jboss.ironjacamar}</version>
> <exclusions>
> <exclusion>
> + <groupId>org.jboss.ironjacamar</groupId>
> + <artifactId>ironjacamar-spec-api</artifactId>
> + </exclusion>
> + <exclusion>
> <artifactId>jboss-integration</artifactId>
> <groupId>org.jboss.integration</groupId>
> </exclusion>
> @@ -4376,6 +4396,10 @@
> <version>\${version.org.jboss.ironjacamar}</version>
> <exclusions>
> <exclusion>
> + <groupId>org.jboss.ironjacamar</groupId>
> + <artifactId>ironjacamar-spec-api</artifactId>
> + </exclusion>
> + <exclusion>
> <artifactId>jboss-common-core</artifactId>
> <groupId>org.jboss</groupId>
> </exclusion>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
- 1
- 0