Fix outdated code references in message passing documentation

[Saurabh16-s]

Description

Updated Message Passing Implementation documentation with current code links (v2.8.7 instead of v0.7.1).

Changes

• Updated all GitHub links from 0.7.1 → v2.8.7
• Replaced Clojure references with current Java file paths
• Changed ZeroMQ references to Netty
• Kept original documentation structure and wording

Related Issues

Closes #7845

[rzo1]

Thx for the PR. The current version is 2.8.7 - any reason for 2.6.7?

[Saurabh16-s]

My bad — I saw v2.6.2 in the issue, so I used that version. I’ll update it to v2.8.7.

[Saurabh16-s]

Updated the documentation to reflect Storm v2.8.7. Please let me know if any further changes are needed.

[rzo1]

Thanks for the update! A few suggestions inline. Main themes: (1) the Disruptor sentence is outdated (2.x uses JCQueue), (2) several links use /blob/ for directories which 404 on GitHub, (3) some link pairs collapse to the same URL — the original doc had distinct line anchors.

[rzo1]

The Disruptor reference is outdated — 2.x replaced it with JCQueue (JCTools), see storm-client/src/jvm/org/apache/storm/utils/JCQueue.java.

Suggested change

	(Note: this walkthrough has been updated for v2.8.7. As of 0.8.0, the message passing infrastructure has been based on the Disruptor)
	(Note: this walkthrough has been updated for v2.8.7. The message passing infrastructure was rewritten in 0.8.0 (originally Disruptor-based) and later moved to JCQueue.)

[rzo1]

The original 0.7.1 source had a comment backing this claim; the modern KryoTupleSerializer holds a Kryo field, and Kryo itself is not thread-safe (instances are scoped per executor/thread). Could you verify, or drop "thread-safe"?

[rzo1]

GitHub /blob/ URLs don't resolve to directories — this should be /tree/, or better, point at the entry-point file:

Suggested change

	- The implementation for distributed mode uses Netty [code](https://github.com/apache/storm/blob/v2.8.7/storm-client/src/jvm/org/apache/storm/messaging/netty/)
	- The implementation for distributed mode uses Netty [code](https://github.com/apache/storm/blob/v2.8.7/storm-client/src/jvm/org/apache/storm/messaging/netty/Context.java)

[rzo1]

Same /blob/ issue, and the directory only contains one file:

Suggested change

	- The implementation for local mode uses in memory Java queues (so that it's easy to use Storm locally without needing external messaging dependencies) [code](https://github.com/apache/storm/blob/v2.8.7/storm-client/src/jvm/org/apache/storm/messaging/local/)
	- The implementation for local mode uses in memory Java queues (so that it's easy to use Storm locally without needing external messaging dependencies) [code](https://github.com/apache/storm/blob/v2.8.7/storm-client/src/jvm/org/apache/storm/messaging/local/Context.java)

[rzo1]

Same /blob/ directory issue:

Suggested change

	- In local mode, the tuple is sent directly to an in-memory queue for the receiving task [code](https://github.com/apache/storm/blob/v2.8.7/storm-client/src/jvm/org/apache/storm/messaging/local/)
	- In local mode, the tuple is sent directly to an in-memory queue for the receiving task [code](https://github.com/apache/storm/blob/v2.8.7/storm-client/src/jvm/org/apache/storm/messaging/local/Context.java)

[rzo1]

Same /blob/ directory issue; original linked a specific file. Suggest pointing at Server.java (or removing this bullet — line 21 already covers Netty routing):

Suggested change

	- The message routing implementation is here: [code](https://github.com/apache/storm/blob/v2.8.7/storm-client/src/jvm/org/apache/storm/messaging/netty/)
	- The message routing implementation is here: [code](https://github.com/apache/storm/blob/v2.8.7/storm-client/src/jvm/org/apache/storm/messaging/netty/Server.java)

[rzo1]

In 2.x, bolt/spout executors consume from their JCQueue receive queue rather than listening on an in-memory connection:

Suggested change

	- Executors listen on an in-memory connection for messages [code](https://github.com/apache/storm/blob/v2.8.7/storm-client/src/jvm/org/apache/storm/executor/Executor.java)
	- Executors consume from their receive queue (a `JCQueue`) [code](https://github.com/apache/storm/blob/v2.8.7/storm-client/src/jvm/org/apache/storm/executor/Executor.java)

[rzo1]

Both bullets link to the same Task.java root. The original 0.7.1 doc had distinct line anchors. Either add #L<line> anchors at the relevant fields/methods, or merge into one bullet:

Suggested change

	- Tasks have a routing map from {stream id} -> {component id} -> {stream grouping function} [code](https://github.com/apache/storm/blob/v2.8.7/storm-client/src/jvm/org/apache/storm/daemon/Task.java)
	- Stream grouping functions determine the task ids to send the tuples to for either regular stream emit or direct stream emit [code](https://github.com/apache/storm/blob/v2.8.7/storm-client/src/jvm/org/apache/storm/daemon/Task.java)
	- Tasks have a routing map from {stream id} -> {component id} -> {stream grouping function}; the grouping functions determine the task ids to send the tuples to for either regular stream emit or direct stream emit. [code](https://github.com/apache/storm/blob/v2.8.7/storm-client/src/jvm/org/apache/storm/daemon/Task.java)

[rzo1]

The "Bolts listen here" (line 24) and "Bolt transfer code here" (line 30) bullets both link to BoltExecutor.java; same for SpoutExecutor.java on lines 25/31. Please add #L<line> anchors so each link lands on a distinct method, or merge the receive/transfer bullets — the right anchors are your call.