It was this issue / commit: https://github.com/apache/activemq-artemis/commit/04f6424928a3d9cbc26f6b26f7c2e9b7f7bf7869
And BTW: Headers are not supposed to be large. Move the data to the body of the message. Headers are meant to be really small and only provide enough information for filtering. On Mon, Jun 3, 2024 at 7:36 PM Clebert Suconic <clebert.suco...@gmail.com> wrote: > > I had a fix for an almost large message becoming large and it should been > fixed on this latest release. > I don’t remember the JIRA now and I’m on the phone. But I may find it > tomorrow if you want it. > > Clebert Suconic > > > On Mon, Jun 3, 2024 at 5:53 PM Justin Bertram <jbert...@apache.org> wrote: >> >> What version of ActiveMQ Artemis are you using? Do you have a way to >> reproduce what you're seeing? If so, could you provide it? >> >> A while back there was an issue with flow control and large messages [1]. >> More recently I've seen some issues with messages which are _almost_ large >> with really big headers causing some problems, but you should be able to >> work-around that by increasing the min-large-message-size on your >> cluster-connection [2] in broker.xml. >> >> >> Justin >> >> [1] https://issues.apache.org/jira/browse/ARTEMIS-4003 >> [2] >> https://activemq.apache.org/components/artemis/documentation/latest/clusters.html#configuring-cluster-connections >> >> On Mon, Jun 3, 2024 at 4:35 AM Shiv Kumar Dixit >> <shivkumar.di...@it.eurofinseu.com.invalid> wrote: >> >> > Hi team, >> > Is there any update/input on this topic? Seems we are being hit by this >> > issue more frequently. >> > >> > Best Regards >> > Shiv >> > >> > -----Original Message----- >> > From: Shiv Kumar Dixit <shivkumar.di...@it.eurofinseu.com.INVALID> >> > Sent: Thursday, May 30, 2024 12:35 PM >> > To: users@activemq.apache.org >> > Subject: Issue in clustering due to Large JMS Header >> > >> > >> > >> > CAUTION: EXTERNAL EMAIL - Sent from an email domain that is not formally >> > trusted by Eurofins. >> > >> > Do not click on links or open attachments unless you recognise the sender >> > and are certain that the content is safe. >> > >> > Hi team, >> > We have a 2-node symmetric cluster. Producer writes on node1, and consumer >> > consumes from node2. As the clustering is working fine, messages move from >> > node1 to node2 for consumer. So far, the setup is working fine. >> > >> > One of our producers started writing larger custom JMS header to pass >> > stack trace information. Producer is able to write the message to node1 but >> > it is not being moved to node2 via clustering. Seems it gets stuck in the >> > clustering queue and does not move from node1 to node2. Once a message gets >> > stuck in clustering queue, other messages with or without large JMS headers >> > also get stuck and no message is delivered to node2 via clustering. >> > >> > Is there any restriction in custom JMS header size or total accumulative >> > JMS headers size? >> > >> > Since we can write the message with large custom JMS header at node1, if >> > there is any restriction in clustering which is not allowing message >> > movement inside cluster due to presence of large JMS header? >> > >> > >> > Thanks >> > Shiv >> > >> > >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org >> > For additional commands, e-mail: users-h...@activemq.apache.org >> > For further information, visit: https://activemq.apache.org/contact >> > >> > >> > -- Clebert Suconic --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org For additional commands, e-mail: users-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
