activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Kaitchuck (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-845) Sending messages to a topic with an inactive durable subscription will hang producers
Date Mon, 22 Jan 2007 21:15:02 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tom Kaitchuck updated AMQ-845:
------------------------------

    Attachment: patch.txt

I ment to add this file a while back and forgot, so it may be a little out of date, but it
is a much better solution.

> Sending messages to a topic with an inactive durable subscription will hang producers
> -------------------------------------------------------------------------------------
>
>                 Key: AMQ-845
>                 URL: https://issues.apache.org/activemq/browse/AMQ-845
>             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
>             Fix For: 4.2.0
>
>         Attachments: patch.txt, testcase.zip
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message