Apologize if this is a re-post...
From: Joe Smith
Subject: Broker forwards msg only once or twice then msg stuck in queue.
To: users@activemq.apache.org
Date: Friday, June 24, 2011, 2:53 AM
Hi,
We have a cluster of 4 brokers (A, B, C, D). The test scenario is for one
produce connected to brok
A type in my original post:
For masterConnectorURI, I am using tcp://localhost:61616
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Junit-Testing-Master-Slave-Program-Hangs-forever-tp3623477p3623481.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
For Junit testing failover , I want to start Master/slave instances with
following piece of code. After Master starts, it hangs forever. If I make
waitForSlave=true, seems to be working. But I want to test it with wait for
slave on..Pls. help.
LOG
-
INFO [main] - Refreshing
org.apache.xbean.
for producers, we can use non -persistent sending mode by the following
code,
producer.setDeliveryMode(DeliveryMode.NON_PERSISTENT);
How to configure this persistent or non-persistent mode through a URI
configuration, and can I configure this feature not only for client and
broker connection b
Hi, I am using ActiveMQ 5.5.0 with NMS.
I want to make a reliable system and confirm that every message is
processed. I want to check that if I don't acknowledge the message it will
be redelivered again. I want to explicitely acknowldge every message so I
have picked Individual acknowledge mode. I
Thanks Dejan, Gary - I still can't get fatal Spring errors logging as the
context startup code doesn't use normal logging. I'm sure there is a good
reason for this though and I can modify the shell script too so shouldn't be
a problem.
Regards,
Tom
On Fri, Jun 24, 2011 at 1:38 PM, Dejan Bosanac
BTW. you need to set trashold for the console logger to debug as well
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
-
The experts in open source integration and messaging - http://fusesource.com
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale
./activemq console
with that flag it will run in the foreground and output to the console.
On 24 June 2011 09:46, Tom <808...@gmail.com> wrote:
> On 23 Jun 2011 12:41, "Dejan Bosanac" wrote:
>>
>> Sure, ActiveMQ uses Spring to load the configuration, so just set
>> "org.springframework" log
Hey,
Since I've updated to "Activemq 5.5.0" and my client software to
"ActiveMQ-CPP 3.4.0" I'm getting this error in my activemq.log now and then:
Does anybody knows if this is a bad error? How can I prevent this?
Thx in advance.
2011-06-24 09:40:00,784 | WARN |
org.apache.activemq.bro
On 23 Jun 2011 12:41, "Dejan Bosanac" wrote:
>
> Sure, ActiveMQ uses Spring to load the configuration, so just set
> "org.springframework" logger to desired level.
That's what I am saying though - I have everything at DEBUG and still don't
see any logging. It seems that Spring Exceptions bubble up
Can you create a test case to reproduce this?
You can take a look at
https://fisheye6.atlassian.com/browse/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/usecases/ThreeBrokerQueueNetworkTest.java?hb=true
for a way on how to create such a test
Regards
--
Dejan Bosanac - http://t
When you create a connection using the ActiveMQConnectionFactory, cast
it to an ActiveMQConnection:
ActiveMQConnectionFactory factory = new
ActiveMQConnectionFactory(brokerUrl);
ActiveMQConnection conn = (ActiveMQConnection) factory.createConnection();
And let your TransportListener implement
Thanks for the replies.
The reason we have redundant clients is to survive hardware crash as both
broker and client reside on the same machine.
We keep the Client 2 live to just keep trying for connection to slave until
master goes down. Once slave becomes master, it gets connection and starts
pr
13 matches
Mail list logo
