I am using activemq as my message broker.I use log4j for my logging.my root
logger is error, so any error happens in any part of my code exception stack
trace is logged, except for exceptions from messagelistner, why exception
from message listner are not logged, did anybody face anything like thi
After some further study, it appears i need INDIVIDUAL_ACKNOWLEDGE mode.
However, what is not clear is how or IF the message is re-delivered if
it is not acknowledged.
What is AMQ's behavior in this regard? Does it use the JMS message
timeout before redelivery?
Can someone verify this behav
The main problem here is that it is really hard to repeat.
I am using a network of brokers for large distributed application.
Message loss happens about 2% of total execution times.
That is I execute 100 times of my application, may be 2 times, message lost
could happen.
Do you have any suggest
Yes, it depends on how you acknowledge.
AUTO, Client or Individual (This is an AMQ specific)
Client == On the Session.
On Jun 28, 2011, at 11:43 AM, Darren Govoni wrote:
> Hi,
> I want to allow consumers of a persistent queue to programmatically
> acknowledge
> messages. And after some time,
Hi,
I want to allow consumers of a persistent queue to programmatically
acknowledge
messages. And after some time, if it is not acknowledge, I want the
message re-delivered
elsewhere.
Are there examples of how to do this? Any tips appreciated.
Thanks!
Darren
see http://activemq.apache.org/shared-file-system-master-slave.html
In short, consumers should use the following URLs. If the consumers are
embedded in the brokers, then using VM for the transport appears to work
fine. However, if the broker goes down, so does the consumer (generally)...
Consum
I experience the same problem with redelivery with Individual acknowledgement
mode. I've looked at the example, but every test case uses
Session.AUTO_ACKNOWLEDGE. It raises 2 questions:
1. So, why should Individual acknowledgement mode be used?
2. I don't see where transaction is started... Does i
Producer and Consumer code is here:
https://fisheye6.atlassian.com/browse/~br=trunk/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/demo
Hope you already gone thru this:
http://activemq.apache.org/getting-started.html
ActiveMQ Examples
http://activemq.apache.org/examples.html
Acti
We are implementing AMQ's master/slave broker topology to achieve geographic
redundancy.
Master is hosted on Server A and Slave is hosted on Server B.
For geographic redundancy, we will have two consumer apps which will be
hosted on the same servers. These consumers will consume a Q named
"TEST
ackType=0 is a delivered ack which is used to increase the prefetch
within a transaction or with individual ack but it is not critical.
The error indicates that the broker does not have knowledge of the
dispatch of that message to the consumer, as a result it has no
message to ack. This can occur
there is currently no plan for a 5.5.1. 5.6 in aug/september is the
current target.
On 27 June 2011 17:44, Norman Maurer wrote:
> Do you know if there will be a ActiveMQ 5.5.1 release for AMQ-3276 ?
>
> Bye,
> Norman
>
>
> 2011/6/27 Gary Tully :
>> While AMQ-3276 is ugly, I don't think it can cau
11 matches
Mail list logo