In the following example from
http://activemq.apache.org/failover-transport-reference.html
failover:(tcp://local1:61616,tcp://local2:61616,tcp://remote:61616)?randomize=false&priorityBackup=true&priorityURIs=tcp://local1:61616,tcp://local2:61616
Will local1 always be tried before local2 or is
On 06/10/2016 08:10 AM, Dale Green wrote:
Hi,
Can someone tell me if the ActiveMQ Resource Adapter is supposed to
communicate with an AMQP Broker?
I saw that there is AMQP code in the RA and actually AMQP connection
strings are correctly recognized/parsed, but the RA doesn't want to send
anythi
For JMSToolBox,
(https://sourceforge.net/projects/jmstoolbox/?source=directory), I bundle those
jars and it works:
- activemq-client-5.13.3.jar
- geronimo-j2ee-management_1.1_spec-1.0.1.jar
- hawtbuf-1.11.jar
Denis
Le 2016-06-17 à 09:43, danny a écrit :
Hi,
Which set of jar are needed for a
To save you some time I just ran a quick dependency tree since I had it up
and here is what it listed for 5.13.3:
[INFO]
[INFO] Building ActiveMQ :: Client 5.13.3
[INFO]
---
The link you have is from version 5.8 and the dependencies have changed
since then. Your best bet is to use a tool like Maven or Gradle and to
declare a dependency on activemq-client to build your application so that
it will pull in all of the correct jars needed transitively. The
dependencies ca
Hi,
Which set of jar are needed for a java JMS client application, to connect
to my ActiveMQ server
I have activemq-client-5.13.3.jar, on my class path. but Its not enough, i
get class not found exceptions.
up till now I have made do using activemq-all-5.13.3.jar,
however now the size of
Right, there is no inheritance between policies or merging semantics as Tim
pointed out. So if you define a new policy then you need to re-apply all
the settings you want to the new policy as well.
On Fri, Jun 17, 2016 at 9:09 AM, Johan Carlquist wrote:
> Thanks for your reply.
>
> It had been
On 06/17/2016 06:16 AM, Christian Schneider wrote:
Just wanted to share some positive feedback we got from a customer.
I wrote some time go about a problem we had at a customer that
activemq failover took too long.
In the end the problem was the sheer amount of data in the kahadb
journals.
W
Thanks for your reply.
It had been nice to avoid dublicated queue configuration so we will look
in to make an JIRA enhancement request for this later this
summer.
--
jocar
> On 11 Jun 2016, at 17:43, Tim Bain wrote:
>
> Sorry, I just re-read your description of the behavior and clearly it's n
Just wanted to share some positive feedback we got from a customer.
I wrote some time go about a problem we had at a customer that activemq
failover took too long.
In the end the problem was the sheer amount of data in the kahadb journals.
We found that most of the long term queued data was in
10 matches
Mail list logo
