You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Aman Nankani <am...@gmail.com> on 2022/05/06 07:09:54 UTC
ActiveMQ Classic STOMP doesn't work with big transport objects (>500MB)
I am new to this mailing list, so please forgive me if I am doing something
wrong or if I am missing something in the procedure.
So, for context,
Up until now, I was using websocket in my application via an in-memory
broker which had the configuration option of increasing the size to handle
big content.
But, from now on, I'm going to use External Broker for websockets
(ActiveMQ) for *Spring over STOMP protocol*.
The problem that I am facing is that when I try to send big files >500 MB
of data, the ActiveMQ server throws the following exception:
"Exception occurred processing: <Unknown> ->
org.apache.activemq.transport.stomp.ProtocolException: The maximum data
length was exceeded"
To solve this, I have gone through the doc and tweaked the following
configurations in the transport connectors of STOMP:
- wireFormat.maxFrameSize=1073741824
- wireformat.maxTextMessageSize=1073741824
- wireformat.maxDataLength=1073741824
- websocket.maxTextMessageSize=1073741824
The final transport connector for STOMP looks like this:
<transportConnector name="stomp" uri="stomp://
0.0.0.0:61613?maximumConnections=1000&wireFormat.maxFrameSize=1073741824&wireFormat.maxInactivityDuration=0&wireformat.maxTextMessageSize=1073741824&wireformat.maxDataLength=1073741824&transport.useInactivityMonitor=false&trace=true&websocket.maxTextMessageSize=1073741824
"/>
Despite adding these, the same exception is coming if I try to send a huge
amount of data in a single message.
Can anyone help me with this? Is there any configuration that I might have
missed that can potentially solve this?
Thank you all for your time.
Once again, I apologize if there's any mistake from my side as this is my
first time sending a mail to this mail list.
Regards
Aman Nankani
Re: ActiveMQ Classic STOMP doesn't work with big transport objects (>500MB)
Posted by Aman Nankani <am...@gmail.com>.
Got your point now Matt.
But I verified, the data I am trying to send over STOMP protocol is of
162MB, and its failing there.
I think it's crossing a threshold of 100 MB, if the data is less than 100
MB, everything is working fine.
Is there any configuration left from my side which can increase this 100 MB
threshold so that messages above that size can work fine?
Also, on a similar note, I tried setting up ActiveMQ Artemis, and this same
thing works perfectly fine over there.
But I am not inclined to use Artemis as of now. Hence, trying to find a
solution for Classic.
Thank you!
On Wed, May 11, 2022 at 7:16 PM Matt Pavlovich <ma...@gmail.com> wrote:
> Hi Aman,
>
> Yes, there is a limit to protect the broker from denial of service and
> flooding. The settings in your tcp transport have a value ~1 GB limit set:
>
> These values are in bytes:
>
> - wireFormat.maxFrameSize=1073741824
> - wireformat.maxTextMessageSize=1073741824
> - wireformat.maxDataLength=1073741824
> - websocket.maxTextMessageSize=1073741824
>
> Matt Pavlovich
>
> > On May 10, 2022, at 7:42 PM, Aman Nankani <am...@gmail.com>
> wrote:
> >
> > Hello Matt,
> >
> > I might have missed something.
> > Is there a limit on the message size?
> >
> > If so, this might be the case and that's why my messages might be
> failing.
> >
> > If you don't mind, can you please point me to a reference doc where it's
> > the message size limits are mentioned.
> >
> > Again, thank you for your time.
> >
> >
> > On Wed, 11 May, 2022, 2:05 am Matt Pavlovich, <ma...@gmail.com>
> wrote:
> >
> >> Hi Aman-
> >>
> >> The message size limits is well tested. Do you know the size of the
> >> message is less than the ~1GB limit?
> >>
> >> Thanks,
> >> Matt Pavlovich
> >>
> >>> On May 10, 2022, at 7:09 AM, Aman Nankani <am...@gmail.com>
> >> wrote:
> >>>
> >>> Hi Matt,
> >>>
> >>> The following is the logs that I see on the server logs:
> >>>
> >>> 2022-05-10 09:27:52,789 | WARN | Exception occurred for client
> >>> ID:ip-xxx-30-0-87.ec2.internal-xxxxxx-1652174804014-3:2
> >>> (tcp://xx.16.xx.115:39556) processing: <Unknown> ->
> >>> org.apache.activemq.transport.stomp.ProtocolException: The maximum data
> >>> length was exceeded |
> >> org.apache.activemq.transport.stomp.ProtocolConverter
> >>> | ActiveMQ Transport: tcp:///xx.xx.xx.115:39556@61613
> >>> 2022-05-10 09:27:52,792 | WARN | Transport Connection to:
> >>> tcp://xx.16.xx.115:39556 failed: The maximum data length was exceeded |
> >>> org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ
> >>> Transport: tcp:///xx.16.xx.115:39556@61613
> >>>
> >>> Thanks,
> >>> Aman Nankani
> >>>
> >>> On Fri, May 6, 2022 at 8:06 PM Matt Pavlovich <ma...@gmail.com>
> >> wrote:
> >>>
> >>>> Hi Aman-
> >>>>
> >>>> Can you share the full stack trace from the server-side log?
> >>>>
> >>>> Thanks,
> >>>> Matt Palvovich
> >>>>
> >>>>> On May 6, 2022, at 2:09 AM, Aman Nankani <am...@gmail.com>
> >>>> wrote:
> >>>>>
> >>>>> I am new to this mailing list, so please forgive me if I am doing
> >>>> something
> >>>>> wrong or if I am missing something in the procedure.
> >>>>>
> >>>>> So, for context,
> >>>>>
> >>>>> Up until now, I was using websocket in my application via an
> in-memory
> >>>>> broker which had the configuration option of increasing the size to
> >>>> handle
> >>>>> big content.
> >>>>>
> >>>>> But, from now on, I'm going to use External Broker for websockets
> >>>>> (ActiveMQ) for *Spring over STOMP protocol*.
> >>>>> The problem that I am facing is that when I try to send big files
> >500
> >> MB
> >>>>> of data, the ActiveMQ server throws the following exception:
> >>>>>
> >>>>> "Exception occurred processing: <Unknown> ->
> >>>>> org.apache.activemq.transport.stomp.ProtocolException: The maximum
> data
> >>>>> length was exceeded"
> >>>>>
> >>>>> To solve this, I have gone through the doc and tweaked the following
> >>>>> configurations in the transport connectors of STOMP:
> >>>>> - wireFormat.maxFrameSize=1073741824
> >>>>> - wireformat.maxTextMessageSize=1073741824
> >>>>> - wireformat.maxDataLength=1073741824
> >>>>> - websocket.maxTextMessageSize=1073741824
> >>>>>
> >>>>> The final transport connector for STOMP looks like this:
> >>>>>
> >>>>> <transportConnector name="stomp" uri="stomp://
> >>>>>
> >>>>
> >>
> 0.0.0.0:61613?maximumConnections=1000&wireFormat.maxFrameSize=1073741824&wireFormat.maxInactivityDuration=0&wireformat.maxTextMessageSize=1073741824&wireformat.maxDataLength=1073741824&transport.useInactivityMonitor=false&trace=true&websocket.maxTextMessageSize=1073741824
> >>>>> "/>
> >>>>>
> >>>>> Despite adding these, the same exception is coming if I try to send a
> >>>> huge
> >>>>> amount of data in a single message.
> >>>>>
> >>>>> Can anyone help me with this? Is there any configuration that I might
> >>>> have
> >>>>> missed that can potentially solve this?
> >>>>>
> >>>>> Thank you all for your time.
> >>>>> Once again, I apologize if there's any mistake from my side as this
> is
> >> my
> >>>>> first time sending a mail to this mail list.
> >>>>>
> >>>>> Regards
> >>>>> Aman Nankani
> >>>>
> >>>>
> >>
> >>
>
>
Re: ActiveMQ Classic STOMP doesn't work with big transport objects (>500MB)
Posted by Matt Pavlovich <ma...@gmail.com>.
Hi Aman,
Yes, there is a limit to protect the broker from denial of service and flooding. The settings in your tcp transport have a value ~1 GB limit set:
These values are in bytes:
- wireFormat.maxFrameSize=1073741824
- wireformat.maxTextMessageSize=1073741824
- wireformat.maxDataLength=1073741824
- websocket.maxTextMessageSize=1073741824
Matt Pavlovich
> On May 10, 2022, at 7:42 PM, Aman Nankani <am...@gmail.com> wrote:
>
> Hello Matt,
>
> I might have missed something.
> Is there a limit on the message size?
>
> If so, this might be the case and that's why my messages might be failing.
>
> If you don't mind, can you please point me to a reference doc where it's
> the message size limits are mentioned.
>
> Again, thank you for your time.
>
>
> On Wed, 11 May, 2022, 2:05 am Matt Pavlovich, <ma...@gmail.com> wrote:
>
>> Hi Aman-
>>
>> The message size limits is well tested. Do you know the size of the
>> message is less than the ~1GB limit?
>>
>> Thanks,
>> Matt Pavlovich
>>
>>> On May 10, 2022, at 7:09 AM, Aman Nankani <am...@gmail.com>
>> wrote:
>>>
>>> Hi Matt,
>>>
>>> The following is the logs that I see on the server logs:
>>>
>>> 2022-05-10 09:27:52,789 | WARN | Exception occurred for client
>>> ID:ip-xxx-30-0-87.ec2.internal-xxxxxx-1652174804014-3:2
>>> (tcp://xx.16.xx.115:39556) processing: <Unknown> ->
>>> org.apache.activemq.transport.stomp.ProtocolException: The maximum data
>>> length was exceeded |
>> org.apache.activemq.transport.stomp.ProtocolConverter
>>> | ActiveMQ Transport: tcp:///xx.xx.xx.115:39556@61613
>>> 2022-05-10 09:27:52,792 | WARN | Transport Connection to:
>>> tcp://xx.16.xx.115:39556 failed: The maximum data length was exceeded |
>>> org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ
>>> Transport: tcp:///xx.16.xx.115:39556@61613
>>>
>>> Thanks,
>>> Aman Nankani
>>>
>>> On Fri, May 6, 2022 at 8:06 PM Matt Pavlovich <ma...@gmail.com>
>> wrote:
>>>
>>>> Hi Aman-
>>>>
>>>> Can you share the full stack trace from the server-side log?
>>>>
>>>> Thanks,
>>>> Matt Palvovich
>>>>
>>>>> On May 6, 2022, at 2:09 AM, Aman Nankani <am...@gmail.com>
>>>> wrote:
>>>>>
>>>>> I am new to this mailing list, so please forgive me if I am doing
>>>> something
>>>>> wrong or if I am missing something in the procedure.
>>>>>
>>>>> So, for context,
>>>>>
>>>>> Up until now, I was using websocket in my application via an in-memory
>>>>> broker which had the configuration option of increasing the size to
>>>> handle
>>>>> big content.
>>>>>
>>>>> But, from now on, I'm going to use External Broker for websockets
>>>>> (ActiveMQ) for *Spring over STOMP protocol*.
>>>>> The problem that I am facing is that when I try to send big files >500
>> MB
>>>>> of data, the ActiveMQ server throws the following exception:
>>>>>
>>>>> "Exception occurred processing: <Unknown> ->
>>>>> org.apache.activemq.transport.stomp.ProtocolException: The maximum data
>>>>> length was exceeded"
>>>>>
>>>>> To solve this, I have gone through the doc and tweaked the following
>>>>> configurations in the transport connectors of STOMP:
>>>>> - wireFormat.maxFrameSize=1073741824
>>>>> - wireformat.maxTextMessageSize=1073741824
>>>>> - wireformat.maxDataLength=1073741824
>>>>> - websocket.maxTextMessageSize=1073741824
>>>>>
>>>>> The final transport connector for STOMP looks like this:
>>>>>
>>>>> <transportConnector name="stomp" uri="stomp://
>>>>>
>>>>
>> 0.0.0.0:61613?maximumConnections=1000&wireFormat.maxFrameSize=1073741824&wireFormat.maxInactivityDuration=0&wireformat.maxTextMessageSize=1073741824&wireformat.maxDataLength=1073741824&transport.useInactivityMonitor=false&trace=true&websocket.maxTextMessageSize=1073741824
>>>>> "/>
>>>>>
>>>>> Despite adding these, the same exception is coming if I try to send a
>>>> huge
>>>>> amount of data in a single message.
>>>>>
>>>>> Can anyone help me with this? Is there any configuration that I might
>>>> have
>>>>> missed that can potentially solve this?
>>>>>
>>>>> Thank you all for your time.
>>>>> Once again, I apologize if there's any mistake from my side as this is
>> my
>>>>> first time sending a mail to this mail list.
>>>>>
>>>>> Regards
>>>>> Aman Nankani
>>>>
>>>>
>>
>>
Re: ActiveMQ Classic STOMP doesn't work with big transport objects (>500MB)
Posted by Aman Nankani <am...@gmail.com>.
Hello Matt,
I might have missed something.
Is there a limit on the message size?
If so, this might be the case and that's why my messages might be failing.
If you don't mind, can you please point me to a reference doc where it's
the message size limits are mentioned.
Again, thank you for your time.
On Wed, 11 May, 2022, 2:05 am Matt Pavlovich, <ma...@gmail.com> wrote:
> Hi Aman-
>
> The message size limits is well tested. Do you know the size of the
> message is less than the ~1GB limit?
>
> Thanks,
> Matt Pavlovich
>
> > On May 10, 2022, at 7:09 AM, Aman Nankani <am...@gmail.com>
> wrote:
> >
> > Hi Matt,
> >
> > The following is the logs that I see on the server logs:
> >
> > 2022-05-10 09:27:52,789 | WARN | Exception occurred for client
> > ID:ip-xxx-30-0-87.ec2.internal-xxxxxx-1652174804014-3:2
> > (tcp://xx.16.xx.115:39556) processing: <Unknown> ->
> > org.apache.activemq.transport.stomp.ProtocolException: The maximum data
> > length was exceeded |
> org.apache.activemq.transport.stomp.ProtocolConverter
> > | ActiveMQ Transport: tcp:///xx.xx.xx.115:39556@61613
> > 2022-05-10 09:27:52,792 | WARN | Transport Connection to:
> > tcp://xx.16.xx.115:39556 failed: The maximum data length was exceeded |
> > org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ
> > Transport: tcp:///xx.16.xx.115:39556@61613
> >
> > Thanks,
> > Aman Nankani
> >
> > On Fri, May 6, 2022 at 8:06 PM Matt Pavlovich <ma...@gmail.com>
> wrote:
> >
> >> Hi Aman-
> >>
> >> Can you share the full stack trace from the server-side log?
> >>
> >> Thanks,
> >> Matt Palvovich
> >>
> >>> On May 6, 2022, at 2:09 AM, Aman Nankani <am...@gmail.com>
> >> wrote:
> >>>
> >>> I am new to this mailing list, so please forgive me if I am doing
> >> something
> >>> wrong or if I am missing something in the procedure.
> >>>
> >>> So, for context,
> >>>
> >>> Up until now, I was using websocket in my application via an in-memory
> >>> broker which had the configuration option of increasing the size to
> >> handle
> >>> big content.
> >>>
> >>> But, from now on, I'm going to use External Broker for websockets
> >>> (ActiveMQ) for *Spring over STOMP protocol*.
> >>> The problem that I am facing is that when I try to send big files >500
> MB
> >>> of data, the ActiveMQ server throws the following exception:
> >>>
> >>> "Exception occurred processing: <Unknown> ->
> >>> org.apache.activemq.transport.stomp.ProtocolException: The maximum data
> >>> length was exceeded"
> >>>
> >>> To solve this, I have gone through the doc and tweaked the following
> >>> configurations in the transport connectors of STOMP:
> >>> - wireFormat.maxFrameSize=1073741824
> >>> - wireformat.maxTextMessageSize=1073741824
> >>> - wireformat.maxDataLength=1073741824
> >>> - websocket.maxTextMessageSize=1073741824
> >>>
> >>> The final transport connector for STOMP looks like this:
> >>>
> >>> <transportConnector name="stomp" uri="stomp://
> >>>
> >>
> 0.0.0.0:61613?maximumConnections=1000&wireFormat.maxFrameSize=1073741824&wireFormat.maxInactivityDuration=0&wireformat.maxTextMessageSize=1073741824&wireformat.maxDataLength=1073741824&transport.useInactivityMonitor=false&trace=true&websocket.maxTextMessageSize=1073741824
> >>> "/>
> >>>
> >>> Despite adding these, the same exception is coming if I try to send a
> >> huge
> >>> amount of data in a single message.
> >>>
> >>> Can anyone help me with this? Is there any configuration that I might
> >> have
> >>> missed that can potentially solve this?
> >>>
> >>> Thank you all for your time.
> >>> Once again, I apologize if there's any mistake from my side as this is
> my
> >>> first time sending a mail to this mail list.
> >>>
> >>> Regards
> >>> Aman Nankani
> >>
> >>
>
>
Re: ActiveMQ Classic STOMP doesn't work with big transport objects (>500MB)
Posted by Matt Pavlovich <ma...@gmail.com>.
Hi Aman-
The message size limits is well tested. Do you know the size of the message is less than the ~1GB limit?
Thanks,
Matt Pavlovich
> On May 10, 2022, at 7:09 AM, Aman Nankani <am...@gmail.com> wrote:
>
> Hi Matt,
>
> The following is the logs that I see on the server logs:
>
> 2022-05-10 09:27:52,789 | WARN | Exception occurred for client
> ID:ip-xxx-30-0-87.ec2.internal-xxxxxx-1652174804014-3:2
> (tcp://xx.16.xx.115:39556) processing: <Unknown> ->
> org.apache.activemq.transport.stomp.ProtocolException: The maximum data
> length was exceeded | org.apache.activemq.transport.stomp.ProtocolConverter
> | ActiveMQ Transport: tcp:///xx.xx.xx.115:39556@61613
> 2022-05-10 09:27:52,792 | WARN | Transport Connection to:
> tcp://xx.16.xx.115:39556 failed: The maximum data length was exceeded |
> org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ
> Transport: tcp:///xx.16.xx.115:39556@61613
>
> Thanks,
> Aman Nankani
>
> On Fri, May 6, 2022 at 8:06 PM Matt Pavlovich <ma...@gmail.com> wrote:
>
>> Hi Aman-
>>
>> Can you share the full stack trace from the server-side log?
>>
>> Thanks,
>> Matt Palvovich
>>
>>> On May 6, 2022, at 2:09 AM, Aman Nankani <am...@gmail.com>
>> wrote:
>>>
>>> I am new to this mailing list, so please forgive me if I am doing
>> something
>>> wrong or if I am missing something in the procedure.
>>>
>>> So, for context,
>>>
>>> Up until now, I was using websocket in my application via an in-memory
>>> broker which had the configuration option of increasing the size to
>> handle
>>> big content.
>>>
>>> But, from now on, I'm going to use External Broker for websockets
>>> (ActiveMQ) for *Spring over STOMP protocol*.
>>> The problem that I am facing is that when I try to send big files >500 MB
>>> of data, the ActiveMQ server throws the following exception:
>>>
>>> "Exception occurred processing: <Unknown> ->
>>> org.apache.activemq.transport.stomp.ProtocolException: The maximum data
>>> length was exceeded"
>>>
>>> To solve this, I have gone through the doc and tweaked the following
>>> configurations in the transport connectors of STOMP:
>>> - wireFormat.maxFrameSize=1073741824
>>> - wireformat.maxTextMessageSize=1073741824
>>> - wireformat.maxDataLength=1073741824
>>> - websocket.maxTextMessageSize=1073741824
>>>
>>> The final transport connector for STOMP looks like this:
>>>
>>> <transportConnector name="stomp" uri="stomp://
>>>
>> 0.0.0.0:61613?maximumConnections=1000&wireFormat.maxFrameSize=1073741824&wireFormat.maxInactivityDuration=0&wireformat.maxTextMessageSize=1073741824&wireformat.maxDataLength=1073741824&transport.useInactivityMonitor=false&trace=true&websocket.maxTextMessageSize=1073741824
>>> "/>
>>>
>>> Despite adding these, the same exception is coming if I try to send a
>> huge
>>> amount of data in a single message.
>>>
>>> Can anyone help me with this? Is there any configuration that I might
>> have
>>> missed that can potentially solve this?
>>>
>>> Thank you all for your time.
>>> Once again, I apologize if there's any mistake from my side as this is my
>>> first time sending a mail to this mail list.
>>>
>>> Regards
>>> Aman Nankani
>>
>>
Re: ActiveMQ Classic STOMP doesn't work with big transport objects (>500MB)
Posted by Aman Nankani <am...@gmail.com>.
Hi Matt,
The following is the logs that I see on the server logs:
2022-05-10 09:27:52,789 | WARN | Exception occurred for client
ID:ip-xxx-30-0-87.ec2.internal-xxxxxx-1652174804014-3:2
(tcp://xx.16.xx.115:39556) processing: <Unknown> ->
org.apache.activemq.transport.stomp.ProtocolException: The maximum data
length was exceeded | org.apache.activemq.transport.stomp.ProtocolConverter
| ActiveMQ Transport: tcp:///xx.xx.xx.115:39556@61613
2022-05-10 09:27:52,792 | WARN | Transport Connection to:
tcp://xx.16.xx.115:39556 failed: The maximum data length was exceeded |
org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ
Transport: tcp:///xx.16.xx.115:39556@61613
Thanks,
Aman Nankani
On Fri, May 6, 2022 at 8:06 PM Matt Pavlovich <ma...@gmail.com> wrote:
> Hi Aman-
>
> Can you share the full stack trace from the server-side log?
>
> Thanks,
> Matt Palvovich
>
> > On May 6, 2022, at 2:09 AM, Aman Nankani <am...@gmail.com>
> wrote:
> >
> > I am new to this mailing list, so please forgive me if I am doing
> something
> > wrong or if I am missing something in the procedure.
> >
> > So, for context,
> >
> > Up until now, I was using websocket in my application via an in-memory
> > broker which had the configuration option of increasing the size to
> handle
> > big content.
> >
> > But, from now on, I'm going to use External Broker for websockets
> > (ActiveMQ) for *Spring over STOMP protocol*.
> > The problem that I am facing is that when I try to send big files >500 MB
> > of data, the ActiveMQ server throws the following exception:
> >
> > "Exception occurred processing: <Unknown> ->
> > org.apache.activemq.transport.stomp.ProtocolException: The maximum data
> > length was exceeded"
> >
> > To solve this, I have gone through the doc and tweaked the following
> > configurations in the transport connectors of STOMP:
> > - wireFormat.maxFrameSize=1073741824
> > - wireformat.maxTextMessageSize=1073741824
> > - wireformat.maxDataLength=1073741824
> > - websocket.maxTextMessageSize=1073741824
> >
> > The final transport connector for STOMP looks like this:
> >
> > <transportConnector name="stomp" uri="stomp://
> >
> 0.0.0.0:61613?maximumConnections=1000&wireFormat.maxFrameSize=1073741824&wireFormat.maxInactivityDuration=0&wireformat.maxTextMessageSize=1073741824&wireformat.maxDataLength=1073741824&transport.useInactivityMonitor=false&trace=true&websocket.maxTextMessageSize=1073741824
> > "/>
> >
> > Despite adding these, the same exception is coming if I try to send a
> huge
> > amount of data in a single message.
> >
> > Can anyone help me with this? Is there any configuration that I might
> have
> > missed that can potentially solve this?
> >
> > Thank you all for your time.
> > Once again, I apologize if there's any mistake from my side as this is my
> > first time sending a mail to this mail list.
> >
> > Regards
> > Aman Nankani
>
>
Re: ActiveMQ Classic STOMP doesn't work with big transport objects (>500MB)
Posted by Matt Pavlovich <ma...@gmail.com>.
Hi Aman-
Can you share the full stack trace from the server-side log?
Thanks,
Matt Palvovich
> On May 6, 2022, at 2:09 AM, Aman Nankani <am...@gmail.com> wrote:
>
> I am new to this mailing list, so please forgive me if I am doing something
> wrong or if I am missing something in the procedure.
>
> So, for context,
>
> Up until now, I was using websocket in my application via an in-memory
> broker which had the configuration option of increasing the size to handle
> big content.
>
> But, from now on, I'm going to use External Broker for websockets
> (ActiveMQ) for *Spring over STOMP protocol*.
> The problem that I am facing is that when I try to send big files >500 MB
> of data, the ActiveMQ server throws the following exception:
>
> "Exception occurred processing: <Unknown> ->
> org.apache.activemq.transport.stomp.ProtocolException: The maximum data
> length was exceeded"
>
> To solve this, I have gone through the doc and tweaked the following
> configurations in the transport connectors of STOMP:
> - wireFormat.maxFrameSize=1073741824
> - wireformat.maxTextMessageSize=1073741824
> - wireformat.maxDataLength=1073741824
> - websocket.maxTextMessageSize=1073741824
>
> The final transport connector for STOMP looks like this:
>
> <transportConnector name="stomp" uri="stomp://
> 0.0.0.0:61613?maximumConnections=1000&wireFormat.maxFrameSize=1073741824&wireFormat.maxInactivityDuration=0&wireformat.maxTextMessageSize=1073741824&wireformat.maxDataLength=1073741824&transport.useInactivityMonitor=false&trace=true&websocket.maxTextMessageSize=1073741824
> "/>
>
> Despite adding these, the same exception is coming if I try to send a huge
> amount of data in a single message.
>
> Can anyone help me with this? Is there any configuration that I might have
> missed that can potentially solve this?
>
> Thank you all for your time.
> Once again, I apologize if there's any mistake from my side as this is my
> first time sending a mail to this mail list.
>
> Regards
> Aman Nankani