[jboss-jira] [JBoss JIRA] Commented: (JGRP-1119) TCP can cause memory usage when connecting to a non-JGroups service

[Bela Ban (JIRA)]

    [ https://jira.jboss.org/jira/browse/JGRP-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12528210#action_12528210 ] 

Bela Ban commented on JGRP-1119:
--------------------------------

Actually, I can't do this !

TCPConnectionMap is *generic*, and a send() doesn't need to ship a version number, so a read() cannot depend on it ! Reverting this change...

> TCP can cause memory usage when connecting to a non-JGroups service
> -------------------------------------------------------------------
>
>                 Key: JGRP-1119
>                 URL: https://jira.jboss.org/jira/browse/JGRP-1119
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.4.7
>            Reporter: Dennis Reed
>            Assignee: Bela Ban
>             Fix For: 2.10
>
>
> JGroups does not verify that it is connecting to a JGroups service before using the data returned.
> If it connects to another service (for example if another service is found in TCPPING's scan), it reads the first four bytes, uses it as the size of a buffer, and blocks until it fills the buffer with data (or the server kills the connection).
> The symptoms are the same as JGRP-1116.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira