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 <[email protected]> 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 <[email protected]> > 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 > >
