I have been running in to this problem and need some help. Here is my
configuration
Client 1 (Producer) -> Broker 1
Client 2 (Consumer) -> Broker 2
The producer keeps producing the messages and the consumer consumes certain
number of messages and then stops. There aren't any other cons
You can see what options are available to you on the configuration page
http://activemq.apache.org/cms/configuring.html
As you can see the only protocol option right now is TCP.
Regards
Tim.
http://activemq.apache.org/cms/configuring.html
On Fri, 2007-10-19 at 12:15 -0700, appi03 wrote:
> well
well that will do it.
Okay i have to ask this question? where can i find out what features are
supported by the cpp client.
tabish121 wrote:
>
> The CPP client doesn't support discovery.
>
> Regards
> Tim
>
> On Fri, 2007-10-19 at 11:10 -0700, appi03 wrote:
>>
>> I am trying to use the m
The CPP client doesn't support discovery.
Regards
Tim
On Fri, 2007-10-19 at 11:10 -0700, appi03 wrote:
>
> I am trying to use the multicast discovery protocol and having some trouble
> with it. I think i have the broker configuration down.
>
> Client 1 (Producer) -> Broker 1
> discoveryUri="mu
I am trying to use the multicast discovery protocol and having some trouble
with it. I think i have the broker configuration down.
Client 1 (Producer) -> Broker 1
Client 2 (Consumer) -> Broker 2
But I am not sure how to configure the client side. this is what I have.
Client 1
st
Hey folks,
i am still struggling with the auto-failover feature of brokers in a broker
network.
Consider that i have two brokers, each of them connected to the other like
this over SSL:
Works like a charm.
Now consider that i have one Broker - called A - connected to a Cluste
Apparently this issue has been resolved in 5.0.0.4-fuse.
Regards,
Roger
--
View this message in context:
http://www.nabble.com/reconnection-to-unavailable-broker-causing-thread-memory-leak-tf4603206s2354.html#a13298013
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
yea i am using failover. I did some more work on it.
So my producer keeps producing messages. the consumer application on a
different machine consumes certain number of messages and stops. Once the
consumer application exits, the brokers also loose connection.
I am thinking that only the connec
I have two brokers configured to use the static transport on two different
machines.
I have producers sending messages on each of the machines sending messages
to specific topics to the local broker.
Also, I have consumers that are configured to recieve messages on each of
these boxes as follows
I have a queueSession that is a singleton for my application on server A.
This queueSession is set at startup. When I start up my application,
activemq is up : my application can send messages. I stop activemq : the
messages are dropped. But when I restart activemq, my application can't send
messa
Yep, that's the normal behavior.
The A servers are probably failing to connect before the B brokers are
started. With the parameters you set, and starting A servers before B
brokers, it's bound to fail...
Try increasing maxReconnectAttempts and maxReconnectDelay parameters,
so there's enoug
OK, it was my mistake, i set a boolean to late...
Now, I have the following configuration :
failover://(tcp://B1:61616,tcp://B2:62626)?maxReconnectAttempts=1&maxReconnectDelay=100
But when I restart my activemq server, my A servers cannot reconnect to it.
When I send a message, I have : javax.jm
I set the maxReconnectAttempts to 1 and it is trying to reconnect endlessly.
And it can't connect to the B servers, even if they are up.
Eduardo Corral wrote:
>
> Hi Delphine
>
> Have you checked the log files? Maybe the clients (A1, A2,...) do follow
> the timeout parameter, but they are try
Ok folks,
i finally solved it like this:
Broker:
First you have to enable JMX in the broker itself in the
$AMQ_HOME/conf/activemq.xml:
http://activemq.org/config/1.0"; brokerName="localhost"
useJmx="true">
and
JVM:
Now you have to enable JMX in the JVM parameters in $AMQ_HOME/bin/a
Hi Delphine
Have you checked the log files? Maybe the clients (A1, A2,...) do follow
the timeout parameter, but they are trying to reconnect endlessly...
http://activemq.apache.org/failover-transport-reference.html
With failover, you may also configure how long between retries and how
many o
Hello,
I have some servers A1, A2, AN, ... that send messages on a queue on servers
B1 ans B2. I configured my A servers to connect with the following URI :
failover:(tcp://B1:61616,tcpB2:62626). But when activemq is stopped on both
B1 and B2, my servers A wait a long time before deciding that B1
James.Strachan wrote:
>
> To attach different policies to destinations :)
>
> On 18/10/2007, ivanrc <[EMAIL PROTECTED]> wrote:
>>
>> Hi,
>>
>> Is DestinationPolicy for durable or Non-durable Consumers or both?
>
> Is for destinations, not for consumers.
>
>
>> I have got this in my config
I have now opened an issue for this:
https://issues.apache.org/activemq/browse/AMQ-1470
Regards,
--
Aaron Digulla
--
View this message in context:
http://www.nabble.com/Reliably-starting-and-stopping-of-a-producer-consumer-tf4600635s2354.html#a13292366
Sent from the ActiveMQ - User mailing li
Hey folks,
sorry for providing such poor information.
Here is precisely what i do:
I follow the instructions provided by the AMQ-website here:
http://activemq.apache.org/jmx.html
The relevant section is at the end of the page and called Advanced JMX
Configuration.
According to the page, i di
Are you using failover?
http://activemq.apache.org/how-can-i-support-auto-reconnection.html
On 18/10/2007, appi03 <[EMAIL PROTECTED]> wrote:
>
> I am learning about ActiveMQ and just started using it this week. So I am in
> the preliminary stages but I was wondering if someone can answer this
> q
To attach different policies to destinations :)
On 18/10/2007, ivanrc <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> Is DestinationPolicy for durable or Non-durable Consumers or both?
Is for destinations, not for consumers.
> I have got this in my config file but neither
> timedSubscriptionRecoveryPo
21 matches
Mail list logo