Bug 964446
| Summary: | read-attribute operation for a deployment fails fails (cli, gui) when name != runtime-name | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | John <jjfraney> |
| Component: | Domain Management, EJB | Assignee: | baranowb <bbaranow> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Kremensky <pkremens> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.1.0 | CC: | bbaranow, brian.stansberry, cdewolf, kkhan, myarboro, pkremens, wfink |
| Target Milestone: | Pending | ||
| Target Release: | EAP 6.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-08-19 12:38:22 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Using the gui to browse into an ejb in an ear file deployed as above (runtime name != deployment name), results in an error that looks like this:
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")
A correction: I mentioned above that my arquillian integration test does not run when the ear is deployed in this manner. However, the error message output is the same as when using the gui, not the cli (as I stated above).
I claim thee.
Additional info:
[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 org.jboss.as.controller.AbstractRuntimeOnlyHandler$1.execute(AbstractRuntimeOnlyHandler.java:90) [jboss-as-controller-7.2.2-internal-SNAPSHOT.jar:7.2.2-internal-SNAPSHOT]
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440) [jboss-as-controller-7.2.2-internal-SNAPSHOT.jar:7.2.2-internal-SNAPSHOT]
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322) [jboss-as-controller-7.2.2-internal-SNAPSHOT.jar:7.2.2-internal-SNAPSHOT]
at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) [jboss-as-controller-7.2.2-internal-SNAPSHOT.jar:7.2.2-internal-SNAPSHOT]
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) [jboss-as-controller-7.2.2-internal-SNAPSHOT.jar:7.2.2-internal-SNAPSHOT]
at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:194) [jboss-as-controller-7.2.2-internal-SNAPSHOT.jar:7.2.2-internal-SNAPSHOT]
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:115) [jboss-as-controller-7.2.2-internal-SNAPSHOT.jar:7.2.2-internal-SNAPSHOT]
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) [jboss-as-controller-7.2.2-internal-SNAPSHOT.jar:7.2.2-internal-SNAPSHOT]
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) [jboss-as-controller-7.2.2-internal-SNAPSHOT.jar:7.2.2-internal-SNAPSHOT]
at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) [jboss-as-protocol-7.2.2-internal-SNAPSHOT.jar:7.2.2-internal-SNAPSHOT]
at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) [jboss-as-protocol-7.2.2-internal-SNAPSHOT.jar:7.2.2-internal-SNAPSHOT]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final]
Add upstream JIRA Bartosz Baranowski <bbaranow> updated the status of jira WFLY-1521 to Coding In Progress PR sent against 6.x, should be rePRed once 6.x is up for dev. *** Bug 1006916 has been marked as a duplicate of this bug. *** Carlo, is there any additional work that needs to be done on this issue? Verified on EAP 6.4.0.DR11 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |
Description of problem: 1) using cli, deploy an ear, overriding default runtime-name: deploy --runtime-name=jboss-as-ejb-in-ear-ear.ear jboss-as-ejb-in-ear-ear-7.1.2-SNAPSHOT.ear 2) apply read-operation via gui or cli Version-Release number of selected component (if applicable): version.txt: JBoss Enterprise Application Platform - Version 6.1.0.Beta1 How reproducible: Always Steps to Reproduce: 1) build quickstart eap-6.1 sample: jboss-as-ejb-in-ear, 2) rename target/jboss-as-ejb-in-ear-ear.ear to target/jboss-as-ejb-in-ear-ear-7.1.2-SNAPSHOT.ear 3) run these cli commands. [standalone@localhost:9999 /] deploy --runtime-name=jboss-as-ejb-in-ear-ear.ear jboss-as-ejb-in-ear-ear-7.1.2-SNAPSHOT.ear [standalone@localhost:9999 /] /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:read-resource { "outcome" => "failed", "result" => {"security-domain" => undefined}, "rolled-back" => true } [standalone@localhost:9999 /] undeploy jboss-as-ejb-in-ear-ear-7.1.2-SNAPSHOT.ear [standalone@localhost:9999 /] deploy jboss-as-ejb-in-ear-ear-7.1.2-SNAPSHOT.ear [standalone@localhost:9999 /] /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:read-resource { "outcome" => "success", "result" => {"security-domain" => undefined} } Actual results: failure occurs when runtime-name does not match deployment name. Expected results: Expected success regardless of runtime-name's value. Additional info: The above reproduces the same error I encountered using arquillian. I hope that if this bug is resolved, my arquillian test would resolve as well. I want an application to be pre-deployed BEFORE running an arquillian test. I want that application to have a runtime-name that is independent of the version number in the file name. After predeploy, I run an arquillian integration test of a different application that depends on this predeployed application. The above error is printed when the arquillian test attempts to resolve an ejb hosted in the pre-deployed application. The above is not reproduced when I deploy and run an application that depends on an application pre-deployed in the manner above (runtime-name != deployment name). Arquillian is not involved in this case.