activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Davies (JIRA)" <>
Subject [jira] Commented: (AMQ-845) Sending messages to a topic with an inactive durable subscription will hang producers
Date Sun, 03 Sep 2006 17:37:23 GMT
    [ ] 
Rob Davies commented on AMQ-845:

currently working a solution to this

> Sending messages to a topic with an inactive durable subscription will hang producers
> -------------------------------------------------------------------------------------
>                 Key: AMQ-845
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 4.0.1
>         Environment: Linux Red Hat Enterprise 4
> java jdk 1.4.2-b28  (or 1.5.0_06-b05)
>            Reporter: Christopher Mihaly
>         Assigned To: Rob Davies
>            Priority: Blocker
>         Attachments:
> If you have a durable subsciber that is not on-line, and you have producers sending message,
eventually the server will hang on that topic.
> I have attached a zip file with a junit test case and my activemq configuration.  The
test case has two tests, one that creates a durable subscription, that will succeed, and a
second that starts publishing up to 100000 events, which will hang.  I don't really know how
to interrupt the all, so the test case never finishes.  Anyway, it does show the problem and
is 100% repeatable on my system.
> The config file is set to use a SQLServer database, but the stock journal or a derby
persistence manager will do the same thing.  I just switched to mssql server because I can
then see what is going on in the database.  And records are being added to the database all
the way up to when the server hangs. I also doubled the memory manager limit and moved the
jmx rmi port to 1080 since I have another server running at 1099.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message