-
Feature Request
-
Resolution: Done
-
Major
-
8.0.0.Alpha1
-
None
-
None
In case archive is deployed with runtime name that does not match archive name, it breaks CLI/GUI commands.
[standalone@localhost:9999 /] deploy --runtime-name=nnn.ear /home/baranowb/redhat/git/jboss-as-quickstart/ejb-in-ear/ear/target/jboss-as-ejb-in-ear-ear-xxxx.ear
[standalone@localhost:9999 /] /deployment=jboss-as-ejb-in-ear-ear-xxxx.ear/subdeployment=jboss-as-ejb-in-ear-ejb.jar/subsystem=ejb3/stateful-session-bean=GreeterEJB:read-resource(include-runtime=true)
{
"outcome" => "failed",
"rolled-back" => true
}
14:05:23,235 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) JBAS014612: Operation ("read-attribute") failed - address: ([
("deployment" => "jboss-as-ejb-in-ear-ear-xxxx.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-xxxx.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.jar:1.0.4.GA]
at org.jboss.as.controller.OperationContextImpl$OperationContextServiceRegistry.getRequiredService(OperationContextImpl.java:1068) [jboss-as-controller-7.2.2-internal-SNAPSHOT.jar:7.2.2-internal-SNAPSHOT]
at org.jboss.as.ejb3.subsystem.deployment.AbstractRuntimeMetricsHandler.executeRuntimeStep(AbstractRuntimeMetricsHandler.java:69)
at
....
However some seem unaffected:
[standalone@localhost:9990 /] /deployment=jboss-as-ejb-in-ear-ear-xxxx.ear:read-resource
{
"outcome" => "success",
"result" => {
"content" => [{"hash" => bytes {
0x5c, 0x22, 0x14, 0x99, 0xff, 0x23, 0x45, 0xfc,
0x15, 0xaf, 0x1b, 0x97, 0x8c, 0x14, 0x75, 0x06,
0xa2, 0xeb, 0xfb, 0x58
}}],
"enabled" => true,
"name" => "jboss-as-ejb-in-ear-ear-xxxx.ear",
"persistent" => true,
"runtime-name" => "nnn.ear",
"subsystem" => undefined,
"subdeployment" =>
}
}
[standalone@localhost:9990 /]
- relates to
-
WFLY-2061 CLI fails to show app status when runtime-name is different from the deployment name
- Closed