A possible reason would be that your 3 instances all use the same rmi port. But it should not be the case, as they use ports 1091, 1092 and 1093 in their servicemix.xml configuration file.
On 10/18/07, martymusk <[EMAIL PROTECTED]> wrote: > > Hi, > I'm trying to start ws-notification example (instance1,instance2,instance3), > but the following error occurs: > > Starting Apache ServiceMix ESB: 3.1.2 > > Loading Apache ServiceMix from file: servicemix2.xml > INFO - ConnectorServerFactoryBean - JMX connector available at: > service:jmx :rmi:///jndi/rmi://localhost:1092/jmxrmi > INFO - JBIContainer - ServiceMix 3.1.2 JBI Container > (wsn2) i s starting > INFO - JBIContainer - For help or more informations > please se e: http://incubator.apache.org/servicemix/ > WARN - ManagementContext - Failed to start jmx connector: > Cannot b ind to URL [rmi://localhost:1099/jmxrmi]: > javax.naming.NameAlreadyBoundException : jmxrmi [Root exception is > java.rmi.AlreadyBoundException: jmxrmi] > INFO - ComponentMBeanImpl - Initializing component: > #SubscriptionMa nager# > INFO - DeploymentService - Restoring service assemblies > INFO - ComponentMBeanImpl - Initializing component: > servicemix-wsn2 005 > WARN - NetworkConnector - Could not start network bridge > between: vm://wsnbroker2?network=true and: tcp://[EMAIL PROTECTED]:32804 due > to: java.net .UnknownHostException: cini172 > WARN - NetworkConnector - Could not start network bridge > between: vm://wsnbroker2?network=true and: tcp://[EMAIL PROTECTED]:32804 due > to: java.net .UnknownHostException: cini172 > ------------------------------------------------------------------- > > javax.naming.NameAlreadyBoundException is thrown by methods to indicate that > a binding cannot be added because the name is already bound to another > object. > > Can Somebody help me? > Thanks in advance, > Martina > > > -- > View this message in context: > http://www.nabble.com/jmx-connector-tf4646264s12049.html#a13272245 > Sent from the ServiceMix - User mailing list archive at Nabble.com. > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
