activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Filip Hanik (JIRA)" <>
Subject [jira] Commented: (AMQ-1557) High message frequency causes ActiveMQ to freeze
Date Tue, 29 Apr 2008 18:31:43 GMT


Filip Hanik commented on AMQ-1557:

If I reconfigure the dead letter strategy
              <sharedDeadLetterStrategy processExpired="false" processNonPersistent="false"

and turn off the flooding of the logs that it causes

The system seems to stay up, in this case, my client (consumer) OOMs, and during the time
it OOMS, the producer freezes up again,
it seems that the producer is synchronized on a connected consumer, and there is no asynchronicity
between the two


> High message frequency causes ActiveMQ to freeze
> ------------------------------------------------
>                 Key: AMQ-1557
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.0.0, 5.1.0
>         Environment: observed on Windows XP Professional SP2, Sun JDK 1.5.01_11, but
probably affects all platforms
>            Reporter: J├╝rgen Schumacher
>            Assignee: Rob Davies
>         Attachments:
> ActiveMQ freezes in a test setup with very high message frequency of persistent messages
and multiple producers and consumers running on multiple machines:
> - Host 1: Multiple Producers send messages very fast to queue1 
> - Host 2: Multiple Processors consume message from queue1 and send a new message for
each consumed message to queue2, also very fast.
> - Host 3: ActiveMQ server and 1 consumer reads messages from queue2.
> With producerFlowControl enabled, the system freezes very soon (a bit more than 1000
> With producerFlowControl disabled, it seems to run longer at first, but it still freezes
> Using transactions or not does not seem to make a difference.
> See this thread in user mailing list for more details:
> See attachment for code of test cases and the batch files to start them.

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

View raw message