[
https://issues.jboss.org/browse/JGRP-2090?page=com.atlassian.jira.plugin....
]
Paul Illingworth commented on JGRP-2090:
----------------------------------------
I am seeing the same issue. For me the problem is that I am on a development network where
there are several JGroups domains/clusters active all using the same UDP muticast
addresses and ports but are differentiated by domain/cluster name. The other domains on
the network are using JGroups 3.6.3 whilst I am using 3.6.11 - this means I get the NPE.
I can avoid the problem by changing my UDP multicast address or port to
"physically" separate the domains/cluster instead of just relying on the domain
name.
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
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
(v7.2.3#72005)