]
Jeff Mesnil updated JBMESSAGING-1247:
-------------------------------------
Priority: Minor (was: Major)
Remove requirement for JMX to use JGroups
-----------------------------------------
Key: JBMESSAGING-1247
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-1247
Project: JBoss Messaging
Issue Type: Task
Affects Versions: 1.4.1.beta1
Reporter: Brian Stansberry
Assigned To: Jeff Mesnil
Priority: Minor
Fix For: 1.4.1.beta2
The current JGroups integration uses JMX to get ahold of a Channel:
public Channel createControlChannel() throws Exception
{
return (Channel) server.invoke(this.channelFactory, MUX_OPERATION,
new Object[]{controlStack, uniqueID + "-CTRL", Boolean.TRUE, uniqueID},
MUX_SIGNATURE);
}
The channelFactory member is an ObjectName injected into MessagingPostOfficeService.
Better is to expose a property of type org.jgroups.ChannelFactory and inject an instance
of that. That's the POJI interface for an object that provides JGroups channels.
Background:
JGroups intends to remove the legacy org.jgroups.jmx.JChannelFactoryMBean interface that
is being invoked in the above code. That code is reflection based, so as long as a
service that exposes the MUX_OPERATION signature is registered in JMX, the call will still
work. AS 5 will ensure that such a service is registered, without using the
org.jgroups.jmx.JChannelFactoryMBean itself. So, the above JMX-based code will work, and
this isn't an urgent issue. But, this usage does tie JBM clustering to JMX, rather
than allowing simple MC integration or even manual instantiation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: