Here is my finding. With a producer window size of 1 mb (same as my
per-destination memory limit) and a payload of 2 kb both producer and
consumer are eventually stopped after sending fewer than 2k messages while
using a batch size > 1. When I used 100 as the batch size, I get the
following excepti
Hi
Any plans to support it in ActiveMQ 5.x?
Regards
Krzysztof
On 07.09.2015 19:31, Vitaliy Semochkin wrote:
> Thank you very much Timothy! That's exactly what I was looking for!
>
> On Mon, Sep 7, 2015 at 6:31 PM, Timothy Bish wrote:
>
>> On 09/07/2015 11:11 AM, Vitaliy Semochkin wrote:
>>> Hi
Thank you very much Timothy! That's exactly what I was looking for!
On Mon, Sep 7, 2015 at 6:31 PM, Timothy Bish wrote:
> On 09/07/2015 11:11 AM, Vitaliy Semochkin wrote:
> > Hi
> >
> > Is ActiveMQ team working on implementing JMS 2.0 support?
> > When and in which project (since apollo is close
@christopher "test message from supplier to consumer is 12000" .Mean to
start the consumer waits to receive messages, if consumers don't exit 15
seconds didn't receive the message, as producers start, timing T1, send
messages, then query whether the consumer process, if the exit time is T2,
the to
"did you use the same settings between the two tests? if you have
a test under the same settings and conditions giving you different result,
then you should share your test, and so people could identify the
difference."
@Clebert Suconic Yes, Two machines configuration is the same, two tests f
On 09/07/2015 11:11 AM, Vitaliy Semochkin wrote:
> Hi
>
> Is ActiveMQ team working on implementing JMS 2.0 support?
> When and in which project (since apollo is closed) can we expect it?
>
> Regards
> Vitaliy S
>
The ActiveMQ Artemis broker has support for JMS 2.0:
https://activemq.apache.org/artem
Hi
Is ActiveMQ team working on implementing JMS 2.0 support?
When and in which project (since apollo is closed) can we expect it?
Regards
Vitaliy S
