Hello again!
I would be very grateful If someone could answer my questions. We need the
high availability to work to use the broker in production.
When I run the replicated-failback example in one machine (broker3) it
succeeds.
It fails when I run the same test - exactly the same servers with sl
Im not on my computer now but it sounds like you are doing a fail back
immediately after failed over. It takes some time (seconds) to the server to
activate on the backup.
Later the server will need to copy the data back before it can be activated in
fail back mode.
It sounds the live is not
How can I report this as a bug?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/JDBC-driver-with-Failover-Master-Slave-MS-SQL-database-tp4702654p4703098.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
I think we're having an issue with prefetch and some of our customers
stealing work and then sitting on it while other threads starve.
Is there a way to trace/listen the prefetch system on the clients?
Alternatively, a way to see the timestamp that a JMS message was
prefetched. This way I can di
Actually.. I should be able to use JMSActiveMQBrokerOutTime... so nevermind
;)
On Sun, Oct 18, 2015 at 8:48 AM, Kevin Burton wrote:
> I think we're having an issue with prefetch and some of our customers
> stealing work and then sitting on it while other threads starve.
>
> Is there a way to tra
Looks like both of these properties aren't changed on redelivery.
Which kind of makes them less valuable. In my situation I think I can only
really use them when the delivery count is 1. Better than nothing
though...
--
We’re hiring if you know of any awesome Java Devops or Linux Operations
En
Bug reports get submitted in JIRA:
https://issues.apache.org/jira/browse/AMQ/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
With that being said, your original description said that "the AMQ service
goes down for some reason". I've never seen ActiveMQ go down without
logging, o
I'm pretty sure the JMS spec describes how JMSTimestamp is handled, so
there's no flexibility there. I'm not sure what value you'd want to use in
a redelivery situation, anyway, since the message isn't being created.
Would you want it to be the timestamp when the broker decided to redeliver
the me
Tim Bain wrote
> When I Googled for how to set the JMX port of an embedded broker, here's
> what I found: broker.getManagementContext().setConnectorPort();
Hint taken. I did google for this, but didn't get past the hits to the
activemq site to find
http://stackoverflow.com/questions/6521898/ho