Hide Forgot
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) --
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.