Improved concurrency for sendMessage

[glassfishrobot]

RFE related to fix for shoal issue 88 to change that synchronization
solution to a more performant pool of OutputPipes (one pipe to be used by one
thread at any point in time).

Environment

Operating System: All
Platform: All

Affected Versions

[current]

[glassfishrobot]

@glassfishrobot Commented
Reported by @jfialli

[glassfishrobot]

@glassfishrobot Commented
shreedhar_ganapathy said:
Transferring to Joe for eval and closure.

[glassfishrobot]

@glassfishrobot Commented
@jfialli said:
there are trade offs for concurrent sendMessage when relying on NIO as the ultimate transport.
so this RFE was considered and postponed due to these tradeoffs.

The concurrent processing resulted in not being able to share the same deserialized output stream with
all send messages. Thus, there is also a space usage and/or multiple desserializations necessary for
each concurrent send.

With regular multicast, only one deserialization of the message to be sent was occurring.
With current implementation, there still is only one.

With concurrent send, there were not so obvious tradeoffs.
So this RFE is on hold for now while sorting through the tradeoffs.

[glassfishrobot]

@glassfishrobot Commented
This issue was imported from java.net JIRA SHOAL-89

[glassfishrobot]

• Issue Imported From: https://github.com/javaee/shoal/issues/89
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @jfialli