I want to download the following activemq versions:
5.3.2
5.4.0
5.4.1
but I get always the ERROR 404. Why I cannot download the old versions of
activemq?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Download-Mirrors-tp3448860p3448860.html
Sent from the ActiveMQ - User
Hi, I upgraded the AMQ to 5.5.0 since I saw a bug on this, however this still
reproduces in another way.
Now, I don't get the error in the AMQ as I wrote of 'Async error' but for some
reason some times after restart, On the client of AMQ I implemented -
Has a problem in the
Public void onMessag
Ah, yup, there it is. Too easy. Thanks for the tip!
Gary Tully wrote:
>
> its on the connection pool, have a peek at the test:
> http://svn.apache.org/viewvc/activemq/trunk/activemq-pool/src/test/java/org/apache/activemq/pool/ConnectionExpiryEvictsFromPoolTest.java?view=markup
>
-
Dan C
I think your URI is having a timeout parameter of 10 sec...take it out, your
SENDing process will reconnect immediately
default value for that is -1, good one.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Pure-Master-Slave-config-Synchronization-of-messages-tp3442845p3
failover:(tcp://master-IP:63616,tcp://slave-1-IP:63616,
tcp://slave-2-IP:63616)?randomize=false
if randamize...after master failure, you can not tell which slave will
startover, if false, it will pick up in sequence, if you have only one
slave...no need of it.
--
View this message in context:
h
Thanks a lot Prasad for the reply.
I made progress after following your tip.
Now, I have one more issue;The client doesn't failover to the slave when
master goes down.
I am using ActiveMQ 5.5. The client URL is:
failover://(tcp://xpw-tkasireddy:61616,tcp://10.1.5.80:61616)?timeout=1
Please
Yes / No...because I am not sure..
I was also getting this Exception but not because of Illegal Argument
Exception, But the Same Async Error Occured...it was because of
javax.jms.JMSException: Unmatched acknowledge: MessageAck {commandId = 2158,
responseRequired = false, ackType = 2, consumerId
Thanks. I did increase my session size to 100. So it cached sessions. The
problem was with Single connection Object. All the threads were trying to
use the same connection. Connection Object uses this Mutex before sending.
So essentially this is a blocker.
java.lang.Thread.State: BLOCKED
Can this exception be the reason for stuck of messages:
Async error occurred: java.lang.IllegalArgumentException: The subscription
does not exist: ID:n11-1681-1159779699684-5:1:1:1
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Messages-stuck-in-queue-tp3244342p3447558
replace "network" with "cluster" or "master/slave pairs" or
"collection" it does not make any difference. The enhancement is that
a connection in a pool will get a chance to be randomized again by the
failover transport.
The relationship between the brokers, if any, is independent.
On 13 April 20
But there a confusion in lernen.2007's previous reply message that he could
reproduce the problem
How can a producer get messages when you shutdown a consumer.
The description of the problem is "When a consumer is active and eagerly
looking for messages, AMQ queues won't deliver messages that we
The link which Gary gave..saying
"It might make sense to restrict the lifetime of connections in a connection
pool, so that once in a while the connection is refreshed providing a chance
of connection load balancing over a network of brokers."
and here the main poster of this message told that h
that is great progress, can you turn that into a junit test case?
In that way it will be obvious what the exact use case is, including
configuration and we can commit the test to protect any changes that
ensue.
There is an existing test case that may provide you with a good
template. If that does
I could reproduce the problem. Following situation:
Producer(Client) Consumer(Server)
NetworkConnector
I shutdown the consumer and the producer get messages further. If I start
the connection between producer and consumer again then at first I see the
followin
its on the connection pool, have a peek at the test:
http://svn.apache.org/viewvc/activemq/trunk/activemq-pool/src/test/java/org/apache/activemq/pool/ConnectionExpiryEvictsFromPoolTest.java?view=markup
On 13 April 2011 11:38, dcheckoway wrote:
> Thanks Gary. That should do the trick! I don't se
Thanks Gary. That should do the trick! I don't see it doc'd on the failover
or tcp transport wiki pages, though. Does expiryTimeout apply to failover:
or tcp:? Sorry to be ignorant about features that have been in there a
while, just haven't run across this one.
-
Dan Checkoway
dcheckoway
have a look at https://issues.apache.org/jira/browse/AMQ-2376, the
expiryTimeout attribute may be what you need as this can be used to
limit the lifetime of a connection in the pool.
On 12 April 2011 20:35, dcheckoway wrote:
> I've got producers set up to randomize to my broker nodes, such as:
>
We tested with activemq version 5.4.2. The message stuck with this version
too. I think a jms provider in which the messages stuck is not useable. The
activemq team should stop to fix another problems and begin to analyse what
the reason for this problem is and deliver a patch as soon as possible.
How does that work - if each broker is standalone then when the producers fail
over they will start communicating with a server with a totally different set
of messages and conversation state, I don't understand how this would work or
be useful?
> -Original Message-
> From: dcheckoway [
19 matches
Mail list logo
