If you're running into issues with producer flow control you can try
setting a higher producerWindowSize (default is 65536 bytes). See the "Flow
Control" chapter [1] in the documentation for more info on that.

However, if the broker is blocking you because the address you're sending
to is getting full then the only way to "fix" that is to either change the
broker's configuration (e.g. increase max-size-bytes, using PAGE instead of
BLOCK, etc.) or consume messages more quickly.

Without more information it's hard to provide a specific recommendation.


Justin

[1]
https://activemq.apache.org/components/artemis/documentation/latest/flow-control.html

On Thu, May 18, 2023 at 8:33 AM Doug Whitfield
<dwhitfi...@perforce.com.invalid> wrote:

> Thanks Domenic!
>
> If we are hitting a credit limit in core API, how would we go about
> increasing the credits?
>
> From: Domenico Francesco Bruscino <bruscin...@gmail.com>
> Date: Wednesday, 17 May 2023 at 11:19
> To: users@activemq.apache.org <users@activemq.apache.org>
> Subject: Re: max_unreferenced_credits_cache_size in broker?
> Hi Douglas,
>
> there is no way to set MAX_UNREFERENCED_CREDITS_CACHE_SIZE because it is a
> static final int field of the ClientProducerCreditManager, for further
> details see
>
> https://github.com/apache/activemq-artemis/blob/2.28.0/artemis-core-client/src/main/java/org/apache/activemq/artemis/core/client/impl/ClientProducerCreditManagerImpl.java#L28
>
> Regards,
> Domenic
>
> On Fri, 12 May 2023 at 16:52, Doug Whitfield
> <dwhitfi...@perforce.com.invalid> wrote:
>
> > I need to set max_unreferenced_credits_cache_size for core. It looks like
> > from
> >
> https://github.com/search?q=repo%3Aapache%2Factivemq-artemis+max_unreferenced_credits_cache_size&type=code
> > that this has to be set on the client. Is that correct?
> >
> >
> > Douglas Whitfield | Enterprise Architect
> >
> >
> >
> >
> >
> > This e-mail may contain information that is privileged or confidential.
> If
> > you are not the intended recipient, please delete the e-mail and any
> > attachments and notify us immediately.
> >
> >
>
>
> CAUTION: This email originated from outside of the organization. Do not
> click on links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
> This e-mail may contain information that is privileged or confidential. If
> you are not the intended recipient, please delete the e-mail and any
> attachments and notify us immediately.
>
>

Reply via email to