[jboss-jira] [JBoss JIRA] (WFLY-1521) Deployment runtime-name is not being handled properly
RH Bugzilla Integration (JIRA)
issues at jboss.org
Tue Dec 2 07:35:39 EST 2014
[ https://issues.jboss.org/browse/WFLY-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024386#comment-13024386 ]
RH Bugzilla Integration commented on WFLY-1521:
-----------------------------------------------
Petr Kremensky <pkremens at redhat.com> changed the Status of [bug 964446|https://bugzilla.redhat.com/show_bug.cgi?id=964446] from ON_QA to VERIFIED
> Deployment runtime-name is not being handled properly
> -----------------------------------------------------
>
> Key: WFLY-1521
> URL: https://issues.jboss.org/browse/WFLY-1521
> Project: WildFly
> Issue Type: Feature Request
> Affects Versions: 8.0.0.Alpha1
> Reporter: Bartosz Baranowski
> Assignee: Bartosz Baranowski
> Fix For: 8.0.0.Alpha4
>
>
> In case archive is deployed with runtime name that does not match archive name, it breaks CLI/GUI commands.
> [standalone at 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 at 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 at 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" => {
> "jboss-as-ejb-in-ear-web.war" => undefined,
> "jboss-as-ejb-in-ear-ejb.jar" => undefined
> }
> }
> }
> [standalone at localhost:9990 /]
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
More information about the jboss-jira
mailing list