Did not work on my 4.1.1 drop, so it does indeed appear to be a bug with 4.1.
Joe ttmdev wrote: > > I am using a recent 5.0 SNAPSHOT and just for grins decided to give your > test a whirl. I followed your steps 1 thru 9 and AMQ worked as it should. > No problema! > > If time allows, I'll give 4.1.1 a whirl today and see what happens. > > Regards, > Joe > > > dantelope wrote: >> >> I'm going to go ahead and say this a defect in 4.1 Virtual Topics appear >> to have lost the expected functionality of permanent registration -- that >> is, it fails the rule "once I register, give me all messages sent to the >> topic until I unregister". >> >> I would love to be proved wrong because we truly need the ability to >> scale consumers by competing for messages on the queue, but if the broker >> goes down and we lose messages until we re-register then something is >> wrong. I shouldn't have to statically define every single client queue. >> That's not how it works in durable subscriptions, and it's not how it >> should work in virtual topics. >> >> Does anyone have a test that counters this? >> >> >> James.Strachan wrote: >>> >>> On 24/09/2007, dantelope <[EMAIL PROTECTED]> wrote: >>>> >>>> The following test produces unexpected results: >>>> >>>> 1) Start a broker with a statically defined destination topic called >>>> VirtualTopic.FOO >>>> 2) Start a consumer listening to Consumer.A.VirtualTopic.FOO >>>> 3) Start a sender and send N messages to VirtualTopic.FOO >>>> 4) Consumer correctly receives N messages. >>>> 5) Kill the consumer process >>>> 6) Stop the broker >>>> 7) Start the broker >>>> 8) Start a sender and send N messages to VirtualTopic.FOO >>>> 9) Start a consumer listening to Consumer.A.VirtualTopic.FOO >>>> >>>> FAIL: the consumer does not receive N messages as expected. >>>> >>>> If I put messages on the topic before stopping the server, then the >>>> consumer >>>> WILL receive the messages on start up. >>>> >>>> Is this my misunderstanding of how Virtual Topics should work, or is >>>> this a >>>> defect I should report? >>> >>> Are you sending the messages using persistent mode? >>> http://activemq.apache.org/what-is-the-difference-between-persistent-and-non-persistent-delivery.html >>> >>> If not then its expected behaviour. >>> >>> Note that to re-enable the consumer each time you need to start the >>> consumer on startup of the broker or add the >>> Consumer.A.VirtualTopic.FOO queue to the startup destinations. >>> >>> http://activemq.apache.org/configure-startup-destinations.html >>> -- >>> James >>> ------- >>> http://macstrac.blogspot.com/ >>> >>> Open Source SOA >>> http://open.iona.com >>> >>> >> >> > > -- View this message in context: http://www.nabble.com/Virtual-Topic-not-working-as-expected---defect%2C-or-misunderstanding--tf4511392s2354.html#a12908113 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
