You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Erwin Dondorp (Jira)" <ji...@apache.org> on 2021/06/22 21:03:00 UTC

[jira] [Created] (ARTEMIS-3363) using parameter minLargeMessage on cluster connections results in stack traces

Erwin Dondorp created ARTEMIS-3363:
--------------------------------------

             Summary: using parameter minLargeMessage on cluster connections results in stack traces
                 Key: ARTEMIS-3363
                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3363
             Project: ActiveMQ Artemis
          Issue Type: Bug
          Components: Broker
    Affects Versions: 2.17.0
            Reporter: Erwin Dondorp


ON HOLD... issues being entered now...

In an attempt to set the large message boundary on cluster connections, I added the parameter {{minLargeMessageSize=200000}} to the

 

Note that the property "min-large-message-size" (under xxx) should have been used.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)