Re: ajax delivery frequently gets delayed or stalled for 25 seconds in activemq 5.3

Hi Alex, thanks for this thorough testing of new refactored Ajax API. I'm very glad it works better then the old one. ActiveMQ 5.4.0 should be released soon and all releases from that point on will include this new implementation. There will be no more 5.3.x releases, so the old implementation

Re: correlation ID on synchronous message

Oh, now I see. I thought 'synchronous' means that a producer send only one message in order not to disorder a request. I also didn't think synchronous producer in MOM can send multiple requests simultaneously because of misunderstanding the sequence of messages should be ordered strictly.

Set ClientID - InvalidClientIDException

Hi all, I have a client that do a durable subscriptio to a topic. It register with a static client id. After a connectivity loss (an so a new re-connection), this exception is thrown and connection cannot be re-established: 2010-07-15 13:49:04,700 ERROR - javax.jms.InvalidClientIDException:

Re: Set ClientID - InvalidClientIDException

If you use the failover: protocol, the reconnect will be transparent and the broker will be aware of the possibility of a duplicate and suppress that exception. Otherwise you will need to backoff the reconnect till the broker has a chance to recognise and deal with the disconnect On 15 July 2010

Re: Set ClientID - InvalidClientIDException

Thank you very much. I'll try failover mecanism. After some tests I see that the code that I have written works correctly with tcp:// but the above problem only occurs in http:// or in https:// mode. It could be a bug? Gary Tully wrote: If you use the failover: protocol, the reconnect will

Re: Set ClientID - InvalidClientIDException

And also. If I kill all the clients an I leave active only the broker, If I try to reconnect using http (or tcp) I get the same error. So client is not de-registered. This appens also if I use failover protocol. After client kill/restart. Same exception is raised

localhost/tmp_storage is created even if KahaDB is used

Hi, I am using ActiveMQ 5.3.2 on Sun JDK 1.6.20 on Linux. localhost/tmp_storage directory structure is created in the directory specified by dataDirectory parameter to broker tag, even if KahaDB is used as a persistence adapter. This directory structure seems to be part of AMQ Message Store

Re: destroyApplicationContextOnStop parameter semantics

Hi Vjaceslavs, this parameter instructs the broker that when it shuts down it try to stop surrounding application context. This is helpful when embedding broker in various environments like OSGi container or Spring app, so it's not much of a concern if you're running it standalone. BTW. I've put

Re: localhost/tmp_storage is created even if KahaDB is used

This is something that has been resolved for 5.4, the temp store is now using kahaDB, in 5.3.x the temp store used the AMQ store irrespective of the persistence adapter. On 15 July 2010 15:12, Vjaceslavs Klimovs vklim...@gmail.com wrote: Hi, I am using ActiveMQ 5.3.2 on Sun JDK 1.6.20 on Linux.

Why do MirroredQueues not work with virtualDestinations?

I wrote the following directions into activemq.xml When I omit the inner virtualDestinationInterceptor then the incming msgs are mirrored successfully as intended to the Topic myqueue22.qmirror But when I want to forward them from this Topic into a second queue myqueue22_log everything fails.

BrokerService stop not closing out everything?

I'm using an embedded Broker in a Spring application context. When the context is destroyed, the broker is stopped (I can confirm this by the broker's logging output), however, unless I kill the jvm instance, the broker never releases it's lock on the persistence directory or unbinds from the tcp

Re: [AMQ-CPP] Issues with 3.2.1

Hi, Have you tried upgrading your gcc in the centos and debian machines? This would keep a consisting environment so that we can rule out that possible root of problems? Regards On 16 July 2010 11:49, Romain CHANU romainch...@gmail.com wrote: Hi, I am currently upgrading my client from