activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Parekh (JIRA)" <>
Subject [jira] Created: (AMQ-1209) Producer Blocks even after emptying out queues on v 4.2
Date Mon, 19 Mar 2007 19:35:35 GMT
Producer Blocks even after emptying out queues on v 4.2

                 Key: AMQ-1209
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 4.2.0
         Environment: WinXP SP2
JDK 1.5.0_11
P4 duo core @2.16GHz

            Reporter: Dave Parekh

Using non-peristant JMS queues.

I have downloaded the active mq  distribution
to test the new message cursor functionality.  We are testing the spooling functionality after
running out of RAM buffer. We modified the existing ProducerTool and ConsumerTool examples
that were provided so that we could send messages that are about 80KB in size. We set the
memory in the xml config file to 512Mb.

When we first run the Producer tool to publish 40, 000 messages, it runs fine and publishes
all 40,000 messages. On version 4.1.1, we could only publish out about ~5,000 messages before
being blocked.

After running the Producer tool, we ran the ConsumerTool to read all the messages in the queue.
It successfully read out all 40, 000 messages.

We then re-ran the Publisher tool to publish 40,000 messsages. However, the publisher would
only publish 10 messages and just block.   We assumed then that 10 messages are in the queue.
We ran the Consumer but it would retrieve 0 messages. It acted as if there were no messages
on the queue. Subsequent attempt to run Publisher would only publish out 10 messages while
subsequent attempts to running the Consumer would retreive 0 messages.

Any assistance with this would be greatly appreciated. We are in the process of migrating
off the Sun MQ producer and are looking at some open source alternatives. With the design
of our application, we need functionality analgous to message cursors. Re-designing the application
is not an option.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message