I don't believe the Virtual Topics feature works in 5.1.0, even with a single
broker.
carbon60 wrote:
>
> I should add that this is ActiveMQ 5.1.0, Spring 2.5.5.
>
--
View this message in context:
http://www.nabble.com/Virtual-Topics---Network-of-Brokers-tp19294934p19342118.html
Sent from t
there has been no update there.
carbon60 wrote:
>
> Did you ever make any progress on this issue Alan?
>
> A.
>
>
> alanmc wrote:
>>
>> Hey Guys,
>> A simple "this is a known issue we're working on" or a "We no longer
>> suppor
Hey Guys,
A simple "this is a known issue we're working on" or a "We no longer support
Virtual Topics" would be greatly appreciated.
alanmc wrote:
>
> Looks like there's an open JIRA for this issue:
> https://issues.apache.org/activemq/browse/AMQ-1763
Looks like there's an open JIRA for this issue:
https://issues.apache.org/activemq/browse/AMQ-1763 but that hasn't been
touched since it was created. Does anyone know what's going on here? Is
the Virtual Topic feature basically unusable in the 5.1.0 broker?
--
View this message in context:
htt
Hey all,
I've been trying to use Virtual Topics but keep running into this problem.
I have a service that broadcasts messages about its state on a VirtualTopic
and I'm trying to consume those messages from another service. The setup
actually seems to work initially, but after a while the broker
Thanks Tim,
Looking over things it seems like establishing a network of brokers is
orthogonal to the transport specified by the client. A client can specify
one or many (a static list via "static:" or a randomized list via
"failover:") brokers to connect to and the fact that that broker may be
fo
We are using ActiveMQ-CPP to build a massively scalable SOA and have been
happy with the product so far, however CMS is missing some key features,
namely Failover and Discovery. Those two features seem to be necessary for
delivering production-quality components using CMS. Are those features
act
Sorry for the long delay responding. I resolved this issue, it was a bug in
our client code. A temporary queue was being cleaned up too early.
rajdavies wrote:
>
> Are you using networks as well ?
>
> On 22 Apr 2008, at 04:01, alanmc wrote:
>
>>
>> We're see
We're seeing the same behavior with 5.1.0. We're basically running the
default broker configuration, with advisory support turned off. We were
using 5.0.0, but saw memory leakage and wanted to try out 5.1.0 and after
switching over with the exact same configuration we started seeing
intermittent
