Mailing-List: contact commits-help@river.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@river.apache.org
Date: Wed, 4 May 2011 18:42:03 +0000 (UTC)
From: "Chris Dolan (JIRA)" <jira@apache.org>
To: commits@river.apache.org
Message-ID: 
 <2008369005.22473.1304534523100.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1842984765.22466.1304534283115.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (RIVER-397) Mux.start() can block indefinitely
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Chris Dolan updated RIVER-397:
------------------------------

    Attachment: MuxStartTimeout.java

Test case that fails with current River and passes with the proposed timeout solution applied.

> Mux.start() can block indefinitely
> ----------------------------------
>
>                 Key: RIVER-397
>                 URL: https://issues.apache.org/jira/browse/RIVER-397
>             Project: River
>          Issue Type: Bug
>          Components: net_jini_jeri
>    Affects Versions: jtsk_2.1
>            Reporter: Chris Dolan
>         Attachments: MuxStartTimeout.java, RIVER-397.patch
>
>
> Email thread starting here: http://mail-archives.apache.org/mod_mbox/river-dev/201104.mbox/%3C77F1E32F67C8D5479858C0C7E93EB465068B06CF@WAL-MAIL.global.avidww.com%3E
> In short, I encountered a case where a JERI client got permanently stuck in Mux.start(). Attached is a patch to add a timeout to that method.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira