[
https://issues.jboss.org/browse/JGRP-2090?page=com.atlassian.jira.plugin....
]
Will Wright commented on JGRP-2090:
-----------------------------------
Thanks for getting back. I can see what the underlying issue was now. My publisher was
running 3.6.6 and the receiver was on 3.6.10. Looks like this change does not maintain
binary compatibility between the micro version, however, the checks in
Version.isBinaryCompatible assume it does.
JGRP000027: failed passing message up
-------------------------------------
Key: JGRP-2090
URL:
https://issues.jboss.org/browse/JGRP-2090
Project: JGroups
Issue Type: Bug
Affects Versions: 3.6.10
Reporter: Will Wright
Assignee: Bela Ban
Fix For: 3.6.11, 4.0
The JGroups library is generating NullPointerExceptions when attempting to process
incoming messages. From what I can tell this is due to it looking for an incorrect message
header.
The TP object has a protocol id of 75 despite being a TUNNEL which ought to have an id of
24. The id is being correctly assigned to 24 at the Protocol.id member variable
declaration, but is then subsequently changed to 75 by the TP.init method. This seems to
have been caused by commit
[
6bc167f7e0181af32e1930935d8cf0efdc1e82f0|https://github.com/belaban/JGrou...]
which has the message "Added TP to jg-protocols.xml". If I backout this change
to the TP.init method so as to not update the id then my application receives the incoming
messages fine.
java.lang.NullPointerException: null
at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1872)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)