The announcement states "The main goal of this release was Java 7
compatibility", is that to say ActiveMQ 5.6.0 was NOT compatible with Java
7??? We have been running it under Java 7 for a bit and haven't noticed
any problems, but I'd hate to find out there was a monster around the
corner!
(*Chr
I would try commenting out the original PropertyPlaceholderConfigurer, they
might be clashing and from what I understand you can put all the
non-encrypted values you want in your credentials-enc.properties file,
they'll work just fine. The example I found seems to have a few more
parameters for th
The problem is that you're duplicating functionality. The shared database
means that the two brokers share the information they are receiving by
placing it in a shared location, i.e. the database. The Network of Brokers
is a different way of sharing the information between the brokers, by
transmi
At least from what I'm seeing in *ActiveMQ in Action*, that looks right.
Could it be that your maxRecoveryAttempts=1 is preventing it from
recovering the second time? (I'm fairly new to this myself)
(*Chris*)
On Wed, Aug 22, 2012 at 10:32 AM, joesan wrote:
> I'm happy to see some help at las
That's not a network of brokers, it's a single broker with a failover. For
a network of brokers you would need multiple databases.
(*Chris*)
On Wed, Aug 22, 2012 at 9:28 AM, joesan wrote:
> I"m trying to understand the concept behind the network of brokers in
> ActiveMQ. What I understand fro
What is the connection URL you are using on your clients?
(*Chris*)
On Wed, Aug 22, 2012 at 12:16 AM, joesan wrote:
> Any help friends?
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-Clustering-Issue-tp4655306p4655410.html
> Sent from the ActiveMQ -
You appear to be missing the required slf4j-api-1.6.4.jar dependency.
(*Chris*)
On Tue, Aug 21, 2012 at 2:33 PM, offbyone wrote:
> When trying to start a broker I get this error on brokerService.start():
>
> BrokerService brokerService = new BrokerService();
> brokerService.setPersistent(false
h wrote:
> On Tue, 2012-07-31 at 13:04 -0700, Chris Pratt wrote:
> > Is the URL parameter nonBlockingRedelivery=true,
> > jms.nonBlockingRedelivery=true,
> > jms.redeliveryPolicy.nonBlockingRedelivery=true, or something else
> entirely?
> > (*Chris*)
> >
>
t; see: https://issues.apache.org/jira/browse/AMQ-3894
>
> The implementation in 5.6 is configured on a connection factory as it
> augments the existing redelivery policy:
> https://issues.apache.org/jira/browse/AMQ-1853
>
> On 30 July 2012 21:02, Chris Pratt wrote:
> > Is it
Is it possible to configure the new ActiveMQ 5.6 Non-Blocking Redelivery in
the Broker itself? Or can it only be done in the ConnectionFactory on the
client? If it is possible, does anyone have a short example of a proper
activemq.xml that might show me how to achieve this? Thanks.
(*Chris*)
10 matches
Mail list logo
