[jboss-jira] [JBoss JIRA] Commented: (JGRP-1119) TCP can cause memory usage when connecting to a non-JGroups service
[
https://jira.jboss.org/jira/browse/JGRP-1119?page=com.atlassian.jira.plug...
]
Bela Ban commented on JGRP-1119:
--------------------------------
Actually, I cannot reproduce this (with a simple program listening on one of the ports
listed in initial_hosts): when JGroups connects to unknownservice:7800, and unknownservice
is NOT a JGroups members, then the following happens:
- JGroups will create a Connection to unknwownservice:7800
- The read will block
- BasicTCP will destroy the connection to unknownservice:7800 because it is not part of
the view
Hmm, this is for joins, but TCPPING is also used by MERGE2, so what happens when no view
is received ? Then the connection to unknownservice:7800 would linger around until the
next view is received...
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