You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "John McClain (JIRA)" <ji...@apache.org> on 2007/11/26 23:19:43 UTC
[jira] Updated: (RIVER-255) Outrigger DestroyThread does not catch
exceptions from exporter.unexport
[ https://issues.apache.org/jira/browse/RIVER-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John McClain updated RIVER-255:
-------------------------------
Fix Version/s: AR2
> Outrigger DestroyThread does not catch exceptions from exporter.unexport
> ------------------------------------------------------------------------
>
> Key: RIVER-255
> URL: https://issues.apache.org/jira/browse/RIVER-255
> Project: River
> Issue Type: Bug
> Components: com_sun_jini_outrigger
> Affects Versions: jtsk_2.0
> Reporter: John McClain
> Assignee: John McClain
> Priority: Trivial
> Fix For: AR2
>
>
> Bugtraq ID [6306598|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6306598]
> Outrigger DestroyThread does not catch Throwables throw by
> exporter.unexport. As a result if unexport throws an exception most of
> the cleanup that is supposed to happen as part of destroy gets
> skipped. While in general "should never happen" the DestroyThread
> generally tries to do its best in the face of Throwables and
> conceptually unexporting is complicated enough that we should probably
> be paranoid.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.