First you need to identify what kind of consumer you're using (i.e. API &
protocol). The broker supports multiple protocols and each protocol
potentially has multiple client implementations.
Also, please elaborate on:
- how you made your observations and drew your conclusions
- the message
Hi,
I am trying to improve the throughput of queue Consumers. At present the
Consumers are much slower than the Producers resulting in messages building up
inside a queue. From what I can see(maybe I’m wrong) it looks like messages are
sent to consumers of a queue one at a time in a round
Thanks for the update Chris.
+1
El jue., 12 sept. 2019 a las 8:45, Jean-Baptiste Onofré ()
escribió:
> Hi Chris,
>
> yes, I'm doing it at same time as I'm at ApacheCon (so a bit busy).
>
> The website update and announcement e-mail will happen very soon.
>
> Sorry for the delay.
>
> Regards
> JB
Hi Tim,
it's in my bucket, but I'm late on this (due to ApacheCon).
It will happen very soon.
Sorry again for the delay.
Regards
JB
On 12/09/2019 15:51, Timothy Bish wrote:
> Is there some hurdle that is holding up the process? Seems like we should
> have an announce thread by now and the
Hi Chris,
yes, I'm doing it at same time as I'm at ApacheCon (so a bit busy).
The website update and announcement e-mail will happen very soon.
Sorry for the delay.
Regards
JB
On 12/09/2019 15:51, Christopher Shannon wrote:
> Jean-Baptiste,
>
> Are you still working on updating the website
Jean-Baptiste,
Are you still working on updating the website and sending a release email?
It's important to get that out as soon as possible after a release is
finished and it's been almost 2 weeks.
On Sun, Sep 1, 2019 at 3:00 PM Jean-Baptiste Onofré wrote:
> Hi guys,
>
> this vote passed
Is there some hurdle that is holding up the process? Seems like we should
have an announce thread by now and the site should be updated.
On Fri, Sep 6, 2019 at 1:27 AM Jean-Baptiste Onofré wrote:
> Hi,
>
> It's on the way, I'm preparing the website update. Chris helped me to
> finalize the
Ok Robbie, I am going to apply your suggestions. Thank you for your insight.
On Thu, Sep 12, 2019 at 11:14 AM Robbie Gemmell
wrote:
> Even though it is annotated as a JMS ObjectMessage, simply observe the
> content type as well before treating it as an NMS Object Message, i.e
> check if the
Even though it is annotated as a JMS ObjectMessage, simply observe the
content type as well before treating it as an NMS Object Message, i.e
check if the content type is also
"application/x-java-serialized-object", and if so then you know it
must be treated as e.g. BytesMessage instead.
On Wed,
I believe so yes, notice that my comments were always specifically
about the serialized object payload messages.
On Wed, 11 Sep 2019 at 21:56, Krzysztof wrote:
>
> And what about AmqpTypedObjects that do not
> have "application/x-dotnet-serialized-object" nor
>
10 matches
Mail list logo
