activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] Closed: (AMQ-1625) Producers hang when broker is fubar
Date Wed, 08 Jul 2009 13:50:07 GMT

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

Gary Tully closed AMQ-1625.
---------------------------

    Resolution: Incomplete

closing this following comments from reporter. no test code available

> Producers hang when broker is fubar
> -----------------------------------
>
>                 Key: AMQ-1625
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1625
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.1.0
>         Environment: SNAPSHOT build from 1/16/08
>            Reporter: peter royal
>             Fix For: 5.4.0
>
>         Attachments: hung producers.log
>
>
> see attached log.
> in a nutshell,
> Transport.request(Object command) is dangerous, and shouldn't be used.
> Transport.request(Object command, int timeout) should be used instead.
> something happened to my broker (don't know what yet), and it caused the producer to
hang as seen. then since the session is shared, a bunch of other threads blocked as well.
if the request on the transport had a timeout (this is to catch failure scenarios, so something
that's not expected to reasonably happen), things would have errored out rather than building
waiting threads.
> if it is amiable, i can produce a patch that will remove the non-timeout'd version of
Transport.request() and use the version with a timeout everywhere.

-- 
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