| Summary: | Enable and disable feature of console for RA connection definitions and admin objects are broken | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Osamu Nagano <onagano> |
| Component: | Web Console | Assignee: | Heiko Braun <hbraun> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jakub Cechacek <jcechace> |
| Severity: | unspecified | Docs Contact: | Russell Dickenson <rdickens> |
| Priority: | unspecified | ||
| Version: | 6.1.1 | CC: | brian.stansberry, jkudrnac, jstefl, onagano |
| Target Milestone: | ER3 | Flags: | onagano:
needinfo+
|
| Target Release: | EAP 6.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-12-15 16:49:10 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: | |
| Bug Depends On: | |||
| Bug Blocks: | 1003533 | ||
Deployable RAR file, TestCase.zip, is available as an attachment in case 00944733, though it's a little bit large. I cannot reproduce the issue. Noty on EAP 6.1.1 and not on 6.x (development) Osamu Nagano <onagano> made a comment on jira HAL-199 I attached a reproducer, which contains those. - standalone/configuration/standalone-full-ibmmq.xml - standalone/deployments/wmq.jmsra.rar - standalone/deployments/wmq.jmsra.rar.dodeploy Unzip and overlay the attachment and start standalone.sh with "-c standalone-full-ibmmq.xml" option. It will deploy a RAR file and try to en/disable it on [Profile > Resource Adapters > View > Connection Definitions] page. I attached a reproducer in JIRA. It must work on EAP 6.1.1. Please let me know if anything. Heiko Braun <ike.braun> updated the status of jira HAL-199 to Coding In Progress Heiko Braun <ike.braun> made a comment on jira HAL-199 Thanks, that does the job. I can now see the problem. Heiko Braun <ike.braun> updated the status of jira HAL-199 to Resolved 6.2.0-ER3 verified - PASSED I was able enable / disable "MQQueueCONNECTIONFACTORY" from reproducer. |
Description of problem: Enable and Disable buttons of [Profile > Resource Adapters > View > Connection Definitions] (and Admin Objects too) send requests with wrong addresses. It results in an unknown error message with the following contents. -- Unexpected HTTP response: 500 Request { "address" => [ ("subsystem" => "resource-adapters"), ("resource-adapter" => "wmq.jmsra.rar"), ("connection-definitions" => "java:jboss/MQQueueCONNECTIONFACTORY") ], "operation" => "write-attribute", "name" => "enabled", "value" => true } Response Internal Server Error { "outcome" => "failed", "failure-description" => "JBAS014807: Management resource '[ (\"subsystem\" => \"resource-adapters\"), (\"resource-adapter\" => \"wmq.jmsra.rar\"), (\"connection-definitions\" => \"java:jboss/MQQueueCONNECTIONFACTORY\") ]' not found", "rolled-back" => true, "response-headers" => {"process-state" => "reload-required"} } -- Path values of connection-definitions and admin-objects are just their names, not JNDI names, like this. -- /subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/connection-definitions=MQQueueCONNECTIONFACTORY:write-attribute(name=enabled,value=false) --