WFLY-2422 Remoting profiles #6835

tadamski · 2014-10-17T15:57:33Z

Adds remoting profiles to ejb3 subsystem. Profiles consist of remote ejb receivers and local ejb receiver. Profile is represented by RemotingProfileService which depends on all connection services that ejb receivers need to connect to. If client wants to use remoting profile it can configure it in jboss-ejb-client.xml.
To provide backward compatibility client can still define remoting ejb receivers directly in jboss-ejb-client.xml. In this case during application deployment internal profile service, which consist of those receivers, is created. Remoting-profiles are responsive to cli operations: each time profile resource (or any of it's children resources) changes profile service is being restarted with new configuration. In case of invalid configuration update (f.e. non-existent connection dependency) operation is being rolled back and profile is restored to it's last correct configuration.

wildfly-ci · 2014-10-19T17:43:53Z

Windows Build 380 is now running using a merge of f3d5922

wildfly-ci · 2014-10-19T18:14:20Z

Linux with security manager Build 263 is now running using a merge of f3d5922

wildfly-ci · 2014-10-19T18:21:29Z

Linux with security manager Build 263 outcome was FAILURE using a merge of f3d5922
Summary: Tests failed: 16 (16 new), passed: 778, ignored: 244 Build time: 0:07:09

Build problems:

Failed tests detected

Failed tests

org.jboss.as.ejb3.subsystem.Ejb3SubsystemUnitTestCase.testTransformerAS720: java.lang.IllegalStateException: duplicate transformer undefine-attribute
    at org.jboss.as.controller.registry.OperationTransformerRegistry.registerTransformer(OperationTransformerRegistry.java:251)
    at org.jboss.as.controller.registry.GlobalTransformerRegistry.registerTransformer(GlobalTransformerRegistry.java:212)

org.jboss.as.ejb3.subsystem.Ejb3SubsystemUnitTestCase.testSubsystem: org.junit.ComparisonFailure: expected:<...jboss:domain:ejb3:3.[0]">
    <session-bean...> but was:<...jboss:domain:ejb3:3.[1]">
    <session-bean...>

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneEC2FullHA: java.lang.AssertionError: 1:9153 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/target/StandardConfigsXMLValidationUnitTestCase3344854635831452017xml' cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'subsystem'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandalone: java.lang.AssertionError: 1:8826 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/target/StandardConfigsXMLValidationUnitTestCase8586899211629886762xml' cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'subsystem'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneHA: java.lang.AssertionError: 1:8940 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/target/StandardConfigsXMLValidationUnitTestCase8969059636142056358xml' cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'subsystem'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneJTS: java.lang.AssertionError: 1:8807 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/target/StandardConfigsXMLValidationUnitTestCase3389319676636582524xml' cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'subsystem'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneRTS: java.lang.AssertionError: 1:8962 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/target/StandardConfigsXMLValidationUnitTestCase9044072835376035384xml' cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'subsystem'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneXTS: java.lang.AssertionError: 1:8587 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/target/StandardConfigsXMLValidationUnitTestCase61501018042070557xml' cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'subsystem'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneGossipHA: java.lang.AssertionError: 1:8940 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/target/StandardConfigsXMLValidationUnitTestCase5302513769391769900xml' cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'subsystem'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandalonePicketLink: java.lang.AssertionError: 1:8603 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/target/StandardConfigsXMLValidationUnitTestCase4292086122218118292xml' cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'subsystem'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneEC2HA: java.lang.AssertionError: 1:8940 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/target/StandardConfigsXMLValidationUnitTestCase3571980562258628689xml' cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'subsystem'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)


##### there are 6 more failed tests, see build details

wildfly-ci · 2014-10-19T18:21:30Z

Linux Build 5264 is now running using a merge of f3d5922

wildfly-ci · 2014-10-19T18:40:05Z

Windows Build 380 outcome was FAILURE using a merge of f3d5922
Summary: Tests failed: 27 (27 new), passed: 2983, ignored: 238 Build time: 0:56:13

Build problems:

Failed tests detected

Failed tests

org.jboss.as.ejb3.subsystem.Ejb3SubsystemUnitTestCase.testTransformerAS720: java.lang.IllegalStateException: duplicate transformer undefine-attribute
    at org.jboss.as.controller.registry.OperationTransformerRegistry.registerTransformer(OperationTransformerRegistry.java:251)
    at org.jboss.as.controller.registry.GlobalTransformerRegistry.registerTransformer(GlobalTransformerRegistry.java:212)

org.jboss.as.ejb3.subsystem.Ejb3SubsystemUnitTestCase.testTransformerEAP610: java.lang.IllegalStateException: duplicate transformer undefine-attribute
    at org.jboss.as.controller.registry.OperationTransformerRegistry.registerTransformer(OperationTransformerRegistry.java:251)
    at org.jboss.as.controller.registry.GlobalTransformerRegistry.registerTransformer(GlobalTransformerRegistry.java:212)

org.jboss.as.ejb3.subsystem.Ejb3SubsystemUnitTestCase.testTransformerEAP611: java.lang.IllegalStateException: duplicate transformer undefine-attribute
    at org.jboss.as.controller.registry.OperationTransformerRegistry.registerTransformer(OperationTransformerRegistry.java:251)
    at org.jboss.as.controller.registry.GlobalTransformerRegistry.registerTransformer(GlobalTransformerRegistry.java:212)

org.jboss.as.ejb3.subsystem.Ejb3SubsystemUnitTestCase.testSubsystem: org.junit.ComparisonFailure: expected:<...jboss:domain:ejb3:3.[0]">
    <session-bean...> but was:<...jboss:domain:ejb3:3.[1]">
    <session-bean...>

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneEC2FullHA: java.lang.AssertionError: 1:9085 systemId='file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/target/StandardConfigsXMLValidationUnitTestCase824463915610260924xml' cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'subsystem'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandalone: java.lang.AssertionError: 1:8758 systemId='file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/target/StandardConfigsXMLValidationUnitTestCase3907406789470277187xml' cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'subsystem'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneHA: java.lang.AssertionError: 1:8872 systemId='file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/target/StandardConfigsXMLValidationUnitTestCase8828518732271796935xml' cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'subsystem'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneJTS: java.lang.AssertionError: 1:8807 systemId='file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/target/StandardConfigsXMLValidationUnitTestCase8542222144206813880xml' cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'subsystem'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneRTS: java.lang.AssertionError: 1:8962 systemId='file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/target/StandardConfigsXMLValidationUnitTestCase7102278184617260122xml' cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'subsystem'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneXTS: java.lang.AssertionError: 1:8587 systemId='file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/target/StandardConfigsXMLValidationUnitTestCase9191492814170781868xml' cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'subsystem'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneGossipHA: java.lang.AssertionError: 1:8872 systemId='file:/C:/BuildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/target/StandardConfigsXMLValidationUnitTestCase4375952218186961893xml' cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'subsystem'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)


##### there are 17 more failed tests, see build details

wildfly-ci · 2014-10-19T19:17:27Z

Linux Build 5264 outcome was FAILURE using a merge of f3d5922
Summary: Tests failed: 27 (27 new), passed: 2983, ignored: 238 Build time: 0:55:57

Build problems:

Failed tests detected

Failed tests

org.jboss.as.ejb3.subsystem.Ejb3SubsystemUnitTestCase.testTransformerAS720: java.lang.IllegalStateException: duplicate transformer undefine-attribute
    at org.jboss.as.controller.registry.OperationTransformerRegistry.registerTransformer(OperationTransformerRegistry.java:251)
    at org.jboss.as.controller.registry.GlobalTransformerRegistry.registerTransformer(GlobalTransformerRegistry.java:212)

org.jboss.as.ejb3.subsystem.Ejb3SubsystemUnitTestCase.testTransformerEAP610: java.lang.IllegalStateException: duplicate transformer undefine-attribute
    at org.jboss.as.controller.registry.OperationTransformerRegistry.registerTransformer(OperationTransformerRegistry.java:251)
    at org.jboss.as.controller.registry.GlobalTransformerRegistry.registerTransformer(GlobalTransformerRegistry.java:212)

org.jboss.as.ejb3.subsystem.Ejb3SubsystemUnitTestCase.testTransformerEAP611: java.lang.IllegalStateException: duplicate transformer undefine-attribute
    at org.jboss.as.controller.registry.OperationTransformerRegistry.registerTransformer(OperationTransformerRegistry.java:251)
    at org.jboss.as.controller.registry.GlobalTransformerRegistry.registerTransformer(GlobalTransformerRegistry.java:212)

org.jboss.as.ejb3.subsystem.Ejb3SubsystemUnitTestCase.testSubsystem: org.junit.ComparisonFailure: expected:<...jboss:domain:ejb3:3.[0]">
    <session-bean...> but was:<...jboss:domain:ejb3:3.[1]">
    <session-bean...>

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneEC2FullHA: java.lang.AssertionError: 1:9085 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/target/StandardConfigsXMLValidationUnitTestCase6891358104544921145xml' cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'subsystem'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandalone: java.lang.AssertionError: 1:8758 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/target/StandardConfigsXMLValidationUnitTestCase1669660583897137626xml' cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'subsystem'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneHA: java.lang.AssertionError: 1:8872 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/target/StandardConfigsXMLValidationUnitTestCase1365269127591033026xml' cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'subsystem'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneJTS: java.lang.AssertionError: 1:8807 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/target/StandardConfigsXMLValidationUnitTestCase6439329031646130385xml' cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'subsystem'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneRTS: java.lang.AssertionError: 1:8962 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/target/StandardConfigsXMLValidationUnitTestCase6969973019812600331xml' cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'subsystem'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneXTS: java.lang.AssertionError: 1:8587 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/target/StandardConfigsXMLValidationUnitTestCase4538505292567358755xml' cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'subsystem'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)

org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testStandaloneGossipHA: java.lang.AssertionError: 1:8872 systemId='file:/opt/buildAgent/work/340a2b56aab3b1db/testsuite/integration/smoke/target/StandardConfigsXMLValidationUnitTestCase2496384869286058021xml' cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'subsystem'. a possible cause may be that a subsystem is not using the most up to date schema.
    at org.junit.Assert.fail(Assert.java:88)
    at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$ErrorHandlerImpl.error(AbstractValidationUnitTest.java:279)


##### there are 17 more failed tests, see build details

wildfly-ci · 2014-10-20T21:25:16Z

Windows Build 391 is now running using a merge of a58951b

wildfly-ci · 2014-10-20T21:25:17Z

Linux Build 5284 is now running using a merge of a58951b

wildfly-ci · 2014-10-20T21:25:17Z

Linux with security manager Build 276 is now running using a merge of a58951b

wildfly-ci · 2014-10-20T21:31:36Z

Linux with security manager Build 276 outcome was SUCCESS using a merge of a58951b
Summary: Tests passed: 794, ignored: 244 Build time: 0:06:20

wildfly-ci · 2014-10-20T22:18:47Z

Windows Build 391 outcome was FAILURE using a merge of a58951b
Summary: Tests failed: 9, passed: 3001, ignored: 238 Build time: 0:53:32

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.integration.ejb.client.descriptor.EJBClientDescriptorTestCase.testClientInvocationTimeout: org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: ejb-client-descriptor-test-with-jboss-ejb-client_1_2_xml.jar
    at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
    at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)

org.jboss.as.test.integration.ejb.client.descriptor.EJBClientDescriptorTestCase.testLocalAndRemoteReceiversClientConfig: org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: ejb-client-descriptor-with-local-and-remote-receivers-test.jar
    at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
    at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)

org.jboss.as.test.integration.ejb.client.descriptor.EJBClientDescriptorTestCase.testEJBClientContextConfiguration: org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: ejb-client-descriptor-test.jar
    at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
    at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)

org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase: org.jboss.as.test.multinode.ejb.timer.database.DatabaseTimerServiceMultiNodeExecutionDisabledTestCase: org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:208)
    at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:112)

org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase: org.jboss.as.test.multinode.ejb.timer.database.DatabaseTimerServiceMultiNodeTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
    at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:85)
    at org.junit.runners.Suite.runChild(Suite.java:127)

org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase: org.jboss.as.test.multinode.remotecall.RemoteLocalCallProfileTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
    at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:85)
    at org.junit.runners.Suite.runChild(Suite.java:127)

org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase: org.jboss.as.test.multinode.remotecall.RemoteLocalCallTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
    at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:85)
    at org.junit.runners.Suite.runChild(Suite.java:127)

org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase: org.jboss.as.test.multinode.remotecall.scoped.context.DynamicJNDIContextEJBInvocationTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
    at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:85)
    at org.junit.runners.Suite.runChild(Suite.java:127)

org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
    at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:85)
    at org.junit.runners.Suite.runChild(Suite.java:127)

wildfly-ci · 2014-10-20T22:21:27Z

Linux Build 5284 outcome was FAILURE using a merge of a58951b
Summary: Tests failed: 9, passed: 3001, ignored: 238 Build time: 0:56:12

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.integration.ejb.client.descriptor.EJBClientDescriptorTestCase.testClientInvocationTimeout: org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: ejb-client-descriptor-test-with-jboss-ejb-client_1_2_xml.jar
    at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
    at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)

org.jboss.as.test.integration.ejb.client.descriptor.EJBClientDescriptorTestCase.testLocalAndRemoteReceiversClientConfig: org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: ejb-client-descriptor-with-local-and-remote-receivers-test.jar
    at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
    at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)

org.jboss.as.test.integration.ejb.client.descriptor.EJBClientDescriptorTestCase.testEJBClientContextConfiguration: org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: ejb-client-descriptor-test.jar
    at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
    at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)

org.jboss.as.test.multinode.remotecall.scoped.context.DynamicJNDIContextEJBInvocationTestCase: org.jboss.as.test.multinode.ejb.timer.database.DatabaseTimerServiceMultiNodeExecutionDisabledTestCase: org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container
    at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:208)
    at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:112)

org.jboss.as.test.multinode.remotecall.scoped.context.DynamicJNDIContextEJBInvocationTestCase: org.jboss.as.test.multinode.ejb.timer.database.DatabaseTimerServiceMultiNodeTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
    at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:85)
    at org.junit.runners.Suite.runChild(Suite.java:127)

org.jboss.as.test.multinode.remotecall.scoped.context.DynamicJNDIContextEJBInvocationTestCase: org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
    at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:85)
    at org.junit.runners.Suite.runChild(Suite.java:127)

org.jboss.as.test.multinode.remotecall.scoped.context.DynamicJNDIContextEJBInvocationTestCase: org.jboss.as.test.multinode.remotecall.RemoteLocalCallTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
    at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:85)
    at org.junit.runners.Suite.runChild(Suite.java:127)

org.jboss.as.test.multinode.remotecall.scoped.context.DynamicJNDIContextEJBInvocationTestCase: org.jboss.as.test.multinode.remotecall.RemoteLocalCallProfileTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
    at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:85)
    at org.junit.runners.Suite.runChild(Suite.java:127)

org.jboss.as.test.multinode.remotecall.scoped.context.DynamicJNDIContextEJBInvocationTestCase: java.lang.RuntimeException: Arquillian has previously been attempted initialized, but failed. See cause for previous exception
    at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:85)
    at org.junit.runners.Suite.runChild(Suite.java:127)

wildfly-ci · 2014-10-21T13:20:23Z

Linux Build 5289 is now running using a merge of 0eb48b5

wildfly-ci · 2014-10-21T13:20:23Z

Windows Build 396 is now running using a merge of 0eb48b5

wildfly-ci · 2014-10-21T13:20:24Z

Linux with security manager Build 281 is now running using a merge of 0eb48b5

wildfly-ci · 2014-10-21T13:26:44Z

Linux with security manager Build 281 outcome was SUCCESS using a merge of 0eb48b5
Summary: Tests passed: 794, ignored: 244 Build time: 0:06:22

wildfly-ci · 2014-10-21T14:13:41Z

Windows Build 396 outcome was SUCCESS using a merge of 0eb48b5
Summary: Tests passed: 3032, ignored: 238 Build time: 0:53:19

wildfly-ci · 2014-10-21T14:16:28Z

Linux Build 5289 outcome was SUCCESS using a merge of 0eb48b5
Summary: Tests passed: 3031, ignored: 238, muted: 1 Build time: 0:56:05

bstansberry · 2014-10-22T20:25:12Z

There shouldn't be a need for a new xsd version for this. I don't see the current 3.0 version used in any 8.x release, so the changes here are just further work on the non-yet-final 3.0.

stuartwdouglas · 2014-10-24T04:36:01Z

.../main/java/org/jboss/as/ejb3/deployment/processors/EJBClientDescriptorMetaDataProcessor.java

+        serviceBuilder.addDependency(TCCLEJBClientContextSelectorService.TCCL_BASED_EJB_CLIENT_CONTEXT_SELECTOR_SERVICE_NAME);
+        // install the service
+        serviceBuilder.install();
+        logger.debug("Deployment unit " + deploymentUnit + " will use " + ejbClientContextServiceName


This should use debugf rather that doing string concatenation, although this is not really performance sensitve code so I guess it does not matter that much

stuartwdouglas · 2014-10-24T04:43:58Z

This looks ok from an EE point of view, but as Brian said all the references to 3.1 schema (and related model version bumps) need to be removed, and the changes put in the 3.0 schema.

wildfly-ci · 2014-12-11T22:55:55Z

Linux Build 5652 is now running using a merge of 03601c4

wildfly-ci · 2014-12-11T22:55:55Z

Linux with security manager Build 637 is now running using a merge of 03601c4

wildfly-ci · 2014-12-11T22:55:56Z

Windows Build 763 is now running using a merge of 03601c4

wildfly-ci · 2014-12-11T23:02:23Z

Linux with security manager Build 637 outcome was SUCCESS using a merge of 03601c4
Summary: Tests passed: 797, ignored: 370 Build time: 0:06:28

wildfly-ci · 2014-12-11T23:47:13Z

Windows Build 763 outcome was FAILURE using a merge of 03601c4
Summary: Tests failed: 1 (1 new), passed: 3017, ignored: 365 Build time: 0:51:18

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.multinode.remotecall.RemoteLocalCallProfileTestCase: org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: remotelocalcall-test-client.jar
    at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:83)
    at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64)

wildfly-ci · 2014-12-11T23:48:46Z

Linux Build 5652 outcome was FAILURE using a merge of 03601c4
Summary: Tests failed: 1 (1 new), passed: 3017, ignored: 365 Build time: 0:52:52

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.multinode.remotecall.RemoteLocalCallProfileTestCase: org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: remotelocalcall-test-client.jar
    at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:83)
    at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64)

wildfly-ci · 2014-12-11T23:55:25Z

Windows Build 764 is now running using a merge of 8dac2a8

wildfly-ci · 2014-12-11T23:55:25Z

Linux Build 5653 is now running using a merge of 8dac2a8

wildfly-ci · 2014-12-11T23:55:26Z

Linux with security manager Build 638 is now running using a merge of 8dac2a8

wildfly-ci · 2014-12-12T00:01:48Z

Linux with security manager Build 638 outcome was SUCCESS using a merge of 98b5eb0
Summary: Tests passed: 797, ignored: 370 Build time: 0:06:24

wildfly-ci · 2014-12-12T00:45:09Z

Windows Build 764 outcome was SUCCESS using a merge of 98b5eb0
Summary: Tests passed: 3025, ignored: 365 Build time: 0:49:45

wildfly-ci · 2014-12-12T00:47:48Z

Linux Build 5653 outcome was SUCCESS using a merge of 98b5eb0
Summary: Tests passed: 3024, ignored: 365, muted: 1 Build time: 0:52:24

wildfly-ci · 2014-12-12T00:50:24Z

Windows Build 765 is now running using a merge of 98b5eb0

wildfly-ci · 2014-12-12T00:50:24Z

Linux with security manager Build 639 is now running using a merge of 98b5eb0

wildfly-ci · 2014-12-12T00:50:25Z

Linux Build 5654 is now running using a merge of 98b5eb0

wildfly-ci · 2014-12-12T00:56:44Z

Linux with security manager Build 639 outcome was SUCCESS using a merge of 98b5eb0
Summary: Tests passed: 797, ignored: 370 Build time: 0:06:21

wildfly-ci · 2014-12-12T01:41:11Z

Windows Build 765 outcome was SUCCESS using a merge of 98b5eb0
Summary: Tests passed: 3025, ignored: 365 Build time: 0:50:47

wildfly-ci · 2014-12-12T01:43:59Z

Linux Build 5654 outcome was FAILURE using a merge of 98b5eb0
Summary: Tests failed: 1 (1 new), passed: 3023, ignored: 365, muted: 1 Build time: 0:53:36

Build problems:

Failed tests detected

Failed tests

org.jboss.as.test.integration.ejb.stateful.passivation.PassivationTestCase.testPassivationMaxSize: java.lang.reflect.UndeclaredThrowableException: null
    at com.sun.proxy.$Proxy61.runTestMethod(Unknown Source)
    at org.jboss.arquillian.protocol.jmx.JMXMethodExecutor.invoke(JMXMethodExecutor.java:71)

WFLY-2422 Remoting profiles

tadamski force-pushed the WFLY-2422 branch from 6e150bd to f3d5922 Compare October 17, 2014 16:29

tadamski force-pushed the WFLY-2422 branch from f3d5922 to a58951b Compare October 20, 2014 21:21

tadamski force-pushed the WFLY-2422 branch from a58951b to 0eb48b5 Compare October 21, 2014 13:15

bstansberry added mgmt-review labels Oct 22, 2014

stuartwdouglas reviewed Oct 24, 2014
View reviewed changes

stuartwdouglas added fixme and removed ee-review labels Oct 24, 2014

bstansberry added fixme and removed mgmt-review labels Dec 4, 2014

tadamski force-pushed the WFLY-2422 branch from 44118b7 to 03601c4 Compare December 11, 2014 22:54

tadamski force-pushed the WFLY-2422 branch from 03601c4 to 8dac2a8 Compare December 11, 2014 23:52

tadamski added 2 commits December 12, 2014 00:57

WFLY-2422 Remoting profiles

326608b

WFLY-2422 Ejb client descriptor parsers refactor

98b5eb0

tadamski force-pushed the WFLY-2422 branch from 8dac2a8 to 98b5eb0 Compare December 11, 2014 23:57

bstansberry added ready-for-merge Only for use by those with merge permissions! and removed fixme labels Dec 12, 2014

bstansberry added a commit that referenced this pull request Dec 15, 2014

Merge pull request #6835 from tadamski/WFLY-2422

c95a8b1

WFLY-2422 Remoting profiles

bstansberry merged commit c95a8b1 into wildfly:master Dec 15, 2014

tadamski deleted the WFLY-2422 branch May 21, 2015 17:00

WFLY-2422 Remoting profiles #6835

WFLY-2422 Remoting profiles #6835

Conversation

tadamski commented Oct 17, 2014

wildfly-ci commented Oct 19, 2014

wildfly-ci commented Oct 19, 2014

wildfly-ci commented Oct 19, 2014

Build problems:

Failed tests

wildfly-ci commented Oct 19, 2014

wildfly-ci commented Oct 19, 2014

Build problems:

Failed tests

wildfly-ci commented Oct 19, 2014

Build problems:

Failed tests

wildfly-ci commented Oct 20, 2014

wildfly-ci commented Oct 20, 2014

wildfly-ci commented Oct 20, 2014

wildfly-ci commented Oct 20, 2014

wildfly-ci commented Oct 20, 2014

Build problems:

Failed tests

wildfly-ci commented Oct 20, 2014

Build problems:

Failed tests

wildfly-ci commented Oct 21, 2014

wildfly-ci commented Oct 21, 2014

wildfly-ci commented Oct 21, 2014

wildfly-ci commented Oct 21, 2014

wildfly-ci commented Oct 21, 2014

wildfly-ci commented Oct 21, 2014

bstansberry commented Oct 22, 2014

stuartwdouglas Oct 24, 2014

Choose a reason for hiding this comment

stuartwdouglas commented Oct 24, 2014

wildfly-ci commented Dec 11, 2014

wildfly-ci commented Dec 11, 2014

wildfly-ci commented Dec 11, 2014

wildfly-ci commented Dec 11, 2014

wildfly-ci commented Dec 11, 2014

Build problems:

Failed tests

wildfly-ci commented Dec 11, 2014

Build problems:

Failed tests

wildfly-ci commented Dec 11, 2014

wildfly-ci commented Dec 11, 2014

wildfly-ci commented Dec 11, 2014

wildfly-ci commented Dec 12, 2014

wildfly-ci commented Dec 12, 2014

wildfly-ci commented Dec 12, 2014

wildfly-ci commented Dec 12, 2014

wildfly-ci commented Dec 12, 2014

wildfly-ci commented Dec 12, 2014

wildfly-ci commented Dec 12, 2014

wildfly-ci commented Dec 12, 2014

wildfly-ci commented Dec 12, 2014

Build problems:

Failed tests