lost messages

We have experienced a problem during somewhat high load (>500 000 messages over 30 minutes to multiple queues), where 2 messages was both delivered and DLQ’ed, 8 messages was delivered twice and 7 messages disappeared (but then upon inspection 6 of them is present in the AMQ database, somehow

Re: [ANNOUNCE] Apache Artemis 1.4.0 Released

The mirrors just replicate whatever is on the main dist repo. They take a variable amount of time to update, typically several hours or more, as they aren't necessarily on the same update period and their update points are also potentially offset from each other. You can track mirror ages at

Re: [ANNOUNCE] Apache Artemis 1.4.0 Released

Yes, it'll take some amount of time. Not sure how much. As I was browsing manually, I noticed that there are synchronization errors. Most mirrors had the 1.3.0 version and not the 1.4.0 version (as expected). However, the mirror that I found 1.4.0 on did *not* have 1.3.0. That was surprising. Do

Re: [ANNOUNCE] Apache Artemis 1.4.0 Released

I tested before sending the ANNOUNCE, but I guess not all mirrors have it. I believe it usually takes some time before it syncs them all. I guess that's normal? On Tue, Sep 13, 2016 at 4:55 PM, Jim Gomes wrote: > Disregard. There seems to be synchronizing issues between the

Re: [ANNOUNCE] Apache Artemis 1.4.0 Released

Disregard. There seems to be synchronizing issues between the mirrors. Some mirrors have it, some don't. I had to manually browse the mirrors to find one that did. On Tue, Sep 13, 2016 at 1:48 PM Jim Gomes wrote: > The download links are still broken. How long before they

Re: [ANNOUNCE] Apache Artemis 1.4.0 Released

The download links are still broken. How long before they will be active? On Tue, Sep 13, 2016 at 8:40 AM Clebert Suconic wrote: > Apache ActiveMQ Artemis 1.4.0 has been released. > > There are a lot of improvements included in this release: > > - Possibility of

Re: HornetQ to Artemis migration

There's no specific HornetQ-to-Artemis migration guide that I know of. However, much of the configuration is very similar if not exactly the same and, as noted, HornetQ clients should "just work." The only major difference I can think of off the top of my head is with the JNDI implementation.

How to remove a MessageListener

Hello, I have created *DurableSubscribers* for different *topics*. A *MessageListener *has been implemented. Some of these subscribers would like to *unsubscribe *one or more topics. Before they may do so, I need to *remove the MessageListener*. How can I do that ? Thanx for your help. --

HornetQ to Artemis migration

Hi, Is there a HornetQ to Artemis migration guide anywhere? I've looked in the Artemis doc and can't find anything, other than a statement that HornetQ clients will work out-of-the-box, however, I have a full client-server system based on HornetQ that I would like to migrate, and I can't seem

RE: Problem With Remote Debug OF Message Broker

So I've set my breakpoint in the wrong function of the wrong class? Michael Tarullo Contractor (Engility Corp) Software Engineer FAA WJH Technical Center (609)485-5294 -Original Message- From: tbai...@gmail.com [mailto:tbai...@gmail.com] On Behalf Of Tim Bain Sent: Tuesday, September

[ANNOUNCE] Apache Artemis 1.4.0 Released

Apache ActiveMQ Artemis 1.4.0 has been released. There are a lot of improvements included in this release: - Possibility of using a max size for paging, and monitoring disk sizes and improving flow control - Interceptors support for MQTT - Reload configuration support The artemis sub-project

Re: Problem With Remote Debug OF Message Broker

I would expect start() to be called when the broker starts (hence the name) not when a client connects. If you really want to debug that method, there is an option you can set on the debug port that prevents the application from running until a debugger attaches. You can find nore details via

Re: Do I need to reconnect upon exception from receive()

On 09/13/2016 10:21 AM, Andrzej K wrote: Hi Everyone, I have a problem with CMS Client, and I am not able to figure out from the documentation what state the connection and session objects are left in after I got an exception from MessageConsumer::receive(). I have an open connection and a

Do I need to reconnect upon exception from receive()

Hi Everyone, I have a problem with CMS Client, and I am not able to figure out from the documentation what state the connection and session objects are left in after I got an exception from MessageConsumer::receive(). I have an open connection and a session. I call MessageConsumer::receive() on my

Problem With Remote Debug OF Message Broker

I have been assigned to track down a problem that requires debugging of the message broker. For this particular situation we are running version 5.5.1 of ActiveMQ. I downloaded the source code for version 5.5.1 of ActiveMQ and imported it into an Eclipse project I created for this purpose. I

Re: Secure broker and web console: Cannot send to queue

but this is not an option in my case, because this solution let anyone connect to your broker as admin/admin as well. Alejandro Haro Javascript Developer e-mail:

failover broker reconnection delay

Hello, I have this scenario: 2 broker active configured in cluster, a client c++ tha is connected to the brokers using failover protocol. The options in activemq.xml on brokers side are: while on client side option are:

Re: A consumer has same clientid with broker

Thanks. You are right. -- View this message in context: http://activemq.2283324.n4.nabble.com/A-consumer-has-same-clientid-with-broker-tp4716290p4716460.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.