[jboss-jira] [JBoss JIRA] (JGRP-1691) Tunnel socket can be closed allowing for infinite high CPU loop that doesn't realize its closed.

[Bela Ban (JIRA)]

     [ https://issues.jboss.org/browse/JGRP-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bela Ban updated JGRP-1691:
---------------------------

    Priority: Major  (was: Blocker)


Hi Chris,

this may be a blocker for you, but a blocker in JIRA means an issue would have to be fixed before a given version can be released. This is IMO not the case here, as not many people use the TUNNEL/GossipRouter combo, so I'm downgrading the severity to major.
                
> Tunnel socket can be closed allowing for infinite high CPU loop that doesn't realize its closed.
> ------------------------------------------------------------------------------------------------
>
>                 Key: JGRP-1691
>                 URL: https://issues.jboss.org/browse/JGRP-1691
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 3.3.2
>         Environment: Win 2k8, all
>            Reporter: Ben Spink
>            Assignee: Bela Ban
>              Labels: socket, tunnel
>             Fix For: 3.3.6, 3.4
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Socket apparently gets closed after some time...maybe a week or two, and the tunnel doesn't realize tis closed.  Just keeps throwing socket closed exceptions, which are consumed and it checks if the "stub" is closed, tis not, so it loops again, no delay, CPU shoots to 100%.  Server is unusable.
> Tunnel.java line 246, 247, 248.  Needs to catch a socket closed exception and break, not loop.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira