I'm glad the issue is resolved. Thanks for following up!
Justin On Tue, May 7, 2024 at 2:12 AM <herbert.helmstr...@systema.com> wrote: > Hello Justin, > > Thank You for the response. You have been completely right. > My conclusion was too hasty. When I tried to reproduce the issue (as first > step to remove, it) it was no longer to observe. > I now believe it was a memory shortage, After increasing the Heap Memory > to 4G the broker works like a charm > > Best Regards > > Herbert > ------------------------------ > > *Herbert Helmstreit* > Senior Software Engineer > > Phone: +49 941 / 7 83 92 36 > herbert.helmstr...@systema.com > > www.systema.com > > [image: LinkedIn] <https://www.linkedin.com/company/systema-gmbh/>[image: > Facebook] <https://de-de.facebook.com/SYSTEMA.automation/>[image: XING] > <https://www.xing.com/pages/systemagmbh> > > SYSTEMA > Systementwicklung Dipl.-Inf. Manfred Austen GmbH > > Manfred-von-Ardenne-Ring 6 | 01099 Dresden > HRB 11256 Amtsgericht Dresden | USt.-ID DE 159 607 786 > Geschäftsführer: Manfred Austen, CEO und Dr. Ulf Martin, COO > > P Please check whether a printout of this e-mail is really necessary. > > > > > Von: "Justin Bertram" <jbert...@apache.org> > An: users@activemq.apache.org > Datum: 03.05.2024 20:46 > Betreff: [Ext] Re: Stomp acceptor causes address memory rise > ------------------------------ > > > > Have you conclusively determined that the STOMP acceptor is _causing_ the > difference? If so, do you have a test to reproduce this behavior? Perhaps > this is just a coincidence? > > > Is the Messagebuffer to high? > > I'm not sure what you mean by "Messagebuffer." Can you clarify? > > > Justin > > > On Fri, May 3, 2024 at 10:21 AM <herbert.helmstr...@systema.com> wrote: > > > Hello Community > > > > in an artemis 2.33 cluster with relatively high rate of core messages we > > enabled a stomp acceptor on one broker. > > > > Compared to the other brokers in the cluster that have <1 MiB used > Address > > Memory the modified guy goes up to 250 MiB. > > There is no stomp client attached. The value of the address memory gauge > > seems to be sensitive to the message rate. > > We are using non-persistent messaging with a TTL of 3 min. Byterate*TTL > > could be close to the value of 250 MiB. > > > > Is the Messagebuffer to high? > > { > > "scheme": "tcp", > > "tcpReceiveBufferSize": "1048576", > > "port": "61613", > > "host": "0.0.0.0", > > "protocols": "STOMP", > > "useEpoll": "true", > > "tcpSendBufferSize": "1048576" > > } > > > > Can somebody recommend a measure? > > > > Best Regards > > > > Herbert > > > > ------------------------------ > > > > *Herbert Helmstreit* > > Senior Software Engineer > > > > Phone: +49 941 / 7 83 92 36 > > herbert.helmstr...@systema.com > > > > www.systema.com > > > > [image: LinkedIn] <https://www.linkedin.com/company/systema-gmbh/ > >[image: > > Facebook] <https://de-de.facebook.com/SYSTEMA.automation/>[image: XING] > > <https://www.xing.com/pages/systemagmbh> > > > > SYSTEMA > > Systementwicklung Dipl.-Inf. Manfred Austen GmbH > > > > Manfred-von-Ardenne-Ring 6 | 01099 Dresden > > HRB 11256 Amtsgericht Dresden | USt.-ID DE 159 607 786 > > Geschäftsführer: Manfred Austen, CEO und Dr. Ulf Martin, COO > > > > P Please check whether a printout of this e-mail is really necessary. > > > > > > > >
