RemoteServiceMixClient creates MBean server that conflicts with other MBean
servers on port 1099
------------------------------------------------------------------------------------------------
Key: SM-1152
URL: https://issues.apache.org/activemq/browse/SM-1152
Project: ServiceMix
Issue Type: Bug
Components: servicemix-core
Affects Versions: 3.2.1, 3.2, 3.1.2, 3.1.1
Reporter: Trevor Pounds
The RemoteServiceMixClient object creates an embedded mbean server that
conflicts with other MBean servers running on port 1099. The following use
case shows the symptoms by starting an application in the following order.
1) start custom application using RemoteServiceMixClient class
i.e.
RemoteServiceMixClient client = new
RemoteServiceMixClient("http://localhost:61616";);
client.start();
2) start a default distribution of ServiceMix running on the same machine (i.e.
bin/servicemix)
Other servers that use port 1099 by default would also show these symptoms at
step 2 if started after a client using the RemoteServiceMixClient object. Also
note that if the steps 1 and 2 are inverted then RemoteServiceMixClient will
operate as desired but issue the warning "Failed to start jmx connector".
It looks like the org.apache.servicemix.jbi.management.MBeanServerContext start
method creates the MBean server via
org.apache.servicemix.jbi.jmx.RmiRegistryFactoryBean if none is found. A
workaround to disable the registry creation is to set createConnector to false
when using a RemoteServiceMixCilent. I will be attaching a patch to provide
this capability that only modifies the RemoteServiceMixClient.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
