2 Replies Latest reply on May 20, 2013 11:20 AM by John Franey

    eap 6.1 beta: error with management-operation

    John Franey Novice

      This problem is repeatable in jboss eap 6.1 using the eap 6.1 beta quickstart project jboss-as-ejb-in-ear.

       

      A bug?

       

      1) rename ear/target/jboss-as-ejb-in-ear-ear.ear to ear/target/jboss-as-ejb-in-ear-ear-7.1.2-SNAPSHOT.ear  (also can be done by altering the ear/pom.xml finalName property to: ${project.artifactId}-${project.version} )

      2) deploy with command line, specifiying runtime name of: jboss-as-ejb-in-ear-ear.ear

                [standalone@localhost:9999 /]  deploy --runtime-name=jboss-as-ejb-in-ear-ear.ear jboss-as-ejb-in-ear-ear-7.1.2-SNAPSHOT.ear

      3) visit the management gui, http://localhost:9990/console/App.html#deployments and navigate into the ear.

         a)  click on jboss-as-ejb-in-ear-ear-7.1.2-SNAPSHOT.ear, gui then displays the jar and the war.

          b)  click on 'jboss-as-ejb-in-ear-ejb.jar', gui then displays 'ejb'

          c)  click on 'ejb' and gui displays 'error message' in upper right, and in log output:

       

      22:48:34,985 ERROR [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 2) JBAS014612: Operation ("read-attribute") failed - address: ([

          ("deployment" => "jboss-as-ejb-in-ear-ear-7.1.2-SNAPSHOT.ear"),

          ("subdeployment" => "jboss-as-ejb-in-ear-ejb.jar"),

          ("subsystem" => "ejb3"),

          ("stateful-session-bean" => "GreeterEJB")

      ]): org.jboss.msc.service.ServiceNotFoundException: Service service jboss.deployment.subunit."jboss-as-ejb-in-ear-ear-7.1.2-SNAPSHOT.ear"."jboss-as-ejb-in-ear-ejb.jar".component.GreeterEJB.START not found

                at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:448) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]

        • 1. Re: eap 6.1 beta: error with management-operation
          Wolf-Dieter Fink Master

          Looks like that it is a bug.

           

          If it is deployed without a runtime name or runtime-name and name are equal it works.

          But it is not a problem of the management GUI, the same problem is visible in the CLI:

           

          [standalone@localhost:9999 /] deploy --runtime-name=jboss1.ear --name=jboss2.ear jboss-as-ejb-in-ear-ear-7.1.2-SNAPSHOT.ear

          [standalone@localhost:9999 /] /deployment=jboss1.ear/subdeployment=jboss-as-ejb-in-ear-ejb.jar/subsystem=ejb3/stateful-session-bean=GreeterEJB:read-resource(recursive=true,include-runtime=true)                 

          {

              "outcome" => "failed",

              "failure-description" => "JBAS014807: Management resource '[(\"deployment\" => \"jboss1.ear\")]' not found",

              "rolled-back" => true

          }

          [standalone@localhost:9999 /] /deployment=jboss2.ear/subdeployment=jboss-as-ejb-in-ear-ejb.jar/subsystem=ejb3/stateful-session-bean=GreeterEJB:read-resource(recursive=true,include-runtime=true)

          {

              "outcome" => "failed",

              "rolled-back" => true

          }

           

           

          Could you file a bug here

          1 of 1 people found this helpful