May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11538) Opentracing - SmallRye - IllegalStateException

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11538?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11538: --------------------------------- Fix Version/s: 17.0.0.Final (was: 17.0.0.Beta1) > Opentracing - SmallRye - IllegalStateException > ---------------------------------------------- > > Key: WFLY-11538 > URL: https://issues.jboss.org/browse/WFLY-11538 > Project: WildFly > Issue Type: Bug > Components: MP OpenTracing > Affects Versions: 15.0.0.Final > Reporter: Alessandro Moscatelli > Priority: Major > Fix For: 17.0.0.Final > > > Caused by: org.jboss.weld.exceptions.IllegalStateException: WELD-000713: Unable to inject ServletContext. None is associated with ModuleClassLoader for Module > The problem is the interaction between these two: > https://github.com/wildfly/wildfly/blob/master/microprofile/opentracing-s... > https://github.com/smallrye/smallrye-opentracing/blob/1.1.1/implementatio... > Those are delivered with Wildfly 15 out of the box in: > smallrye-opentracing-1.1.1.jar > wildfly-microprofile-opentracing-smallrye-15.0.0.Final.jar > I have an EAR with a EJB jar, WAR and a common JAR library. > To reproduce the issue I created a Stateless EJB in the EJB jar and then I injected a Traced ApplicationScoped bean from the JAR library in the Stateless EJB. > SmallRyeTracingCDIInterceptor triggers and it requires an Injected Tracer. > TracerProducer triggers and it has no active ServletContext and this leads to the error above. > My suggestion: > I don't think the ServletContext is a really good place to store the Tracer. > I think that the Tracer created by Wildfly should be registered into the GlobalTracer. > This should be done by: > https://github.com/wildfly/wildfly/blob/master/microprofile/opentracing-s... > If you don't want Wildfly to register automatically its Tracer in the GlobalTracer, this behavior could be disabled in the subsystem. > Also please be aware that SmallRyeTracingCDIInterceptor is dismissed in the last versions of the library and SmallRye states (https://github.com/smallrye/smallrye-opentracing) it has been replaced with: > https://github.com/opentracing-contrib/java-interceptors/blob/master/src/... > Also be aware that what I am suggesting is similar to the same behavior adopted in opentracing java-cdi (not yet integrated in Wildfly): > https://github.com/opentracing-contrib/java-cdi/blob/master/opentracing-c... > https://github.com/opentracing-contrib/java-cdi/blob/master/opentracing-c... > Also notice that opentracing java-ejb (not yet integrated in Wildfly) also requires a registration in GlobalTracing: > https://github.com/opentracing-contrib/java-ejb/blob/master/opentracing-e... > Thank you for your support. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11492) Quickstart http-custom-mechanism: documentation step fails

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11492?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11492: --------------------------------- Fix Version/s: 17.0.0.Final (was: 17.0.0.Beta1) > Quickstart http-custom-mechanism: documentation step fails > ---------------------------------------------------------- > > Key: WFLY-11492 > URL: https://issues.jboss.org/browse/WFLY-11492 > Project: WildFly > Issue Type: Bug > Components: Documentation > Reporter: Alan Hantke > Assignee: Darran Lofthouse > Priority: Major > Fix For: 17.0.0.Final > > > Step #3, entitled *Configure the Application Security Domain* has the developer executing the following CLI command: > {code:java} > $ {jbossHomeName}/bin/jboss-cli.sh --connect --file=configure-security-domain.cli > {code} > However, this results in the following error: > {code:java} > The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): > WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed: > Step: step-1 > Operation: /subsystem=undertow/application-security-domain=other:add(http-authentication-factory=application-http-authentication) > Failure: WFLYCTL0369: Required capabilities are not available: > org.wildfly.security.http-authentication-factory.application-http-authentication; Possible registration points for this capability: > /subsystem=elytron/http-authentication-factory=* > {code} > I am by no means an expert on this, but in looking at the standalone.xml file, I think that there needs to be a mate for the inserted *application-http-authentication*. I have attempted to continue without this changes installed by the CLI, but I am unable to execute the webapp even after providing the correct user/pass in the BASIC AUTH. > I have verified that the same problem-causing syntax exists on the quickstart 'master', although I have been using branch '14.x' because neither 15.x nor 'master' would build when I execute 'mvn clean build'. Finally, the I encounter the problem with fresh installs of WildFly versions 10.1.0 and 14.0. > Please change change the project if I have categorized the ticket incorrectly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11904) No ActiveMQ connection factory with RAR deployment

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11904?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11904: --------------------------------- Fix Version/s: 17.0.0.Final (was: 17.0.0.Beta1) > No ActiveMQ connection factory with RAR deployment > -------------------------------------------------- > > Key: WFLY-11904 > URL: https://issues.jboss.org/browse/WFLY-11904 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Thomas Diesler > Assignee: Emmanuel Hugonnet > Priority: Major > Fix For: 17.0.0.Final > > > The ActiveMQ RAR deployment no longer registers its connection factory nor destination. > Is org.apache.activemq:activemq-rar:rar:5.15.7 no longer supported? > CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/2783 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11880) Add a SASL mechanism reference to the documentation

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11880?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11880: --------------------------------- Fix Version/s: 17.0.0.Final (was: 17.0.0.Beta1) > Add a SASL mechanism reference to the documentation > --------------------------------------------------- > > Key: WFLY-11880 > URL: https://issues.jboss.org/browse/WFLY-11880 > Project: WildFly > Issue Type: Task > Components: Documentation, Security > Reporter: Darran Lofthouse > Priority: Major > Fix For: 17.0.0.Final > > > A mechanism by mechanism listing, describing the mech, any features / requirements of the mech and any properties or other configuration affecting the mech. > This will need to cover both the client and server perspectives. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11879) Add a more in-depth section in the docs covering authentication.

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11879?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11879: --------------------------------- Fix Version/s: 17.0.0.Final (was: 17.0.0.Beta1) > Add a more in-depth section in the docs covering authentication. > ---------------------------------------------------------------- > > Key: WFLY-11879 > URL: https://issues.jboss.org/browse/WFLY-11879 > Project: WildFly > Issue Type: Task > Components: Documentation, Security > Reporter: Darran Lofthouse > Priority: Major > Fix For: 17.0.0.Final > > > A detailed authentication section, this will be huge but I don't think we have a clear picture of how the different pieces really come together i.e. realms, domains, mappers and decoders and subsequently the authentication factories. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11843) CXF-7994 - NumberFormatException on JDK13 in org.apache.cxf.helpers.JavaUtils

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11843?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11843: --------------------------------- Fix Version/s: 17.0.0.Final (was: 17.0.0.Beta1) > CXF-7994 - NumberFormatException on JDK13 in org.apache.cxf.helpers.JavaUtils > ----------------------------------------------------------------------------- > > Key: WFLY-11843 > URL: https://issues.jboss.org/browse/WFLY-11843 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 16.0.0.Final > Reporter: Richard Opalka > Assignee: Jim Ma > Priority: Major > Labels: jdk13 > Fix For: 17.0.0.Final > > > We are getting the following exception when running CXF on top of JDK13: > — > Failed to start service jboss.deployment.unit."ws-endpoint-example.war".INSTALL: org.jboss.msc.service.StartExceptio > <------>at org.jboss.as.server@8.0.1.CR1-SNAPSHOT//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183) > <------>at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738) > <------>at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700) > <------>at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558) > <------>at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > <------>at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > <------>at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > <------>at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363) > <------>at java.base/java.lang.Thread.run(Thread.java:835) > Caused by: java.lang.ExceptionInInitializerError > <------>at org.apache.cxf.impl//org.apache.cxf.jaxws.WrapperClassGenerator.generateMessagePart(WrapperClassGenerator.java:335) > <------>at org.apache.cxf.impl//org.apache.cxf.jaxws.WrapperClassGenerator.createWrapperClass(WrapperClassGenerator.java:224) > <------>at org.apache.cxf.impl//org.apache.cxf.jaxws.WrapperClassGenerator.generate(WrapperClassGenerator.java:122) > <------>at org.apache.cxf.impl//org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.generatedWrapperBeanClass(JaxWsServiceFactoryBean.java:674) > <------>at org.apache.cxf.impl//org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.getExtraClass(JaxWsServiceFactoryBean.java:644) > <------>at org.apache.cxf.impl//org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean.buildServiceFromClass(ReflectionServiceFactoryBean.java:464) > <------>at org.apache.cxf.impl//org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.buildServiceFromClass(JaxWsServiceFactoryBean.java:695) > <------>at org.apache.cxf.impl//org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean.initializeServiceModel(ReflectionServiceFactoryBean.java:530) > <------>at org.apache.cxf.impl//org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean.create(ReflectionServiceFactoryBean.java:263) > <------>at org.apache.cxf.impl//org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.create(JaxWsServiceFactoryBean.java:199) > <------>at org.apache.cxf.impl//org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:103) > <------>at org.apache.cxf.impl//org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:168) > <------>at org.apache.cxf.impl//org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:211) > <------>at org.apache.cxf.impl//org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:460) > <------>at org.apache.cxf.impl//org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:338) > <------>at org.jboss.ws.cxf.jbossws-cxf-server@5.2.4.Final//org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:79) > <------>at org.apache.cxf.impl//org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:255) > <------>at org.apache.cxf.impl//org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:543) > <------>at org.jboss.ws.cxf.jbossws-cxf-server@5.2.4.Final//org.jboss.wsf.stack.cxf.configuration.BusHolder.configure(BusHolder.java:235) > <------>at org.jboss.ws.cxf.jbossws-cxf-server@5.2.4.Final//org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:97) > <------>at org.jboss.ws.cxf.jbossws-cxf-server@5.2.4.Final//org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:59) > <------>at org.jboss.as.webservices//org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:73) > <------>at org.jboss.as.server@8.0.1.CR1-SNAPSHOT//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176) > <------>... 8 more > Caused by: java.lang.NumberFormatException: For input string: "13-ea" > <------>at java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:68) > <------>at java.base/java.lang.Integer.parseInt(Integer.java:658) > <------>at java.base/java.lang.Integer.valueOf(Integer.java:989) > <------>at org.apache.cxf(a)3.2.7//org.apache.cxf.helpers.JavaUtils.<clinit>(JavaUtils.java:65) > <------>... 31 more -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11825) CXF-7984 - UsernameTokenInterceptor doesn't respect contextual property "allowNamespaceQualifiedPasswordTypes"

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11825?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11825: --------------------------------- Fix Version/s: 17.0.0.Final (was: 17.0.0.Beta1) > CXF-7984 - UsernameTokenInterceptor doesn't respect contextual property "allowNamespaceQualifiedPasswordTypes" > -------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11825 > URL: https://issues.jboss.org/browse/WFLY-11825 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 16.0.0.Final > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > Labels: downstream_dependency > Fix For: 17.0.0.Final > > > allowNamespaceQualifiedPasswordTypes is not read from contextual properties before create wss4j UsernameToken. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11783) Rewrite some WildFly EE services to don't use deprecated MSC API

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11783?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11783: --------------------------------- Fix Version/s: 17.0.0.Final (was: 17.0.0.Beta1) > Rewrite some WildFly EE services to don't use deprecated MSC API > ---------------------------------------------------------------- > > Key: WFLY-11783 > URL: https://issues.jboss.org/browse/WFLY-11783 > Project: WildFly > Issue Type: Enhancement > Components: EE > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 17.0.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11759) Use LegacyKernelServicesInitializer to exclude problematic resources from UndertowTransformersTestCase

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11759?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11759: --------------------------------- Fix Version/s: 17.0.0.Final (was: 17.0.0.Beta1) > Use LegacyKernelServicesInitializer to exclude problematic resources from UndertowTransformersTestCase > ------------------------------------------------------------------------------------------------------ > > Key: WFLY-11759 > URL: https://issues.jboss.org/browse/WFLY-11759 > Project: WildFly > Issue Type: Task > Components: Web (Undertow) > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Minor > Fix For: 17.0.0.Final > > > Revert this workaround using the exclusion feature added by WFCORE-4346: > https://github.com/wildfly/wildfly/pull/12098 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12120) Upgrade websocket-api_1.1_spec to 1.1.4.Final

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-12120?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-12120: --------------------------------- Fix Version/s: 17.0.0.Final (was: 17.0.0.Beta1) > Upgrade websocket-api_1.1_spec to 1.1.4.Final > --------------------------------------------- > > Key: WFLY-12120 > URL: https://issues.jboss.org/browse/WFLY-12120 > Project: WildFly > Issue Type: Task > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Major > Fix For: 17.0.0.Final > > > Upgrade the version of websocket-api-spec 1.1 at the server to 1.1.4.Final -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2019