[
https://issues.jboss.org/browse/JGRP-718?page=com.atlassian.jira.plugin.s...
]
Bela Ban updated JGRP-718:
--------------------------
Fix Version/s: 3.6.8
(was: Future)
We also send a cookie, plus the length, so unless both match, the mesage won't ever be
read and will be discarded right away. If it does match, then an OOME will ensure, will
causes the msg to be discarded as well, and the next message will be read (or the conn
closed).
Transport: limit number of bytes read
-------------------------------------
Key: JGRP-718
URL:
https://issues.jboss.org/browse/JGRP-718
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Vladimir Blagojevic
Priority: Minor
Fix For: 3.6.8
In the transport, each message is prefixed with its length. If, on the receiver side, we
receive garbage data (e.g. a random app connects to the same port), then JGroups tries to
interpret the first 4 bytes as length, and this might be quite huge (1.6GB in one
instance).
If we know that our packets are never larger than 200'000 bytes, then we can set a
flag discard_messages_larger_than="200000". If the flag is 0, no messages will
be discarded.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)