Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-11830

Writing an invalid operation to pooled-connection-factory's transaction attribute should fail the mgmt operation

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • 16.0.0.Final
    • JMS
    • None

      Current behaviour:

      [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=invalid)
10:26:37,062 WARN  [org.wildfly.extension.messaging-activemq] (management-handler-thread - 1) WFLYMSGAMQ0101: Invalid value invalid for transaction, legal values are [local, none, xa], default value is applied.
{"outcome" => "success"}

[standalone@localhost:9990 /]  /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:read-attribute(name=transaction)
{
    "outcome" => "success",
    "result" => "xa"
}

      To make it clear, the 

      10:26:37,062 WARN  [org.wildfly.extension.messaging-activemq] (management-handler-thread - 1) WFLYMSGAMQ0101: Invalid value invalid for transaction, legal values are [local, none, xa], default value is applied.

      message comes from server side, so as a client I have no idea that my mgmt operation did not happend (write didn't happen).

      The management operation should fail in this case, and "Invalid value invalid for transaction, legal values are [local, none, xa], default value is applied." message should be part of failure description instead.

              ehugonne1@redhat.com Emmanuel Hugonnet
              pkremens@redhat.com Petr Kremensky (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: