Hi there,
what are the exact limitations of topics which are spread over a cluster of
brokers? I want to use a mesh- or ring-topology with potentially quite a few
brokers (~10-150).
The wiki says [1]
Distributed Topics in Store/Forward
For topics the above algorithm is followed except, every in
Appreciate prompt response. I have to implement pool for my requirement and
will try to contribute it once I am done. Thanks
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Apache-Artemis-pooling-tp4707663p4707675.html
Sent from the ActiveMQ - User mailing list archive
>> Is there anything equivalent of
>> org.apache.activemq.pool.PooledConnectionFactory in Artemis?
not **yet** :) (accepting contributions though :P )
That wiki page is generic really. Creating / deleting connections on
any technology is an expensive process that will create a socket,
require a
Hi,
I am new to Apache artemis and was looking to pool jms related objects for
producer and consumer. We are using embedded Jetty container and do not
really want to go JCA route. Is there anything equivalent of
org.apache.activemq.pool.PooledConnectionFactory in Artemis?
I searched through c
I did further testing.
I am using Amazon Linux, "Amazon Linux AMI release 2015.09".
In this OS, this issue occurs.
Now I tried RHEL 7.1, and this issue didn't occur.
In Amazon Linux, this issue even occurs in only one client subscribing the
topic.
Another different point:
In RHEL 7.1, Apollo is i
