Bug 1008823 - Enable and disable feature of console for RA connection definitions and admin objects are broken
Summary: Enable and disable feature of console for RA connection definitions and admin...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console
Version: 6.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER3
: EAP 6.2.0
Assignee: Heiko Braun
QA Contact: Jakub Cechacek
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks: 1003533
TreeView+ depends on / blocked
 
Reported: 2013-09-17 06:58 UTC by Osamu Nagano
Modified: 2018-12-03 19:57 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-15 16:49:10 UTC
Type: Bug
onagano: needinfo+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker HAL-199 0 Major Resolved Enable and disable feature of console for RA connection definitions and admin objects are broken 2013-11-12 10:48:07 UTC

Description Osamu Nagano 2013-09-17 06:58:48 UTC
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)
--

Comment 1 Osamu Nagano 2013-09-17 07:02:21 UTC
Deployable RAR file, TestCase.zip, is available as an attachment in case 00944733, though it's a little bit large.

Comment 2 Heiko Braun 2013-09-17 10:26:25 UTC
I cannot reproduce the issue. Noty on EAP 6.1.1 and not on 6.x (development)

Comment 3 JBoss JIRA Server 2013-09-18 01:36:54 UTC
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.

Comment 4 Osamu Nagano 2013-09-18 01:42:23 UTC
I attached a reproducer in JIRA.  It must work on EAP 6.1.1.  Please let me know if anything.

Comment 5 JBoss JIRA Server 2013-09-18 07:38:13 UTC
Heiko Braun <ike.braun> updated the status of jira HAL-199 to Coding In Progress

Comment 6 JBoss JIRA Server 2013-09-18 07:38:29 UTC
Heiko Braun <ike.braun> made a comment on jira HAL-199

Thanks, that does the job. I can now see the problem.

Comment 7 JBoss JIRA Server 2013-09-18 08:00:56 UTC
Heiko Braun <ike.braun> updated the status of jira HAL-199 to Resolved

Comment 8 Jan Stefl 2013-09-27 09:56:35 UTC
6.2.0-ER3 verified - PASSED
I was able enable / disable "MQQueueCONNECTIONFACTORY" from reproducer.


Note You need to log in before you can comment on or make changes to this bug.