1.Virtualtopic is work fine for single broker . but in the network broker is seems have problem when you create differnce consumer on differce borker and they subscription same virtualtopic
2. Recovery policy problem
1.if you setup this ixedcount recovery policy on you broker and producer send message size >10K then broker will be crush . so it seems this policy not good work with big message
but you change the recovery policy to FixedSizedSubscriptionRecoveryPolicy then it stablity
3.Activemq multicast transferport problem
first time i thought it support multicast send message .not copy message to each consume. but i tested it this multicast is seems uses multicast to find out the broker on network . not for message.
becuase multicast is base on UDP protocol. but the consumer connection broker is still uses TCP .
4. Activemq Retroactive Policy onle support first connection subscription .please refer to web page.
5. if broker is died. the producer can receiver get notify and but consumer only can get exception. and the Listeren thread were still running.(you need to some logic to kill it on you program)
Actually Activemq is not good work for high performance and high throughput messaging . we tested it on 8G MEM 4(CPU) server. message is 10-20k . producer performance 5000/s
(one producer) and consumer performance is same . it's non-persistent.
so we think Activemq is work with durable and persistent message . if you not need high performance and just only it stablily you can ues.
<low latency >
other trade message system
activemq
qpid
persistent
durable
recover HighPerformance