Is it possible to configure a network connector such that on startup it is
disabled, but may be activated later via JMX or updated config?
Raffi
This e-mail transmission may contain information that is proprietary,
privileged and/or confidential and is intended exclusively for the person(s) to
Ah... based on selectors...
I don't think ActiveMQ5 supports it either.. it's a fundamental
problem that usually goes against the messaging context.
Most of times I have seen this pattern being used the Messaging system
was being used for store & retrieve. I.e. a database like application.
which
I have the following code so far:-
Producer code:-
public class TradeProducer implements Runnable {
public void run() {
try {
// Create a ConnectionFactory
ActiveMQConnectionFactory connectionFactory = new
ActiveMQConnectionFactory("vm://localho
As far as I know redistribution based on selectors is not currently supported
in Artemis.
Justin
did you look at
examples/features/clustered/queue-message-redistribution under the
distribution?
that has the exact settings you need for that to happen. if you have
any questions after that let us know.
On Thu, Oct 29, 2015 at 10:12 PM, ohsgx wrote:
> Hi.
> I was clustering two artemis node, e
Hi.
I was clustering two artemis node, each node was configured the same queue
in broker.xml file.
Producer A sends a message(with selector) to the node A. Consumer A connect
to node A and consume message with selector (node = a), Consumer B connect
to node B and consume message with selector (nod
Using an out-the-box installation of
jboss-fuse-pre-patched-6.2.0.redhat-143-p1 message sent to Topics are not
always delivered. Everything worked fine for a couple of weeks. Then this
error started happening. In one particular instance, the management console
showed 4 topics related to my topic -
Hi Tim,
thank you for your replay and your very thoughtful questions.
>But are you sure you need to? Are you sure this isn't a premature [...]
I think so. The central broker is on our server farm and it is very
resourceful machine; anyway it often uses a lot of cpu. The broker uses
thousands of
I'm trying to update to AMQ CPP 3.9.0.
The calls to the consumer receive() and receiveNoWait() will not return.
There are messages available on the queue. Older version 2.4.4 worked.
Anybody have any thoughts on this?
Thanks!
Steve
--
View this message in context:
http://activemq.2283324.n
Hello all,
I am facing an issue, which seems to be a regression from my point of view,
but I'd like to know your opinion about this problem... here it is...
We are using ActiveMQ to send a message on queue, which is quite simple:
cf = (javax.jms.ConnectionFactory)
So the logs pretty clearly say that the broker shut down because the broker
lost the JDBC lock (because it couldn't talk to the database) and that it
failed to restart a little later because it still couldn't talk to the
database.
When the database has failed over and ActiveMQ fails to reconnect,
11 matches
Mail list logo
