JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
feature_request_small.png
OPEN  Feature request JPPF-435  -  Remove the limitation to 2 GB message size in communication protocol
Posted Feb 01, 2016 - updated Oct 27, 2016
action_vote_minus_faded.png
0
Votes
action_vote_plus_faded.png
Issue details
  • Type of issue
    Feature request
  • Status
     
    New
  • Assigned to
    Not assigned to anyone
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Core
  • Resolution
    Not determined
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 6.0
Issue description
In the current communication protocol between servers, nodes and clients, a message is made of one or more serialized objects preceded by their serialized size: size1 object1 | ... | sizeN objectN

Each size is expressed as a signed int, which effectively limits the object size to 2 GB. I have seen user situations where that limit was broken, which got us to handle this situation. For instance, when a node returns a task which takes more than 2 GB, the node detects it and returns a special type of task instead, with information on the error.

We propose to express the size as a long instead of an int, which would allow object sizes of up to 2^63 - 1 (around 9.223e18). This should give us some breathing space for the next few years.

Let's not kid ourselves: this will be a huge refactoring effort, which should only be done for a new major version.