Hi all,
We've got yesterday exception and I'd want to know what can cause it and
what is the impact of it
- was it called after message processing?
- was it removed fro queue if we use JMS transaction?
version of AMQ we use is 4.1.1 and operations says that more likely it was
not processed sinc
Hi all
I'm using network of brokers config with 2 brokers
After some time one of the queues on one broker stopped dispatching messages
to its 2 consumers, log files contained no errors and any kind of strange
behavior, 3 other queues on the same broker were just fine
my config file for brokers is
Hi all
After problems with Master/Slave configuration over MySQL when master broker
hangs up after some time, we decided to switch to the Network of Brokers to
achieve HA
I setup 2 brokers on 61616 and 61716 ports with following configs
http://activemq.org/config/1.0";
dataDirectory="${act
Fixed
use org.springframework.jms.listener.SimpleMessageListenerContainer instead,
Default one just refetches the message in endless loop. Simple one uses
redelivery policy to do that. No idea why default behavior in Spring so
weird
--
View this message in context:
http://www.nabble.com/Redelive
Hi All.
I fased the problem with redelivery policy, it simply does not work for
following config
Factory:
Anthrope wrote:
>
> There is a bug in the 4.1.1 release version of DefaultDatabaseLocker.java.
> The problem is that the result of the execution of the prepared statement
> to lock the database row is being incorrectly interpreted. This link ought
> to explain why:
>
>
This bug exist also in 4
Hi all,
Similar problem :(
I'm new to ActiveMQ so probably I misconfigure it somehow.
Problem: I'm trying to setup jdbcPersistenceAdapter in AMQ 4.1.1 to store
journal into the MySQL 5.0.24 with Connector mysql-connector-java-5.0.4
under Windows XP
My config file is very simple
---
