tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Gallimore <jonathan.gallim...@gmail.com>
Subject Re: MDB / JMS Consumer Throttling?
Date Tue, 26 Feb 2019 20:44:27 GMT
> but this one is accessing an external resource that will error out if we
go too fast.

Out of curiosity (and because it might help with suggestions), what's the
external resource? Its "sounds" like a rate limited external webservice,
but I'm just guessing.

Sounds like we could wrap the connector somehow. I'll give it some thought
overnight.

Jon

On Tue, Feb 26, 2019 at 8:38 PM exabrial12 <exabrial@gmail.com> wrote:

> I know right? It's sort of funny actually. We have one instance of TomEE
> processing 5k+ msg/s for another purpose, but this one is accessing an
> external resource that will error out if we go too fast.
>
> We can choke resources by limiting the pool and maxSessions, but we need
> something more predictable than that.
>
>
> If we add a throttling algorithm to the MDB code, we'll be taking time off
> the JTA timeout, and Thread.sleep() is hardly ever a good idea.
>
>
> We could possibly limit it with Camel at the broker level, but we don't
> want
> to put business logic there.
>
>
> If there was a way to inject delay before the JTA timeout started counting,
> that would be ideal.
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message