[
https://issues.redhat.com/browse/JGRP-2493?page=com.atlassian.jira.plugin...
]
Bela Ban commented on JGRP-2493:
--------------------------------
You have to differentiate between {{channel}}, which is the channel for the local cluster
(and which can be set using {{setProtocolStack()}}), and {{bridge}} which is the channel
for the bridge cluster.
The latter cannot currently be set, other than passing correct {{bridge_props}} to
{{RELAY}}.
I suggest you create a subclass of {{RELAY}} and override {{createBridge()}} to create
your bridge channel programmatically. I'll also create a getter/setter to a function
which creates the bridge channel.
RELAY does not use protocol stack supplied programmatically
-----------------------------------------------------------
Key: JGRP-2493
URL:
https://issues.redhat.com/browse/JGRP-2493
Project: JGroups
Issue Type: Bug
Affects Versions: 4.2.4
Reporter: S Pokutniy
Assignee: Bela Ban
Priority: Minor
Fix For: 4.2.5
RELAY does not use protocol stack supplied programmatically (i.e. stack which was set by
using relay.setProtocolStack(protocolStack). Even though the stack is used in init(), the
function below only relies on bridge_props file. Even though using an XML file is mostly
possible, it becomes problematic when a custom SSLContext needs to be used
in SSL_KEY_EXCHANGE, which can now only be set programmatically.
protected void createBridge() {
try {
if(log.isTraceEnabled())
log.trace("I'm the coordinator, creating a channel (props=" + bridge_props
+ ", cluster_name=" + bridge_name + ")");
{color:#FF0000}bridge=new JChannel(bridge_props);{color}
bridge.setDiscardOwnMessages(true); // don't receive my own messages
bridge.setReceiver(new Receiver());
bridge.connect(bridge_name);
}
catch(Exception e) {
log.error(Util.getMessage("FailedCreatingBridgeChannelProps") + bridge_props +
")", e);
}
}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)