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

Details

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

    Description

      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.

      Attachments

        Issue Links

          duplicates

          Task - Represents a small unit of work that is not end-user facing. WFLY-11695 Remove ParameterCorrector added for WFLY-11617

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Open
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-16528 Broken validation for pooled-connection-factory's transaction attribute - redundant WARN logs on startup

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. WFLY-11827 Broken validation for pooled-connection-factory's transaction attribute.

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. WFLY-11617 Validation not working for pooled-connection-factory's transaction attribute.

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: