JWT-security has errors when used with opentracing extension.

[sean-scott-lr]

1. Follow the security-jwt guide link
2. Add opentracing extension ( add to pom.xml )

    <dependency>
      <groupId>io.quarkus</groupId>
      <artifactId>quarkus-smallrye-opentracing</artifactId>
    </dependency> 

3. Send a GET request to http://localhost:8080/secured/roles-allowed with no Authorization Header ( or with a bogus value for the Bearer token )
4. Observe log message

Caused by: java.io.IOException: UT000034: Stream is closed
        at io.undertow.servlet.spec.ServletOutputStreamImpl.write(ServletOutputStreamImpl.java:126)
        at io.undertow.servlet.spec.ServletOutputStreamImpl.write(ServletOutputStreamImpl.java:115)
        at org.jboss.resteasy.plugins.server.servlet.HttpServletResponseWrapper$DeferredOutputStream.write(HttpServletResponseWrapper.java:39)
        at org.jboss.resteasy.util.CommitHeaderOutputStream.write(CommitHeaderOutputStream.java:64)
        at org.jboss.resteasy.plugins.providers.StringTextStar.writeTo(StringTextStar.java:65)
        at org.jboss.resteasy.plugins.providers.StringTextStar.writeTo(StringTextStar.java:24)
        at org.jboss.resteasy.core.interception.jaxrs.AbstractWriterInterceptorContext.writeTo(AbstractWriterInterceptorContext.java:193)
        at org.jboss.resteasy.core.interception.jaxrs.ServerWriterInterceptorContext.writeTo(ServerWriterInterceptorContext.java:64)
        at org.jboss.resteasy.core.interception.jaxrs.AbstractWriterInterceptorContext.proceed(AbstractWriterInterceptorContext.java:155)
        at org.jboss.resteasy.core.ServerResponseWriter.lambda$writeNomapResponse$2(ServerResponseWriter.java:156)
        at org.jboss.resteasy.core.interception.jaxrs.ContainerResponseContextImpl.filter(ContainerResponseContextImpl.java:404)
        at org.jboss.resteasy.core.ServerResponseWriter.executeFilters(ServerResponseWriter.java:232)
        at org.jboss.resteasy.core.ServerResponseWriter.writeNomapResponse(ServerResponseWriter.java:97)
        at org.jboss.resteasy.core.ServerResponseWriter.writeNomapResponse(ServerResponseWriter.java:70)
        at org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:217)
        ... 57 more

[sean-scott-lr]

Version 1.0.0.CR1

[cescoffier]

@sberyozkin ?

[sberyozkin]

@sean-scott-lr @cescoffier quarkus-smallrye-jwt works with Vertx HTTP, right ? Just noticed the Undertow exception

[cescoffier]

You can still add quarkus-undertow as a dependency, and deploy your servlets.

[sberyozkin]

@cescoffier thanks, but here we have a JAX-RS app. Should the fix be about removing this dependency ? Otherwise I guess it has to be excluded in this case in the demo ?

[sberyozkin]

I will try to exclude

[sberyozkin]

Going to open a quarkus issue

[sean-scott-lr]

@sberyozkin Correct, I am not trying to use servlets or undertow. ( I have not added quarkus-undertow as a dependency) I am just using JAX-RS.

[sberyozkin]

@sean-scott-lr can you please exclude quarkus-undertow from quarkus-smallrye-opentracing ?
I'm getting

Caused by: java.lang.NoClassDefFoundError: io/quarkus/undertow/runtime/UndertowDeploymentRecorder

But the build itself passes when I remove this dependency in Quarkus master

[sean-scott-lr]

I tried changing the dependency in my pom.xml to

    <dependency>
      <groupId>io.quarkus</groupId>
      <artifactId>quarkus-smallrye-opentracing</artifactId>
      <exclusions>
        <exclusion>
          <groupId>io.quarkus</groupId>
          <artifactId>quarkus-undertow</artifactId>
        </exclusion>
      </exclusions>
    </dependency>

Still see this in the logs.

Caused by: java.io.IOException: UT000034: Stream is closed
        at io.undertow.servlet.spec.ServletOutputStreamImpl.write(ServletOutputStreamImpl.java:126)
        at io.undertow.servlet.spec.ServletOutputStreamImpl.write(ServletOutputStreamImpl.java:115)
        at org.jboss.resteasy.plugins.server.servlet.HttpServletResponseWrapper$DeferredOutputStream.write(HttpServletResponseWrapper.java:39)
        at org.jboss.resteasy.util.CommitHeaderOutputStream.write(CommitHeaderOutputStream.java:64)
        at org.jboss.resteasy.plugins.providers.StringTextStar.writeTo(StringTextStar.java:66)
        at org.jboss.resteasy.plugins.providers.StringTextStar.writeTo(StringTextStar.java:24)
        at org.jboss.resteasy.core.interception.jaxrs.AbstractWriterInterceptorContext.writeTo(AbstractWriterInterceptorContext.java:193)
        at org.jboss.resteasy.core.interception.jaxrs.ServerWriterInterceptorContext.writeTo(ServerWriterInterceptorContext.java:64)
        at org.jboss.resteasy.core.interception.jaxrs.AbstractWriterInterceptorContext.proceed(AbstractWriterInterceptorContext.java:155)
        at org.jboss.resteasy.core.ServerResponseWriter.lambda$writeNomapResponse$2(ServerResponseWriter.java:156)
        at org.jboss.resteasy.core.interception.jaxrs.ContainerResponseContextImpl.filter(ContainerResponseContextImpl.java:404)
        at org.jboss.resteasy.core.ServerResponseWriter.executeFilters(ServerResponseWriter.java:232)
        at org.jboss.resteasy.core.ServerResponseWriter.writeNomapResponse(ServerResponseWriter.java:97)
        at org.jboss.resteasy.core.ServerResponseWriter.writeNomapResponse(ServerResponseWriter.java:70)
        at org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:217)
        ... 57 more

Edit:
I should note that I see the result above using quarkus:dev... it appears that it is because the quarkus:dev maven extension is pulling in the undertow dependency itself. When I run the test target, I see the same result as @sberyozkin

[sberyozkin]

Opened quarkusio/quarkus#5419