[jboss-jira] [JBoss JIRA] (WFLY-6690) Read-resource(include-runtime=true) fais on jms-bridge in domain mode

Jeff Mesnil (JIRA) issues at jboss.org
Wed Sep 6 04:04:01 EDT 2017


     [ https://issues.jboss.org/browse/WFLY-6690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Mesnil resolved WFLY-6690.
-------------------------------
    Fix Version/s: 11.0.0.Alpha1
       Resolution: Done


Underlying fix in wildfly-core has been integrated in WildFly 11.0.0.Alpha1

> Read-resource(include-runtime=true) fais on jms-bridge in domain mode
> ---------------------------------------------------------------------
>
>                 Key: WFLY-6690
>                 URL: https://issues.jboss.org/browse/WFLY-6690
>             Project: WildFly
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 10.0.0.Final
>            Reporter: Jeff Mesnil
>            Assignee: Jeff Mesnil
>             Fix For: 11.0.0.Alpha1
>
>
> /profile=full/subsystem=messaging-activemq/jms-bridge=bridge-mane-3:read-resource(include-runtime=true)
> {
>    "outcome" => "failed",
>    "rolled-back" => true
> }
> The server log
> [Host Controller] 15:30:49,150 ERROR
> [org.jboss.as.controller.management-operation]
> (management-handler-thread - 9) WFLYCTL0013: Operation
> ("read-attribute") failed - address: ([
> [Host Controller]     ("profile" => "full"),
> [Host Controller]     ("subsystem" => "messaging-activemq"),
> [Host Controller]     ("jms-bridge" => "bridge-mane-3")
> [Host Controller] ]) - failure description: "WFLYCTL0216: Management resource '[
> [Host Controller]     (\"profile\" => \"full\"),
> [Host Controller]     (\"subsystem\" => \"messaging-activemq\"),
> [Host Controller]     (\"jms-bridge\" => \"bridge-mane-3\")
> [Host Controller] ]' not found"
> Remove the include-runtime=true, it works.
> The issue lies with the "paused" and "started" runtime attributes whose read handler throws an exception if the bridge is not available in the runtime (that is the case in the profile).



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jboss-jira mailing list