Just sent the RC for 2.2.0..
I would appreciate if you could evaluate the release accordingly to
that vote thread on the dev list.
On Tue, Jul 25, 2017 at 8:47 AM, Clebert Suconic
wrote:
> I am sending the vote thread today for 2.2.0 with that fix.
>
> Can you try it
I'm referring to this part of the code:
https://github.com/apache/activemq/blob/master/activemq-broker/src/main/java/org/apache/activemq/broker/region/Queue.java#L882
--
View this message in context:
Thanks for the responses Tim. I was getting emails to my spam so I didn't see
them.
After some digging it appears I know the reason for the different
performance we see.
ActiveMQ has a threadpool of 1 thread persisting messages received to a
queue to disk. In the situation where we have multiple
Hello
I'm trying to limit the information available to a client from the broker.
In an activemq client I can use the getDestinationSource() function on a
connection to get a list of queues from the broker. Is there any way I can make
sure that the client can only see the queues it is has read or
Failover is what you want in this case, and I'm not aware of a built-in
workaround. But if anyone else does, please share.
Until we figure out why failover isn't working in the other thread, your
try-catch approach is the best option I know of.
Tim
On Jul 25, 2017 6:25 AM, "akpuvvada"
Do composite queues allow to forwardTo to another ActiveMQ broker instances?
Or it just allow to forwardTo queues in the same Broker instance.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMq-composite-queues-tp4728865.html
Sent from the ActiveMQ - User mailing
I am sending the vote thread today for 2.2.0 with that fix.
Can you try it then. Expect it within 11:00 EST today.
On Tue, Jul 25, 2017 at 5:35 AM Helge Waastad wrote:
> Hi,
> Try 2.2.0 snapshot.
> A few mem issues has been resolved since 2.1.0.
>
> /hw
>
> Sendt fra min
I can now reliably reproduce the duplication and I can prevent it. However,
the behavior leaves me a bit puzzled:
The issue is that the broker adds the message twice to the subscription, via
org.apache.activemq.broker.region.TopicSubscription#add
There is a check for duplicate messages,
I have configured two servers with static discovery as NoB.
I am trying to configure a Java client to connect to connect to these
servers dynamically.
How do I configured the Connection factory to have this working.
Please advise.
I tried fail-over URL and it is not working as expected.
OK, based on everything you just tested, it sounds like the problem is in
the ActiveMQ client code (either in the failover transport itself or maybe
somewhere else that's not hit when using the raw TCP transport). My best
guess at the moment is that we're somehow getting stuck (waiting for a
lock,
Hi,
Try 2.2.0 snapshot.
A few mem issues has been resolved since 2.1.0.
/hw
Sendt fra min iPhone
> Den 25. jul. 2017 kl. 11.06 skrev Deomisr :
>
> Hi,
>
> With my broker Mqtt configuration, it seems a memory leak appears after 3
> days.
> Indeed the memory increase but
Hi,
With my broker Mqtt configuration, it seems a memory leak appears after 3
days.
Indeed the memory increase but each full GC and GC not release enough
memory.
my JAVA_ARGS=" -XX:+PrintClassHistogram -XX:+UseG1GC -XX:+AggressiveOpts
-XX:+UseFastAccessorMethods -Xms4G -Xmx4G"
see below my
Hi Tim,
Please find below the observations.
1. Kill host1 so host2 becomes the master and there is no slave. Connect a
consumer with a URI of tcp://host1:61616. Does it connect? What's in the
consumer's logs?
ActiveMQConnectionFactory connectionFactory = new
13 matches
Mail list logo