activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher L. Shannon (JIRA)" <>
Subject [jira] [Commented] (AMQ-5774) Add maximum message size per transport
Date Wed, 13 May 2015 20:06:03 GMT


Christopher L. Shannon commented on AMQ-5774:

Timothy, thanks for the detailed explanation, that was very helpful to understand what's going
on under the covers.  Now that I know that OpenWire encodes a single message as one frame
than I am fine with using maxFrameSize and there is the added benefit of being able to check
the size before unmarshalling which would be preferred.  I was also not aware that message
properties could be missed when using other protocols which would certainly be bad.  I will
go ahead and close my pull request since my fix isn't going to be the ideal solution.

I agree with your last statement about applying maxFrameSize across all protocols.  I am primarily
interested in JMS and STOMP support so should I open another Jira to add maxFrameSize support
to all protocols? (especially STOMP for my use case)


> Add maximum message size per transport
> --------------------------------------
>                 Key: AMQ-5774
>                 URL:
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker
>    Affects Versions: 5.11.1
>            Reporter: Christopher L. Shannon
>            Priority: Minor
> It would be useful to be able to configure a limit for the maximum size per message that
can be sent by a client per transport.  This will help prevent bad behaving clients from affecting
the performance of the broker.

This message was sent by Atlassian JIRA

View raw message