Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-6113

The minLargeMessageSize option on the default acceptor has no effect

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Minor Minor
    • None
    • 7.9.1.CR2
    • broker-core, core-protocol
    • None
    • False
    • False
    • Hide

      Create a broker instance (ie, `artemis create ...`).

      Change the minLargeMessageSize on the broker acceptor to something other than 100K (ie, 1024000).

      Send in a message over 100K, but less than your configured minLargeMessageSize.

      See that it gets written to the large messages directory anyway.

      Show
      Create a broker instance (ie, `artemis create ...`). Change the minLargeMessageSize on the broker acceptor to something other than 100K (ie, 1024000). Send in a message over 100K, but less than your configured minLargeMessageSize. See that it gets written to the large messages directory anyway.

      When you create a broker using the `artemis create ...` command, it generates a default acceptor listening on port 61616. That acceptor has a minLargeMessageSize=102400 option set. However, that option does nothing when changed. It is only honored when set on the client broker URL for the ActiveMQConnectionFactory. If it's meant to be honored on the broker acceptor, it's not. If it's not meant for use on the acceptor, it should be removed from the default so it's not confusing to customers.

              rhn-support-jbertram Justin Bertram
              jreagan@redhat.com Joshua Reagan (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: