December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4854) Exclude org.jboss.logmanager:jboss-logmanager from wildfly-client-all (jboss-client.jar)

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4854?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4854. ---------------------------- > Exclude org.jboss.logmanager:jboss-logmanager from wildfly-client-all (jboss-client.jar) > ---------------------------------------------------------------------------------------- > > Key: WFLY-4854 > URL: https://issues.jboss.org/browse/WFLY-4854 > Project: WildFly > Issue Type: Bug > Components: Application Client > Reporter: Martin Simka > Assignee: Jeff Mesnil > Fix For: 10.0.0.Alpha5 > > > Exclude org.jboss.logmanager:jboss-logmanager from wildfly-client-all (jboss-client.jar) > its presence causes TCK failures with error: > {noformat} > IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager") > {noformat} > as LogManager is loaded twice, from jboss-client.jar and from module. It was brought in together with ActiveMQ Artemis messaging. > {noformat} > [INFO] --- maven-dependency-plugin:2.9:tree (default-cli) @ wildfly-client-all --- > [INFO] org.wildfly:wildfly-client-all:jar:10.0.0.Alpha5-SNAPSHOT > [INFO] +- org.wildfly:wildfly-ejb-client-bom:pom:10.0.0.Alpha5-SNAPSHOT:compile > [INFO] | +- org.jboss:jboss-ejb-client:jar:2.1.1.Final:compile > [INFO] | +- org.jboss:jboss-remote-naming:jar:2.0.4.Final:compile > [INFO] | +- org.jboss.logging:jboss-logging:jar:3.2.1.Final:compile > [INFO] | +- org.jboss.marshalling:jboss-marshalling:jar:1.4.10.Final:compile > [INFO] | +- org.jboss.marshalling:jboss-marshalling-river:jar:1.4.10.Final:compile > [INFO] | +- org.jboss.remoting:jboss-remoting:jar:4.0.9.Final:compile > [INFO] | +- org.jboss.sasl:jboss-sasl:jar:1.0.5.Final:compile > [INFO] | +- org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec:jar:1.0.0.Final:compile > [INFO] | +- org.jboss.spec.javax.ejb:jboss-ejb-api_3.2_spec:jar:1.0.0.Final:compile > [INFO] | +- org.jboss.xnio:xnio-api:jar:3.3.1.Final:compile > [INFO] | \- org.jboss.xnio:xnio-nio:jar:3.3.1.Final:compile > [INFO] +- org.wildfly:wildfly-jms-client-bom:pom:10.0.0.Alpha5-SNAPSHOT:compile > [INFO] | +- org.apache.activemq:artemis-commons:jar:1.0.0:compile > [INFO] | | +- org.jboss.logmanager:jboss-logmanager:jar:2.0.0.Final:compile > [INFO] | | \- commons-beanutils:commons-beanutils:jar:1.9.2:compile > [INFO] | | \- commons-collections:commons-collections:jar:3.2.1:compile > [INFO] | +- org.apache.activemq:artemis-core-client:jar:1.0.0:compile > [INFO] | | +- org.jgroups:jgroups:jar:3.6.4.Final:compile > [INFO] | | +- org.apache.activemq:artemis-selector:jar:1.0.0:compile > [INFO] | | \- org.apache.activemq:artemis-journal:jar:1.0.0:compile > [INFO] | | \- org.apache.activemq:artemis-native:jar:1.0.0:compile > [INFO] | +- org.apache.activemq:artemis-jms-client:jar:1.0.0:compile > [INFO] | | +- org.apache.geronimo.specs:geronimo-jms_2.0_spec:jar:1.0-alpha-1:compile > [INFO] | | \- javax.inject:javax.inject:jar:1:compile > [INFO] | +- org.hornetq:hornetq-commons:jar:2.4.7.Final:compile > [INFO] | +- org.hornetq:hornetq-core-client:jar:2.4.7.Final:compile > [INFO] | | \- org.hornetq:hornetq-journal:jar:2.4.7.Final:compile > [INFO] | | \- org.hornetq:hornetq-native:jar:2.4.7.Final:compile > [INFO] | +- org.hornetq:hornetq-jms-client:jar:2.4.7.Final:compile > [INFO] | +- io.netty:netty-all:jar:4.0.26.Final:compile > [INFO] | +- org.jboss.spec.javax.jms:jboss-jms-api_2.0_spec:jar:1.0.0.Final:compile > [INFO] | \- org.slf4j:jcl-over-slf4j:jar:1.7.7.jbossorg-1:compile > [INFO] | \- org.slf4j:slf4j-api:jar:1.7.7.jbossorg-1:compile > [INFO] +- org.jboss.remotingjmx:remoting-jmx:jar:2.0.1.Final:compile > [INFO] \- org.wildfly.checkstyle:wildfly-checkstyle-config:jar:1.0.3.Final:compile > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5099) Transaction subsystem startup failed with setting the "use-hornetq-store"

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5099?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5099. ---------------------------- > Transaction subsystem startup failed with setting the "use-hornetq-store" > ------------------------------------------------------------------------- > > Key: WFLY-5099 > URL: https://issues.jboss.org/browse/WFLY-5099 > Project: WildFly > Issue Type: Bug > Components: Transactions > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 10.0.0.Beta2 > > > using <use-hornetq-store enable-async-io="true"/> in standalone.xml and wildfly starts failed with > {code} > 21:45:42,140 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "transactions")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.txn.ArjunaRecoveryManager" => "org.jboss.msc.service.StartException in service jboss.txn.ArjunaRecoveryManager: Failed to start service > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError: ARJUNA012135: Could not create Store type: com.arjuna.ats.internal.arjuna.objectstore.hornetq.HornetqObjectStoreAdaptor > Caused by: java.lang.NoClassDefFoundError: org/apache/activemq/artemis/core/journal/SequentialFileFactory > Caused by: java.lang.ClassNotFoundException: org.apache.activemq.artemis.core.journal.SequentialFileFactory from [Module \"org.jboss.jts:main\" from local module loader @2aae9190 (finder: local module finder @2f333739 (roots: /home/zhfeng/work/zhfeng/jboss-as/build/target/wildfly-10.0.0.Beta2-SNAPSHOT/modules,/home/zhfeng/work/zhfeng/jboss-as/build/target/wildfly-10.0.0.Beta2-SNAPSHOT/modules/system/layers/base))]"}} > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5052) NoClassDefFoundError at JAX-WS webservice deployment

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5052?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5052. ---------------------------- > NoClassDefFoundError at JAX-WS webservice deployment > ---------------------------------------------------- > > Key: WFLY-5052 > URL: https://issues.jboss.org/browse/WFLY-5052 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 9.0.1.Final > Reporter: Gregory Lardiere > Assignee: Alessio Soldano > Fix For: 10.0.0.Beta1 > > Attachments: SampleWS.war, SampleWS.zip > > > The exception *java.lang.NoClassDefFoundError: org/apache/ws/commons/schema/XmlSchemaAllMember* is thrown when deploying a JAX-WS webservice : > {code} > 2015-08-04 16:32:18,222 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."SampleWS.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."SampleWS.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "SampleWS.war" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NoClassDefFoundError: org/apache/ws/commons/schema/XmlSchemaAllMember > at org.apache.cxf.common.xmlschema.SchemaCollection.addCrossImports(SchemaCollection.java:315) > at org.apache.cxf.common.xmlschema.SchemaCollection.addCrossImportsType(SchemaCollection.java:307) > at org.apache.cxf.common.xmlschema.SchemaCollection.addOneSchemaCrossImports(SchemaCollection.java:252) > at org.apache.cxf.common.xmlschema.SchemaCollection.addCrossImports(SchemaCollection.java:236) > at org.apache.cxf.jaxb.JAXBSchemaInitializer.buildExceptionType(JAXBSchemaInitializer.java:605) > at org.apache.cxf.jaxb.JAXBSchemaInitializer.checkForExistence(JAXBSchemaInitializer.java:326) > at org.apache.cxf.jaxb.JAXBSchemaInitializer.begin(JAXBSchemaInitializer.java:150) > at org.apache.cxf.service.ServiceModelVisitor.visitOperation(ServiceModelVisitor.java:120) > at org.apache.cxf.service.ServiceModelVisitor.walk(ServiceModelVisitor.java:74) > at org.apache.cxf.jaxb.JAXBDataBinding.initialize(JAXBDataBinding.java:403) > at org.apache.cxf.service.factory.AbstractServiceFactoryBean.initializeDataBindings(AbstractServiceFactoryBean.java:86) > at org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean.buildServiceFromClass(ReflectionServiceFactoryBean.java:467) > at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.buildServiceFromClass(JaxWsServiceFactoryBean.java:712) > at org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean.initializeServiceModel(ReflectionServiceFactoryBean.java:527) > at org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean.create(ReflectionServiceFactoryBean.java:261) > at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.create(JaxWsServiceFactoryBean.java:215) > at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:102) > at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:159) > at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:211) > at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:456) > at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:334) > at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:79) > at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:251) > at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:539) > at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:119) > at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:120) > at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:66) > at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:73) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156) > ... 5 more > Caused by: java.lang.ClassNotFoundException: org.apache.ws.commons.schema.XmlSchemaAllMember from [Module "org.apache.cxf:main" from local module loader @14899482 (finder: local module finder @21588809 (roots: /tmp/wildfly-9.0.1.Final/modules,/tmp/wildfly-9.0.1.Final/modules/system/layers/base))] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130) > ... 34 more > {code} > Replacing xmlschema-core-2.0.2.jar with xmlschema-core-2.2.1.jar fixes this problem. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4871) Upgrade to Hibernate Search 5.3.0.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4871?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4871. ---------------------------- > Upgrade to Hibernate Search 5.3.0.Final > --------------------------------------- > > Key: WFLY-4871 > URL: https://issues.jboss.org/browse/WFLY-4871 > Project: WildFly > Issue Type: Component Upgrade > Components: JPA / Hibernate > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 10.0.0.Alpha5 > > > The main reason for this upgrade is that some changes are needed in modules structure between Hibernate Search 5.2 to 5.3. > Wildfly is currently using HS 5.2 but will require >=5.4 to be compatible with Hibernate ORM 5. > So applying this intermediate step towards HS 5.3 will make the Hibernate ORM 5 pull request easier. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5041) Test case for Reuse authenticated subject from incoming context when security domains match

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5041?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5041. ---------------------------- > Test case for Reuse authenticated subject from incoming context when security domains match > ------------------------------------------------------------------------------------------- > > Key: WFLY-5041 > URL: https://issues.jboss.org/browse/WFLY-5041 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Ondrej Lukas > Assignee: Ondrej Lukas > Fix For: 10.0.0.Beta1 > > > Add tests for Reuse authenticated subject from incoming context when security domains match. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4925) Admin in Monitor role can execute test-connection-in-pool op

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4925?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4925. ---------------------------- > Admin in Monitor role can execute test-connection-in-pool op > ------------------------------------------------------------ > > Key: WFLY-4925 > URL: https://issues.jboss.org/browse/WFLY-4925 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 10.0.0.Alpha5 > Reporter: Brian Stansberry > Assignee: Jesper Pedersen > Fix For: 10.0.0.Alpha6 > > > This should not work, as the Monitor role is not allowed to do anything that modifies any state: > {code} > [standalone@localhost:9990 data-source=ExampleDS] :test-connection-in-pool{roles=Monitor} > { > "outcome" => "success", > "result" => [true] > } > {code} > I believe the problem is PoolOperations L75: > {code} > final ServiceController<?> managementRepoService = context.getServiceRegistry(false).getService( > ConnectorServices.MANAGEMENT_REPOSITORY_SERVICE); > {code} > The parameter to context.getServiceRegistry(...) must be 'true' if the operation is going to use the returned service registry to perform any form of state modification. So I believe all the PoolOperation subclasses should provide a param to PoolOperation's constructor that can be used to set this value. I believe in all subclasses except DumpQueuedThreadInPool this param should be 'true'. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4564) Switch to version 4 of the management schema

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4564?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4564. ---------------------------- > Switch to version 4 of the management schema > -------------------------------------------- > > Key: WFLY-4564 > URL: https://issues.jboss.org/browse/WFLY-4564 > Project: WildFly > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 10.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4532) Clean up jboss-as-web_2_*.xsd schemas

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4532?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4532. ---------------------------- > Clean up jboss-as-web_2_*.xsd schemas > ------------------------------------- > > Key: WFLY-4532 > URL: https://issues.jboss.org/browse/WFLY-4532 > Project: WildFly > Issue Type: Sub-task > Components: Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 9.0.0.CR2, 10.0.0.Alpha1 > > > The last jboss-as-web schema included in a community release is jboss-as-web_2_0.xsd > JBoss EAP contains both jboss-as-web_2_1.xsd and jboss-as-web_2_2.xsd > I believe something was mistakenly added to the 2.1 schema in EAP, this was forward ported to WildFly - then the change to 2.1 was reverted in EAP and a 2.2 schema added. > Version 2.1 and 2.2 of the schemas need porting from EAP to WildFly and the parsers updated to support them accordingly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5055) JobControlTestCase fails intermittently

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5055?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5055. ---------------------------- > JobControlTestCase fails intermittently > ---------------------------------------- > > Key: WFLY-5055 > URL: https://issues.jboss.org/browse/WFLY-5055 > Project: WildFly > Issue Type: Bug > Components: Batch, Test Suite > Reporter: James Perkins > Assignee: James Perkins > Fix For: 10.0.0.Beta1 > > > See http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=63411&buildTyp... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4780) Provide a migration management operation for JBossWeb to Undertow

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4780?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4780. ---------------------------- > Provide a migration management operation for JBossWeb to Undertow > ------------------------------------------------------------------ > > Key: WFLY-4780 > URL: https://issues.jboss.org/browse/WFLY-4780 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Reporter: Jason Greene > Assignee: Stuart Douglas > Fix For: 10.0.0.Beta1 > > > Provide a management operation that performs a one-time conversion from the JBossWeb subsystem into the Undertow subsystem. This allows users using the CLI to perform a migration, as well as tools such as WindUp to also execute the change. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2017