[jira] Commented: (AMQ-1068) DestinationMap seems to use up lots of RAM if using deep hierarchies

[ https://issues.apache.org/activemq/browse/AMQ-1068?page=comments#action_37564 ] james strachan commented on AMQ-1068: - The fix was done in r478324 on trunk if folks wanna backport DestinationMap seems to use up lots of RAM if using deep

communicating with Topic subscribers from custom interceptor class

Hello, Thanks for your great work on ActiveMQ! I'm writing a custom interceptor that extends BrokerFilter in order to process messages that are published to particular Topics. My question is, how can my interceptor make a direct connection with the JMS client that published the message?

Re: Message Expiry

Hi, I've tried your code. It worked. But then I substituted synch .receive() with asynch MessageListener, which I register after the same timeout. And surprise! The message arrives. But it still shouldn't, right? Let me post here my code: ConnectionFactory connectionFactory =

ActiveMQ-CPP 1.0 released

Hey everyone, We have an official release of ActiveMQ-CPP 1.0! You can go to the release page here: http://www.activemq.org/site/activemq-cpp-10-release.html . And the main ActiveMQ-CPP page has been updated as well: http://www.activemq.org/site/activemq-c-clients.html Thanks to everyone that

Re: ActiveMQ-CPP 1.0 released

On 11/27/06, Nathan Mittler [EMAIL PROTECTED] wrote: Hey everyone, We have an official release of ActiveMQ-CPP 1.0! You can go to the release page here: http://www.activemq.org/site/activemq-cpp-10-release.html . And the main ActiveMQ-CPP page has been updated as well:

Re: Message Expiry

hi Sergey, This does look like a bug. You can monitor the progress of this issue at https://issues.apache.org/activemq/browse/AMQ-1072. Regards, Jonas Sergey wrote: Hi, I've tried your code. It worked. But then I substituted synch .receive() with asynch MessageListener, which I register