[jboss-jira] [JBoss JIRA] (WFLY-1520) Deployment runtime-name is not being handled properly
Bartosz Baranowski created WFLY-1520:
----------------------------------------
Summary: Deployment runtime-name is not being handled properly
Key: WFLY-1520
URL: https://issues.jboss.org/browse/WFLY-1520
Project: WildFly
Issue Type: Feature Request
Affects Versions: 8.0.0.Alpha1
Reporter: Bartosz Baranowski
Assignee: Bartosz Baranowski
Fix For: 8.0.0.Alpha2
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
....
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira