Is your issue that certain consumers become too slow? If so, you can always
set the JMSXGroupSeq header to −1 to force a new consumer (maybe set this
periodically or after a certain number of messages)...
here is a good article that discusses this a bit...
http://scottcranton.blogspot.com/20
Brilliant! Many thanks Gary - v5.5.0 fixed the issue.
If you have time, I'd be very interested to read the JIRA should you find
it.
Great work, and thanks for the response.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Memory-Leak-In-TransportConnector-tp3635116p3637273
Dear Active MQ users group,
I am benchmarking the maximum number of queues that activemq can support;
With default config I can
go up to 1000 queues;
For more than 1000, I need to add in the -
xbean:conf/activemq-scalability.xml to the command line for
broker startup;
I also needed to change
There is a transport listener interface that can give you indications
of reconnects.
see: org.apache.activemq.ActiveMQConnection#addTransportListener
For a unit test, have a look at:
org.apache.activemq.usecases.BrokerQueueNetworkWithDisconnectTest
this uses a socket proxy to simulate a network f
Sorry for the late response.
There is already a Jira issue
(https://issues.apache.org/jira/browse/AMQ-3353).
While I do know how to reproduce it using multicast brokers and producer and
consumer from the example directory, I do not know how to make a junit case.
If it's not difficult, I could try
Typo.
I am using this :
For client 1: tcp://masterhost:port
For client 2: tcp://slavehost:port
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Master-Slave-configuring-clients-tp3630225p3635592.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Slave broker is not usable until Master goes down.
Currently I am configuring clients like this:
For client 1: tcp://masterhost:port
For client 2: vm://slavehost:port
This seem to be causing message loss. Any thoughts.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/M
CACHE_CONSUMER will help, but also setting the networkConnector attribute
destinationFilter and if you don't want to bridge temp destinations
set bridgeTempDestinations="false"
It defaults to ">" so the network connector gets consumer advisories
for all destinations, but ideally it should be correl
Hi,
we currently use message groups to ensure ordered delivery of messages
within a given group. As noted on the documentation for message
groups, this often does not scale very well with variable consumer
counts, as in this case the oldest consumers will hog all message
groups.
In our use-case,
Hi,
we plan a setup with lots of remote sites, each of them having their
own broker which are then connected via a network-of-brokers via a
duplex connector. We'd like to use dynamicallyIncludedDestinations,
but even in our small test installation we already see huge amounts of
advisory messages.
that sounds familiar, as in an issue that has been resolved, but I
can't quickly find a corresponding jira to show that it is fixed.
It sounds like something that could be easily reproducible in a test
setup. Maybe try and replicate and then try with 5.5.
If the problem persists with 5.5, and ther
Hi All
I have a Java application (A) with 4Gb of heap using an embedded broker
(v5.3.1). I have a second application (B) also containing a broker.
Messages are sent to broker A which auto-forwards them to broker B. We use
this setup for fault tolerance. We want to be able to continue to run A
12 matches
Mail list logo
