[
http://jira.jboss.com/jira/browse/JGRP-449?page=comments#action_12357617 ]
Michael Newcomb commented on JGRP-449:
--------------------------------------
Sorry, I misread my own comment.
There is only one use of Channel.down() inside JBoss and that is in the ClusterPartition
(as you pointed out).
There are a few uses of the return result in Channel.down() inside JGroups and they are:
JChannel.connect, line 369:
Object res=down(connect_event); // waits forever until connected (or channel is closed)
JChannel.startFlush, line 1460:
successfulFlush = (Boolean) down(new Event(Event.SUSPEND));
MessageDispatcher.ProtocolAdapter.down(), line 737:
return channel.down(evt);
MuxChannel.down(), line 204:
return ch.down(evt);
Changing signature of Channel.down() breaks drop in replacement with
JGroups <= 2.4
-----------------------------------------------------------------------------------
Key: JGRP-449
URL:
http://jira.jboss.com/jira/browse/JGRP-449
Project: JGroups
Issue Type: Bug
Affects Versions: 2.5
Environment: JGroups 2.5 beta-1
Reporter: Michael Newcomb
Assigned To: Bela Ban
Fix For: 2.5
Changing the signatue for Channel.down() from:
void down(Event e);
to:
Object down(Event e);
Causes NoSuchMethodError to be thrown in JBoss 4.0.5.
This is not a super major issue (just need to recompile JBoss), but since our project
doesn't like the idea of recompiling JBoss (want to get it directly from the site) it
is a show stopper.
If drop-in replacement for JGroups <= 2.4 is a requirment, something will have to be
done but the result of Channel.down() is only used in a few places, so it shouldn't be
too much to get it to work.
It looks like it is just the JBoss HA service that uses Channel.down() explicitly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira