[
https://issues.apache.org/jira/browse/QPID-8452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17185105#comment-17185105
]
Marek Laca commented on QPID-8452:
----------------------------------
The AMQP protocol specification states that the Data section of the message is
a byte array, which has the size limit 4 GB. The best possible improvement is
from 2 GB to 4 GB.
Broker utilizes the Java byte array and ByteBuffer that have the limit 2 GB.
Broker uses the sign integer for data size, length, position and the sign
integer can index 2 GB of data at most.
Fixing the issue would require an extensive change in the Broker. I would
suggest limiting the maximum message size that the broker can process to the 2
GB. Let the broker gracefully fail when client tries to send a message bigger
than 2 GB.
> Message larger than 2GB
> -----------------------
>
> Key: QPID-8452
> URL: https://issues.apache.org/jira/browse/QPID-8452
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
> Affects Versions: qpid-java-broker-8.0.0
> Reporter: Tomas Soltys
> Priority: Minor
>
> Seems like there is a 2GB limitation for how big the message can be. This is
> most likely due to usage of Int type.
> Also, when this limit is reached no exception is raised nor any message is
> printed into a broker log and sender seems to keep waiting for
> acknowledgement.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
