2 Replies Latest reply on Nov 15, 2007 1:14 AM by Robert Davies

    Early experiences with FUSE 5.0.0.4

    Ian Beaumont Newbie

      We have our own application server that uses queuing as it's backbone.  We currently support a number of queue providers (such as MQSeries).  I evaulated ActiveMQ 4.0 a long time back and found the reliability and performance poor.  With the release of 5.0 I thought I'd give it another go.

       

      Configuring ActiveMQ I found straightforward and easy (once I remembered to remove the old activeMQ jars from my class path!).

       

      In my test case I have a message producer that reads a message from a queue and then queues 100 new messages in the same transaction.  Each of those 100 messages is then read off the queue by a number of consumes (all within the same application).  What I'm finding is there seems to be some sort of hanging/deadlock issue.  Each time the test is run, the system hangs after processing a number of messages and no more messages get processed.

       

      I often get many messages like the following in the broker and the webconsole reports a negative number of messages on the queue.:

      2007-11-14 13:55:07,710 /127.0.0.1:3855 ERROR RecoveryListenerAdapter        - Message id ID:IAN-LAPTOP-3275-1195047220687-0:0:1:2:47 could not be recovered from the data store!

       

      As for performance - I can't get it to process messages long enough to actually measure the performance.

       

      Hopefully I'll get some time at some point to try to reproduce the problem in a simple test case but there is a lot of code that I'd need to go through to achieve this.

       

      Would be interested in other peoples experiences - am I just missing some configuration option?

       

      Ian

        • 1. Re: Early experiences with FUSE 5.0.0.4
          Bruce Snyder Novice

          In my test case I have a message producer that reads a message from a queue and then queues 100 new messages in the same transaction. Each of those

          100 messages is then read off the queue by a number of consumes (all within the same application). What I'm finding is there seems to be some sort of

          hanging/deadlock issue. Each time the test is run, the system hangs after processing a number of messages and no more messages get processed.

           

          Are you using the same connection for both the consumer and the producer? If so, there is a possibility of deadlock here. If the producer is blocked waiting for space in the broker, then the connection will block, therefore blocking the consumer. Make sure that each is using a separate connection to the broker.

           

          Bruce

          • 2. Re: Early experiences with FUSE 5.0.0.4
            Robert Davies Newbie

            Hi Ian,

             

            You've stumbled across an issue thats fixed with the FUSE Message Broker 5.0.0.5 release that will be released on Monday 19th November.

             

            thanks,

             

            Rob Davies