Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-19253

The RemoteLocalCallProfileTestCase setup task invokes commands that fail a reload

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • None
    • None
    • EJB, Test Suite
    • None
    • ---
    • ---

    Description

      The RemoteLocalCallProfileTestCase.RemoteLocalCallProfileTestCaseServerSetup invokes two operations which do not fail, but on a reload the server is in an invalid state.

      The two commands are:

      /subsystem=ejb3/remoting-profile=test-profile:add
      /subsystem=ejb3/remoting-profile=test-profile/remoting-ejb-receiver=test-reciever:add(outbound-connection-ref=remote-ejb-connection)
      

      If you execute those in CLI then execute a reload the server will boot with errors:

      14:09:43,371 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) WFLYDS0013: Started FileSystemDeploymentService for directory /home/jperkins/projects/wildfly/wildfly/build/target/wildfly-32.0.0.Final-SNAPSHOT/standalone/deployments
      14:09:43,384 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
          ("subsystem" => "ejb3"),
          ("remoting-profile" => "test-profile")
      ]) - failure description: {
          "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.remoting.outbound-connection.remote-ejb-connection"],
          "WFLYCTL0180: Services with missing/unavailable dependencies" => ["service org.wildfly.ejb3.remoting-profile.test-profile is missing [org.wildfly.remoting.outbound-connection.remote-ejb-connection]"]
      }
      14:09:43,388 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
      WFLYCTL0184:    New missing/unsatisfied dependencies:
            service org.wildfly.remoting.outbound-connection.remote-ejb-connection (missing) dependents: [service org.wildfly.ejb3.remoting-profile.test-profile] 
      
      14:09:43,397 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
      14:09:43,399 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
      14:09:43,399 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
      14:09:43,399 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 32.0.0.Final-SNAPSHOT (WildFly Core 24.0.0.Beta3) started (with errors) in 128ms - Started 280 of 523 services (1 services failed or missing dependencies, 317 services are lazy, passive or on-demand) - Server configuration file in use: standalone.xml
      

      This became visible to me while testing WFARQ-168. For some reason the test passes even though the server booted with a failed service.

      Note that if you batch the commands, the failure occurs in CLI as well:

      batch
      /subsystem=ejb3/remoting-profile=test-profile:add
      /subsystem=ejb3/remoting-profile=test-profile/remoting-ejb-receiver=test-reciever:add(outbound-connection-ref=remote-ejb-connection)
      run-batch
      

      Attachments

        Activity

          People

            jperkins-rhn James Perkins
            jperkins-rhn James Perkins
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: