You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Dejan Bosanac <de...@nighttale.net> on 2010/01/08 13:09:49 UTC

Re: java.io.IOException: Transport Connector could not be registered in JMX: Failed to bind to server socket: tcp://0.0.0.0:61616 due to: java.ne t.BindException: Address already in use: JVM_Bind

Hi Charles,

web console tries to start an embedded broker by default. You should try
adding something like this

webconsole.type=properties
webconsole.jms.url=tcp://localhost:61616
webconsole.jmx.url=service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
webconsole.jmx.user=smx
webconsole.jmx.password=smx

to etc/system.properties to make it connect to the remote broker.

See http://activemq.apache.org/osgi-integration.html for more details

Cheers
--
Dejan Bosanac - http://twitter.com/dejanb

Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net


On Fri, Jan 8, 2010 at 12:08 PM, cmoulliard <cm...@gmail.com> wrote:

>
> I have deployed ActiveMQ 5.3 top of ServiceMix 4.1.0-SNAPSHOT and installed
> a
> activemq-broker.xml configuration file
>
> Here is my osgi bundle list
>
> [  43] [Active     ] [            ] [       ] [   60] activemq-core (5.3.0)
> [  44] [Active     ] [            ] [       ] [   60] activemq-ra (5.3.0)
> [  45] [Active     ] [            ] [       ] [   60] activemq-console
> (5.3.0)
> [  46] [Active     ] [            ] [       ] [   60] activemq-pool (5.3.0)
> [  47] [Active     ] [Created     ] [       ] [   60] Apache ServiceMix
> Features :: ActiveMQ Commands (4.1.0.SNAPSHOT)
> [  59] [Active     ] [            ] [       ] [   60] activemq-broker.xml
> (0.0.0)
>
> To admin activemq, I have also deployed the activemq web console
>
> [  84] [Active     ] [            ] [       ] [   60]
> mvn_org.apache.activemq_activemq-web-console_5.3.0_war (0)
>
> Unfortunately, the following error is reported in the log
>
> {code}
> karaf@root> 2010-01-08 11:24:47,062 [Thread-5       ] INFO
> ResourceXmlApplicationContext  - Refreshing
> org.apache.xbean.spring.context.ResourceXmlApp
> licationContext@ff87dc: display name
> [org.apache.xbean.spring.context.ResourceXmlApplicationContext@ff87dc];
> startup date [Fri Jan 08 11:24:47 CET 201
> 0]; parent:
> org.springframework.web.context.support.XmlWebApplicationContext@1930ebb
> 2010-01-08 11:24:47,093 [Thread-5       ] INFO
>  XBeanXmlBeanDefinitionReader
> - Loading XML bean definitions from ServletContext resource [/WEB-INF/a
> ctivemq.xml]
> 2010-01-08 11:24:49,718 [Thread-5       ] INFO
> ResourceXmlApplicationContext  - Bean factory for application context
> [org.apache.xbean.spring.context
> .ResourceXmlApplicationContext@ff87dc]:
>
> org.springframework.beans.factory.support.DefaultListableBeanFactory@1a6ac39
> 2010-01-08 11:24:50,593 [Thread-5       ] INFO  BrokerService
> - Using Persistence Adapter: AMQPersistenceAdapter(activemq-data\localh
> ost)
> 2010-01-08 11:24:50,593 [Thread-5       ] INFO  AMQPersistenceAdapter
> - AMQStore starting using directory: activemq-data\localhost
> 2010-01-08 11:24:50,687 [Thread-5       ] INFO  KahaStore
> - Kaha Store using data directory activemq-data\localhost\kr-store\stat
> e
> 2010-01-08 11:24:50,843 [Thread-5       ] INFO  AMQPersistenceAdapter
> - Active data files: []
> 2010-01-08 11:24:51,046 [Thread-5       ] INFO  BrokerService
> - ActiveMQ null JMS Message Broker (localhost) is starting
> 2010-01-08 11:24:51,046 [Thread-5       ] INFO  BrokerService
> - For help or more information please see: http://activemq.apache.org/
> 2010-01-08 11:24:51,328 [Thread-5       ] INFO  KahaStore
> - Kaha Store using data directory activemq-data\localhost\kr-store\data
>
> 2010-01-08 11:24:51,906 [JMX connector  ] INFO  ManagementContext
> - JMX consoles can connect to service:jmx:rmi:///jndi/rmi://localhost:1
> 099/jmxrmi
> 2010-01-08 11:24:51,984 [Thread-5       ] INFO
>  TransportServerThreadSupport
> - Listening for connections at: tcp://localhost:61616
> 2010-01-08 11:24:52,000 [Thread-5       ] INFO  TransportConnector
> - Connector openwire Started
> 2010-01-08 11:24:52,031 [Thread-5       ] INFO
>  TransportServerThreadSupport
> - Listening for connections at: stomp://localhost:61613
> 2010-01-08 11:24:52,031 [Thread-5       ] INFO  TransportConnector
> - Connector stomp Started
> 2010-01-08 11:24:52,109 [Thread-5       ] INFO
>  TransportServerThreadSupport
> - Listening for connections at: xmpp://localhost:61222
> 2010-01-08 11:24:52,109 [Thread-5       ] INFO  TransportConnector
> - Connector xmpp Started
> 2010-01-08 11:24:52,109 [Thread-5       ] INFO  NetworkConnector
> - Network Connector defaultNetwork Started
> 2010-01-08 11:24:52,109 [Thread-5       ] INFO  BrokerService
> - ActiveMQ JMS Message Broker (localhost, ID:dell-charles-3782-12629462
> 91109-0:0) started
> 2010-01-08 11:24:52,171 [Thread-5       ] INFO  TransportConnector
> - Connector vm://localhost Started
> 2010-01-08 11:24:52,750 [Thread-5       ] INFO  WebConsoleStarter
> - ActiveMQ WebConsole initialized.
>
> Exception in thread "SpringOsgiExtenderThread-2"
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean
> with name 'org.apache.ac
> tivemq.xbean.XBeanBrokerService#0' defined in URL
> [bundle://59.0:0/META-INF/spring/activemq-broker.xml]: Invocation of init
> method failed; nested exce
> ption is java.io.IOException: Transport Connector could not be registered
> in
> JMX: Failed to bind to server socket: tcp://0.0.0.0:61616 due to: java.ne
> t.BindException: Address already in use: JVM_Bind
>
> QUESTION :
>
> The war file of activemq-console contains in the folder WEB-INF, an
> activemq.xml file. Is it this file which is in conflict with the
> activemq-broker.xml files and responsible of this error ?
> If I remove this file from the WAR, can the activemq web console work ?
>
> Regards,
>
> Charles Moulliard
> Senior Enterprise Architect
> Apache Camel Committer
>
> *****************************
> blog : http://cmoulliard.blogspot.com
> twitter : http://twitter.com/cmoulliard
> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>
> Apache Camel Group :
> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>
> -----
> Charles Moulliard
> SOA Architect
>
> My Blog :  http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/
> --
> View this message in context:
> http://old.nabble.com/java.io.IOException%3A-Transport-Connector-could-not-be-registered-in-JMX%3A-Failed-to-bind-to-server-socket%3A-tcp%3A--0.0.0.0%3A61616-due-to%3A-java.ne-t.BindException%3A-Address-already-in-use%3A-JVM_Bind-tp27074390p27074390.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>

Re: java.io.IOException: Transport Connector could not be registered in JMX: Failed to bind to server socket: tcp://0.0.0.0:61616 due to: java.ne t.BindException: Address already in use: JVM_Bind

Posted by cmoulliard <cm...@gmail.com>.
You are right.

The url to be used now is : 

service:jmx:rmi:///jndi/rmi://localhost:1099/karaf-root

and 

service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi

Regards,

Charles

Dejan Bosanac wrote:
> 
> Hi,
> 
> not sure what can it be then without inspecting it further. Just
> double-check the JMX uri
> 
> Cheers
> --
> Dejan Bosanac - http://twitter.com/dejanb
> 
> Open Source Integration - http://fusesource.com/
> ActiveMQ in Action - http://www.manning.com/snyder/
> Blog - http://www.nighttale.net
> 
> 
> On Fri, Jan 8, 2010 at 3:17 PM, cmoulliard <cm...@gmail.com> wrote:
> 
>>
>> Jconsole can connect to activemq instance.
>>
>>
>> Dejan Bosanac wrote:
>> >
>> > Hi Charles,
>> >
>> > seems like web console cannot connect to the that JMX url. Found this
>> > issue
>> > http://issues.apache.org/activemq/browse/AMQ-509
>> >
>> > Can you also check if JConsole can connect to your ActiveMQ instance?
>> >
>> > Cheers
>> > --
>> > Dejan Bosanac - http://twitter.com/dejanb
>> >
>> > Open Source Integration - http://fusesource.com/
>> > ActiveMQ in Action - http://www.manning.com/snyder/
>> > Blog - http://www.nighttale.net
>> >
>> >
>> > On Fri, Jan 8, 2010 at 2:12 PM, cmoulliard <cm...@gmail.com>
>> wrote:
>> >
>> >>
>> >> Hi Dejan,
>> >>
>> >> Many thanks for the tip.
>> >>
>> >> A new error is returned now which is related to JMX stuff :
>> >>
>> >> Caused by: java.lang.RuntimeException: java.io.IOException: Failed to
>> >> retrieve RMIServer stub: javax.naming.NameNotFoundException: jmxrmi
>> >>        at
>> >>
>> >>
>> org.apache.activemq.web.RemoteJMXBrokerFacade.createConnection(RemoteJMXBrokerFacade.java:164)
>> >>        at
>> >>
>> >>
>> org.apache.activemq.web.RemoteJMXBrokerFacade.getMBeanServerConnection(RemoteJMXBrokerFacade.java:113)
>> >>        at
>> >>
>> >>
>> org.apache.activemq.web.RemoteJMXBrokerFacade.getBrokerAdmin(RemoteJMXBrokerFacade.java:87)
>> >>        at
>> >>
>> >>
>> org.apache.activemq.web.RemoteJMXBrokerFacade.getBrokerName(RemoteJMXBrokerFacade.java:100)
>> >>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> >>        at
>> >>
>> >>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> >>        at
>> >>
>> >>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> >>        at java.lang.reflect.Method.invoke(Method.java:597)
>> >>        at javax.el.BeanELResolver.getValue(BeanELResolver.java:62)
>> >>        ... 44 more
>> >> Caused by: java.io.IOException: Failed to retrieve RMIServer stub:
>> >> javax.naming.NameNotFoundException: jmxrmi
>> >>        at
>> >>
>> javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:338)
>> >>        at
>> >>
>> >>
>> javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
>> >>        at
>> >>
>> >>
>> org.apache.activemq.web.RemoteJMXBrokerFacade.createConnection(RemoteJMXBrokerFacade.java:145)
>> >>        ... 52 more
>> >> Caused by: javax.naming.NameNotFoundException: jmxrmi
>> >>        at
>> >>
>> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:99)
>> >>        at
>> >>
>> >>
>> com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:185)
>> >>        at javax.naming.InitialContext.lookup(InitialContext.java:392)
>> >>        at
>> >>
>> >>
>> javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1886)
>> >>        at
>> >>
>> >>
>> javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1856)
>> >>        at
>> >>
>> javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:257)
>> >>        ... 54 more
>> >>
>> >> REMARK : This point has been mentioned this morning by scott petterson
>> >> when
>> >> he used the command activemq:query (see mail posted in servicemix
>> forum)
>> >>
>> >> For your information, I have created the following jira ticket because
>> >> when
>> >> we deploy the activemq-browser feature to deploy activemq, than the
>> >> command
>> >> activemq:browse, activemq:list, ... returns null
>> >>
>> >> https://issues.apache.org/activemq/browse/SMX4-458
>> >>
>> >> To simplify the deployment of JSP projects like activemq, camel web
>> >> console
>> >> and synchornised version between karaf, servicemix and camel, I have
>> >> posted
>> >> different tickets :
>> >>
>> >> https://issues.apache.org/activemq/browse/SMX4-446
>> >>
>> >> https://issues.apache.org/jira/browse/FELIX-1949
>> >>
>> >> Regards,
>> >>
>> >> Charles
>> >>
>> >> Dejan Bosanac wrote:
>> >> >
>> >> > Hi Charles,
>> >> >
>> >> > web console tries to start an embedded broker by default. You should
>> >> try
>> >> > adding something like this
>> >> >
>> >> > webconsole.type=properties
>> >> > webconsole.jms.url=tcp://localhost:61616
>> >> >
>> webconsole.jmx.url=service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
>> >> > webconsole.jmx.user=smx
>> >> > webconsole.jmx.password=smx
>> >> >
>> >> > to etc/system.properties to make it connect to the remote broker.
>> >> >
>> >> > See http://activemq.apache.org/osgi-integration.html for more
>> details
>> >> >
>> >> > Cheers
>> >> > --
>> >> > Dejan Bosanac - http://twitter.com/dejanb
>> >> >
>> >> > Open Source Integration - http://fusesource.com/
>> >> > ActiveMQ in Action - http://www.manning.com/snyder/
>> >> > Blog - http://www.nighttale.net
>> >> >
>> >> >
>> >> > On Fri, Jan 8, 2010 at 12:08 PM, cmoulliard <cm...@gmail.com>
>> >> wrote:
>> >> >
>> >> >>
>> >> >> I have deployed ActiveMQ 5.3 top of ServiceMix 4.1.0-SNAPSHOT and
>> >> >> installed
>> >> >> a
>> >> >> activemq-broker.xml configuration file
>> >> >>
>> >> >> Here is my osgi bundle list
>> >> >>
>> >> >> [  43] [Active     ] [            ] [       ] [   60] activemq-core
>> >> >> (5.3.0)
>> >> >> [  44] [Active     ] [            ] [       ] [   60] activemq-ra
>> >> (5.3.0)
>> >> >> [  45] [Active     ] [            ] [       ] [   60]
>> activemq-console
>> >> >> (5.3.0)
>> >> >> [  46] [Active     ] [            ] [       ] [   60] activemq-pool
>> >> >> (5.3.0)
>> >> >> [  47] [Active     ] [Created     ] [       ] [   60] Apache
>> >> ServiceMix
>> >> >> Features :: ActiveMQ Commands (4.1.0.SNAPSHOT)
>> >> >> [  59] [Active     ] [            ] [       ] [   60]
>> >> activemq-broker.xml
>> >> >> (0.0.0)
>> >> >>
>> >> >> To admin activemq, I have also deployed the activemq web console
>> >> >>
>> >> >> [  84] [Active     ] [            ] [       ] [   60]
>> >> >> mvn_org.apache.activemq_activemq-web-console_5.3.0_war (0)
>> >> >>
>> >> >> Unfortunately, the following error is reported in the log
>> >> >>
>> >> >> {code}
>> >> >> karaf@root> 2010-01-08 11:24:47,062 [Thread-5       ] INFO
>> >> >> ResourceXmlApplicationContext  - Refreshing
>> >> >> org.apache.xbean.spring.context.ResourceXmlApp
>> >> >> licationContext@ff87dc: display name
>> >> >>
>> >>
>> [org.apache.xbean.spring.context.ResourceXmlApplicationContext@ff87dc];
>> >> >> startup date [Fri Jan 08 11:24:47 CET 201
>> >> >> 0]; parent:
>> >> >>
>> >>
>> org.springframework.web.context.support.XmlWebApplicationContext@1930ebb
>> >> >> 2010-01-08 11:24:47,093 [Thread-5       ] INFO
>> >> >>  XBeanXmlBeanDefinitionReader
>> >> >> - Loading XML bean definitions from ServletContext resource
>> >> [/WEB-INF/a
>> >> >> ctivemq.xml]
>> >> >> 2010-01-08 11:24:49,718 [Thread-5       ] INFO
>> >> >> ResourceXmlApplicationContext  - Bean factory for application
>> context
>> >> >> [org.apache.xbean.spring.context
>> >> >> .ResourceXmlApplicationContext@ff87dc]:
>> >> >>
>> >> >>
>> >>
>> org.springframework.beans.factory.support.DefaultListableBeanFactory@1a6ac39
>> >> >> 2010-01-08 11:24:50,593 [Thread-5       ] INFO  BrokerService
>> >> >> - Using Persistence Adapter:
>> >> AMQPersistenceAdapter(activemq-data\localh
>> >> >> ost)
>> >> >> 2010-01-08 11:24:50,593 [Thread-5       ] INFO 
>> AMQPersistenceAdapter
>> >> >> - AMQStore starting using directory: activemq-data\localhost
>> >> >> 2010-01-08 11:24:50,687 [Thread-5       ] INFO  KahaStore
>> >> >> - Kaha Store using data directory
>> >> activemq-data\localhost\kr-store\stat
>> >> >> e
>> >> >> 2010-01-08 11:24:50,843 [Thread-5       ] INFO 
>> AMQPersistenceAdapter
>> >> >> - Active data files: []
>> >> >> 2010-01-08 11:24:51,046 [Thread-5       ] INFO  BrokerService
>> >> >> - ActiveMQ null JMS Message Broker (localhost) is starting
>> >> >> 2010-01-08 11:24:51,046 [Thread-5       ] INFO  BrokerService
>> >> >> - For help or more information please see:
>> http://activemq.apache.org/
>> >> >> 2010-01-08 11:24:51,328 [Thread-5       ] INFO  KahaStore
>> >> >> - Kaha Store using data directory
>> >> activemq-data\localhost\kr-store\data
>> >> >>
>> >> >> 2010-01-08 11:24:51,906 [JMX connector  ] INFO  ManagementContext
>> >> >> - JMX consoles can connect to
>> >> service:jmx:rmi:///jndi/rmi://localhost:1
>> >> >> 099/jmxrmi
>> >> >> 2010-01-08 11:24:51,984 [Thread-5       ] INFO
>> >> >>  TransportServerThreadSupport
>> >> >> - Listening for connections at: tcp://localhost:61616
>> >> >> 2010-01-08 11:24:52,000 [Thread-5       ] INFO  TransportConnector
>> >> >> - Connector openwire Started
>> >> >> 2010-01-08 11:24:52,031 [Thread-5       ] INFO
>> >> >>  TransportServerThreadSupport
>> >> >> - Listening for connections at: stomp://localhost:61613
>> >> >> 2010-01-08 11:24:52,031 [Thread-5       ] INFO  TransportConnector
>> >> >> - Connector stomp Started
>> >> >> 2010-01-08 11:24:52,109 [Thread-5       ] INFO
>> >> >>  TransportServerThreadSupport
>> >> >> - Listening for connections at: xmpp://localhost:61222
>> >> >> 2010-01-08 11:24:52,109 [Thread-5       ] INFO  TransportConnector
>> >> >> - Connector xmpp Started
>> >> >> 2010-01-08 11:24:52,109 [Thread-5       ] INFO  NetworkConnector
>> >> >> - Network Connector defaultNetwork Started
>> >> >> 2010-01-08 11:24:52,109 [Thread-5       ] INFO  BrokerService
>> >> >> - ActiveMQ JMS Message Broker (localhost,
>> >> ID:dell-charles-3782-12629462
>> >> >> 91109-0:0) started
>> >> >> 2010-01-08 11:24:52,171 [Thread-5       ] INFO  TransportConnector
>> >> >> - Connector vm://localhost Started
>> >> >> 2010-01-08 11:24:52,750 [Thread-5       ] INFO  WebConsoleStarter
>> >> >> - ActiveMQ WebConsole initialized.
>> >> >>
>> >> >> Exception in thread "SpringOsgiExtenderThread-2"
>> >> >> org.springframework.beans.factory.BeanCreationException: Error
>> >> creating
>> >> >> bean
>> >> >> with name 'org.apache.ac
>> >> >> tivemq.xbean.XBeanBrokerService#0' defined in URL
>> >> >> [bundle://59.0:0/META-INF/spring/activemq-broker.xml]: Invocation
>> of
>> >> init
>> >> >> method failed; nested exce
>> >> >> ption is java.io.IOException: Transport Connector could not be
>> >> registered
>> >> >> in
>> >> >> JMX: Failed to bind to server socket: tcp://0.0.0.0:61616 due to:
>> >> java.ne
>> >> >> t.BindException: Address already in use: JVM_Bind
>> >> >>
>> >> >> QUESTION :
>> >> >>
>> >> >> The war file of activemq-console contains in the folder WEB-INF, an
>> >> >> activemq.xml file. Is it this file which is in conflict with the
>> >> >> activemq-broker.xml files and responsible of this error ?
>> >> >> If I remove this file from the WAR, can the activemq web console
>> work
>> >> ?
>> >> >>
>> >> >> Regards,
>> >> >>
>> >> >> Charles Moulliard
>> >> >> Senior Enterprise Architect
>> >> >> Apache Camel Committer
>> >> >>
>> >> >> *****************************
>> >> >> blog : http://cmoulliard.blogspot.com
>> >> >> twitter : http://twitter.com/cmoulliard
>> >> >> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>> >> >>
>> >> >> Apache Camel Group :
>> >> >> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>> >> >>
>> >> >> -----
>> >> >> Charles Moulliard
>> >> >> SOA Architect
>> >> >>
>> >> >> My Blog :  http://cmoulliard.blogspot.com/
>> >> >> http://cmoulliard.blogspot.com/
>> >> >> --
>> >> >> View this message in context:
>> >> >>
>> >>
>> http://old.nabble.com/java.io.IOException%3A-Transport-Connector-could-not-be-registered-in-JMX%3A-Failed-to-bind-to-server-socket%3A-tcp%3A--0.0.0.0%3A61616-due-to%3A-java.ne-t.BindException%3A-Address-already-in-use%3A-JVM_Bind-tp27074390p27074390.html
>> >> >> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> > -----
>> >> > Dejan Bosanac
>> >> >
>> >> > Open Source Integration - http://fusesource.com/
>> >> > ActiveMQ in Action - http://www.manning.com/snyder/
>> >> > Blog - http://www.nighttale.net
>> >> >
>> >>
>> >>
>> >> -----
>> >> Charles Moulliard
>> >> SOA Architect
>> >>
>> >> My Blog :  http://cmoulliard.blogspot.com/
>> >> http://cmoulliard.blogspot.com/
>> >> --
>> >> View this message in context:
>> >>
>> http://old.nabble.com/java.io.IOException%3A-Transport-Connector-could-not-be-registered-in-JMX%3A-Failed-to-bind-to-server-socket%3A-tcp%3A--0.0.0.0%3A61616-due-to%3A-java.ne-t.BindException%3A-Address-already-in-use%3A-JVM_Bind-tp27074390p27075724.html
>> >> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>> >>
>> >>
>> >
>> >
>> > -----
>> > Dejan Bosanac
>> >
>> > Open Source Integration - http://fusesource.com/
>> > ActiveMQ in Action - http://www.manning.com/snyder/
>> > Blog - http://www.nighttale.net
>> >
>>
>>
>> -----
>> Charles Moulliard
>> SOA Architect
>>
>> My Blog :  http://cmoulliard.blogspot.com/
>> http://cmoulliard.blogspot.com/
>> --
>> View this message in context:
>> http://old.nabble.com/java.io.IOException%3A-Transport-Connector-could-not-be-registered-in-JMX%3A-Failed-to-bind-to-server-socket%3A-tcp%3A--0.0.0.0%3A61616-due-to%3A-java.ne-t.BindException%3A-Address-already-in-use%3A-JVM_Bind-tp27074390p27076650.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
> 
> 
> -----
> Dejan Bosanac
> 
> Open Source Integration - http://fusesource.com/
> ActiveMQ in Action - http://www.manning.com/snyder/
> Blog - http://www.nighttale.net
> 


-----
Charles Moulliard
SOA Architect

My Blog :  http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/  
-- 
View this message in context: http://old.nabble.com/java.io.IOException%3A-Transport-Connector-could-not-be-registered-in-JMX%3A-Failed-to-bind-to-server-socket%3A-tcp%3A--0.0.0.0%3A61616-due-to%3A-java.ne-t.BindException%3A-Address-already-in-use%3A-JVM_Bind-tp27074390p27078487.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Re: java.io.IOException: Transport Connector could not be registered in JMX: Failed to bind to server socket: tcp://0.0.0.0:61616 due to: java.ne t.BindException: Address already in use: JVM_Bind

Posted by Dejan Bosanac <de...@nighttale.net>.
Hi,

not sure what can it be then without inspecting it further. Just
double-check the JMX uri

Cheers
--
Dejan Bosanac - http://twitter.com/dejanb

Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net


On Fri, Jan 8, 2010 at 3:17 PM, cmoulliard <cm...@gmail.com> wrote:

>
> Jconsole can connect to activemq instance.
>
>
> Dejan Bosanac wrote:
> >
> > Hi Charles,
> >
> > seems like web console cannot connect to the that JMX url. Found this
> > issue
> > http://issues.apache.org/activemq/browse/AMQ-509
> >
> > Can you also check if JConsole can connect to your ActiveMQ instance?
> >
> > Cheers
> > --
> > Dejan Bosanac - http://twitter.com/dejanb
> >
> > Open Source Integration - http://fusesource.com/
> > ActiveMQ in Action - http://www.manning.com/snyder/
> > Blog - http://www.nighttale.net
> >
> >
> > On Fri, Jan 8, 2010 at 2:12 PM, cmoulliard <cm...@gmail.com> wrote:
> >
> >>
> >> Hi Dejan,
> >>
> >> Many thanks for the tip.
> >>
> >> A new error is returned now which is related to JMX stuff :
> >>
> >> Caused by: java.lang.RuntimeException: java.io.IOException: Failed to
> >> retrieve RMIServer stub: javax.naming.NameNotFoundException: jmxrmi
> >>        at
> >>
> >>
> org.apache.activemq.web.RemoteJMXBrokerFacade.createConnection(RemoteJMXBrokerFacade.java:164)
> >>        at
> >>
> >>
> org.apache.activemq.web.RemoteJMXBrokerFacade.getMBeanServerConnection(RemoteJMXBrokerFacade.java:113)
> >>        at
> >>
> >>
> org.apache.activemq.web.RemoteJMXBrokerFacade.getBrokerAdmin(RemoteJMXBrokerFacade.java:87)
> >>        at
> >>
> >>
> org.apache.activemq.web.RemoteJMXBrokerFacade.getBrokerName(RemoteJMXBrokerFacade.java:100)
> >>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>        at
> >>
> >>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> >>        at
> >>
> >>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> >>        at java.lang.reflect.Method.invoke(Method.java:597)
> >>        at javax.el.BeanELResolver.getValue(BeanELResolver.java:62)
> >>        ... 44 more
> >> Caused by: java.io.IOException: Failed to retrieve RMIServer stub:
> >> javax.naming.NameNotFoundException: jmxrmi
> >>        at
> >> javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:338)
> >>        at
> >>
> >>
> javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
> >>        at
> >>
> >>
> org.apache.activemq.web.RemoteJMXBrokerFacade.createConnection(RemoteJMXBrokerFacade.java:145)
> >>        ... 52 more
> >> Caused by: javax.naming.NameNotFoundException: jmxrmi
> >>        at
> >>
> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:99)
> >>        at
> >>
> >>
> com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:185)
> >>        at javax.naming.InitialContext.lookup(InitialContext.java:392)
> >>        at
> >>
> >>
> javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1886)
> >>        at
> >>
> >>
> javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1856)
> >>        at
> >> javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:257)
> >>        ... 54 more
> >>
> >> REMARK : This point has been mentioned this morning by scott petterson
> >> when
> >> he used the command activemq:query (see mail posted in servicemix forum)
> >>
> >> For your information, I have created the following jira ticket because
> >> when
> >> we deploy the activemq-browser feature to deploy activemq, than the
> >> command
> >> activemq:browse, activemq:list, ... returns null
> >>
> >> https://issues.apache.org/activemq/browse/SMX4-458
> >>
> >> To simplify the deployment of JSP projects like activemq, camel web
> >> console
> >> and synchornised version between karaf, servicemix and camel, I have
> >> posted
> >> different tickets :
> >>
> >> https://issues.apache.org/activemq/browse/SMX4-446
> >>
> >> https://issues.apache.org/jira/browse/FELIX-1949
> >>
> >> Regards,
> >>
> >> Charles
> >>
> >> Dejan Bosanac wrote:
> >> >
> >> > Hi Charles,
> >> >
> >> > web console tries to start an embedded broker by default. You should
> >> try
> >> > adding something like this
> >> >
> >> > webconsole.type=properties
> >> > webconsole.jms.url=tcp://localhost:61616
> >> > webconsole.jmx.url=service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
> >> > webconsole.jmx.user=smx
> >> > webconsole.jmx.password=smx
> >> >
> >> > to etc/system.properties to make it connect to the remote broker.
> >> >
> >> > See http://activemq.apache.org/osgi-integration.html for more details
> >> >
> >> > Cheers
> >> > --
> >> > Dejan Bosanac - http://twitter.com/dejanb
> >> >
> >> > Open Source Integration - http://fusesource.com/
> >> > ActiveMQ in Action - http://www.manning.com/snyder/
> >> > Blog - http://www.nighttale.net
> >> >
> >> >
> >> > On Fri, Jan 8, 2010 at 12:08 PM, cmoulliard <cm...@gmail.com>
> >> wrote:
> >> >
> >> >>
> >> >> I have deployed ActiveMQ 5.3 top of ServiceMix 4.1.0-SNAPSHOT and
> >> >> installed
> >> >> a
> >> >> activemq-broker.xml configuration file
> >> >>
> >> >> Here is my osgi bundle list
> >> >>
> >> >> [  43] [Active     ] [            ] [       ] [   60] activemq-core
> >> >> (5.3.0)
> >> >> [  44] [Active     ] [            ] [       ] [   60] activemq-ra
> >> (5.3.0)
> >> >> [  45] [Active     ] [            ] [       ] [   60]
> activemq-console
> >> >> (5.3.0)
> >> >> [  46] [Active     ] [            ] [       ] [   60] activemq-pool
> >> >> (5.3.0)
> >> >> [  47] [Active     ] [Created     ] [       ] [   60] Apache
> >> ServiceMix
> >> >> Features :: ActiveMQ Commands (4.1.0.SNAPSHOT)
> >> >> [  59] [Active     ] [            ] [       ] [   60]
> >> activemq-broker.xml
> >> >> (0.0.0)
> >> >>
> >> >> To admin activemq, I have also deployed the activemq web console
> >> >>
> >> >> [  84] [Active     ] [            ] [       ] [   60]
> >> >> mvn_org.apache.activemq_activemq-web-console_5.3.0_war (0)
> >> >>
> >> >> Unfortunately, the following error is reported in the log
> >> >>
> >> >> {code}
> >> >> karaf@root> 2010-01-08 11:24:47,062 [Thread-5       ] INFO
> >> >> ResourceXmlApplicationContext  - Refreshing
> >> >> org.apache.xbean.spring.context.ResourceXmlApp
> >> >> licationContext@ff87dc: display name
> >> >>
> >> [org.apache.xbean.spring.context.ResourceXmlApplicationContext@ff87dc];
> >> >> startup date [Fri Jan 08 11:24:47 CET 201
> >> >> 0]; parent:
> >> >>
> >> org.springframework.web.context.support.XmlWebApplicationContext@1930ebb
> >> >> 2010-01-08 11:24:47,093 [Thread-5       ] INFO
> >> >>  XBeanXmlBeanDefinitionReader
> >> >> - Loading XML bean definitions from ServletContext resource
> >> [/WEB-INF/a
> >> >> ctivemq.xml]
> >> >> 2010-01-08 11:24:49,718 [Thread-5       ] INFO
> >> >> ResourceXmlApplicationContext  - Bean factory for application context
> >> >> [org.apache.xbean.spring.context
> >> >> .ResourceXmlApplicationContext@ff87dc]:
> >> >>
> >> >>
> >>
> org.springframework.beans.factory.support.DefaultListableBeanFactory@1a6ac39
> >> >> 2010-01-08 11:24:50,593 [Thread-5       ] INFO  BrokerService
> >> >> - Using Persistence Adapter:
> >> AMQPersistenceAdapter(activemq-data\localh
> >> >> ost)
> >> >> 2010-01-08 11:24:50,593 [Thread-5       ] INFO  AMQPersistenceAdapter
> >> >> - AMQStore starting using directory: activemq-data\localhost
> >> >> 2010-01-08 11:24:50,687 [Thread-5       ] INFO  KahaStore
> >> >> - Kaha Store using data directory
> >> activemq-data\localhost\kr-store\stat
> >> >> e
> >> >> 2010-01-08 11:24:50,843 [Thread-5       ] INFO  AMQPersistenceAdapter
> >> >> - Active data files: []
> >> >> 2010-01-08 11:24:51,046 [Thread-5       ] INFO  BrokerService
> >> >> - ActiveMQ null JMS Message Broker (localhost) is starting
> >> >> 2010-01-08 11:24:51,046 [Thread-5       ] INFO  BrokerService
> >> >> - For help or more information please see:
> http://activemq.apache.org/
> >> >> 2010-01-08 11:24:51,328 [Thread-5       ] INFO  KahaStore
> >> >> - Kaha Store using data directory
> >> activemq-data\localhost\kr-store\data
> >> >>
> >> >> 2010-01-08 11:24:51,906 [JMX connector  ] INFO  ManagementContext
> >> >> - JMX consoles can connect to
> >> service:jmx:rmi:///jndi/rmi://localhost:1
> >> >> 099/jmxrmi
> >> >> 2010-01-08 11:24:51,984 [Thread-5       ] INFO
> >> >>  TransportServerThreadSupport
> >> >> - Listening for connections at: tcp://localhost:61616
> >> >> 2010-01-08 11:24:52,000 [Thread-5       ] INFO  TransportConnector
> >> >> - Connector openwire Started
> >> >> 2010-01-08 11:24:52,031 [Thread-5       ] INFO
> >> >>  TransportServerThreadSupport
> >> >> - Listening for connections at: stomp://localhost:61613
> >> >> 2010-01-08 11:24:52,031 [Thread-5       ] INFO  TransportConnector
> >> >> - Connector stomp Started
> >> >> 2010-01-08 11:24:52,109 [Thread-5       ] INFO
> >> >>  TransportServerThreadSupport
> >> >> - Listening for connections at: xmpp://localhost:61222
> >> >> 2010-01-08 11:24:52,109 [Thread-5       ] INFO  TransportConnector
> >> >> - Connector xmpp Started
> >> >> 2010-01-08 11:24:52,109 [Thread-5       ] INFO  NetworkConnector
> >> >> - Network Connector defaultNetwork Started
> >> >> 2010-01-08 11:24:52,109 [Thread-5       ] INFO  BrokerService
> >> >> - ActiveMQ JMS Message Broker (localhost,
> >> ID:dell-charles-3782-12629462
> >> >> 91109-0:0) started
> >> >> 2010-01-08 11:24:52,171 [Thread-5       ] INFO  TransportConnector
> >> >> - Connector vm://localhost Started
> >> >> 2010-01-08 11:24:52,750 [Thread-5       ] INFO  WebConsoleStarter
> >> >> - ActiveMQ WebConsole initialized.
> >> >>
> >> >> Exception in thread "SpringOsgiExtenderThread-2"
> >> >> org.springframework.beans.factory.BeanCreationException: Error
> >> creating
> >> >> bean
> >> >> with name 'org.apache.ac
> >> >> tivemq.xbean.XBeanBrokerService#0' defined in URL
> >> >> [bundle://59.0:0/META-INF/spring/activemq-broker.xml]: Invocation of
> >> init
> >> >> method failed; nested exce
> >> >> ption is java.io.IOException: Transport Connector could not be
> >> registered
> >> >> in
> >> >> JMX: Failed to bind to server socket: tcp://0.0.0.0:61616 due to:
> >> java.ne
> >> >> t.BindException: Address already in use: JVM_Bind
> >> >>
> >> >> QUESTION :
> >> >>
> >> >> The war file of activemq-console contains in the folder WEB-INF, an
> >> >> activemq.xml file. Is it this file which is in conflict with the
> >> >> activemq-broker.xml files and responsible of this error ?
> >> >> If I remove this file from the WAR, can the activemq web console work
> >> ?
> >> >>
> >> >> Regards,
> >> >>
> >> >> Charles Moulliard
> >> >> Senior Enterprise Architect
> >> >> Apache Camel Committer
> >> >>
> >> >> *****************************
> >> >> blog : http://cmoulliard.blogspot.com
> >> >> twitter : http://twitter.com/cmoulliard
> >> >> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
> >> >>
> >> >> Apache Camel Group :
> >> >> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
> >> >>
> >> >> -----
> >> >> Charles Moulliard
> >> >> SOA Architect
> >> >>
> >> >> My Blog :  http://cmoulliard.blogspot.com/
> >> >> http://cmoulliard.blogspot.com/
> >> >> --
> >> >> View this message in context:
> >> >>
> >>
> http://old.nabble.com/java.io.IOException%3A-Transport-Connector-could-not-be-registered-in-JMX%3A-Failed-to-bind-to-server-socket%3A-tcp%3A--0.0.0.0%3A61616-due-to%3A-java.ne-t.BindException%3A-Address-already-in-use%3A-JVM_Bind-tp27074390p27074390.html
> >> >> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >> >>
> >> >>
> >> >
> >> >
> >> > -----
> >> > Dejan Bosanac
> >> >
> >> > Open Source Integration - http://fusesource.com/
> >> > ActiveMQ in Action - http://www.manning.com/snyder/
> >> > Blog - http://www.nighttale.net
> >> >
> >>
> >>
> >> -----
> >> Charles Moulliard
> >> SOA Architect
> >>
> >> My Blog :  http://cmoulliard.blogspot.com/
> >> http://cmoulliard.blogspot.com/
> >> --
> >> View this message in context:
> >>
> http://old.nabble.com/java.io.IOException%3A-Transport-Connector-could-not-be-registered-in-JMX%3A-Failed-to-bind-to-server-socket%3A-tcp%3A--0.0.0.0%3A61616-due-to%3A-java.ne-t.BindException%3A-Address-already-in-use%3A-JVM_Bind-tp27074390p27075724.html
> >> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >>
> >>
> >
> >
> > -----
> > Dejan Bosanac
> >
> > Open Source Integration - http://fusesource.com/
> > ActiveMQ in Action - http://www.manning.com/snyder/
> > Blog - http://www.nighttale.net
> >
>
>
> -----
> Charles Moulliard
> SOA Architect
>
> My Blog :  http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/
> --
> View this message in context:
> http://old.nabble.com/java.io.IOException%3A-Transport-Connector-could-not-be-registered-in-JMX%3A-Failed-to-bind-to-server-socket%3A-tcp%3A--0.0.0.0%3A61616-due-to%3A-java.ne-t.BindException%3A-Address-already-in-use%3A-JVM_Bind-tp27074390p27076650.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>

Re: java.io.IOException: Transport Connector could not be registered in JMX: Failed to bind to server socket: tcp://0.0.0.0:61616 due to: java.ne t.BindException: Address already in use: JVM_Bind

Posted by cmoulliard <cm...@gmail.com>.
Jconsole can connect to activemq instance.


Dejan Bosanac wrote:
> 
> Hi Charles,
> 
> seems like web console cannot connect to the that JMX url. Found this
> issue
> http://issues.apache.org/activemq/browse/AMQ-509
> 
> Can you also check if JConsole can connect to your ActiveMQ instance?
> 
> Cheers
> --
> Dejan Bosanac - http://twitter.com/dejanb
> 
> Open Source Integration - http://fusesource.com/
> ActiveMQ in Action - http://www.manning.com/snyder/
> Blog - http://www.nighttale.net
> 
> 
> On Fri, Jan 8, 2010 at 2:12 PM, cmoulliard <cm...@gmail.com> wrote:
> 
>>
>> Hi Dejan,
>>
>> Many thanks for the tip.
>>
>> A new error is returned now which is related to JMX stuff :
>>
>> Caused by: java.lang.RuntimeException: java.io.IOException: Failed to
>> retrieve RMIServer stub: javax.naming.NameNotFoundException: jmxrmi
>>        at
>>
>> org.apache.activemq.web.RemoteJMXBrokerFacade.createConnection(RemoteJMXBrokerFacade.java:164)
>>        at
>>
>> org.apache.activemq.web.RemoteJMXBrokerFacade.getMBeanServerConnection(RemoteJMXBrokerFacade.java:113)
>>        at
>>
>> org.apache.activemq.web.RemoteJMXBrokerFacade.getBrokerAdmin(RemoteJMXBrokerFacade.java:87)
>>        at
>>
>> org.apache.activemq.web.RemoteJMXBrokerFacade.getBrokerName(RemoteJMXBrokerFacade.java:100)
>>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>        at
>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>        at
>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>        at java.lang.reflect.Method.invoke(Method.java:597)
>>        at javax.el.BeanELResolver.getValue(BeanELResolver.java:62)
>>        ... 44 more
>> Caused by: java.io.IOException: Failed to retrieve RMIServer stub:
>> javax.naming.NameNotFoundException: jmxrmi
>>        at
>> javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:338)
>>        at
>>
>> javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
>>        at
>>
>> org.apache.activemq.web.RemoteJMXBrokerFacade.createConnection(RemoteJMXBrokerFacade.java:145)
>>        ... 52 more
>> Caused by: javax.naming.NameNotFoundException: jmxrmi
>>        at
>> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:99)
>>        at
>>
>> com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:185)
>>        at javax.naming.InitialContext.lookup(InitialContext.java:392)
>>        at
>>
>> javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1886)
>>        at
>>
>> javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1856)
>>        at
>> javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:257)
>>        ... 54 more
>>
>> REMARK : This point has been mentioned this morning by scott petterson
>> when
>> he used the command activemq:query (see mail posted in servicemix forum)
>>
>> For your information, I have created the following jira ticket because
>> when
>> we deploy the activemq-browser feature to deploy activemq, than the
>> command
>> activemq:browse, activemq:list, ... returns null
>>
>> https://issues.apache.org/activemq/browse/SMX4-458
>>
>> To simplify the deployment of JSP projects like activemq, camel web
>> console
>> and synchornised version between karaf, servicemix and camel, I have
>> posted
>> different tickets :
>>
>> https://issues.apache.org/activemq/browse/SMX4-446
>>
>> https://issues.apache.org/jira/browse/FELIX-1949
>>
>> Regards,
>>
>> Charles
>>
>> Dejan Bosanac wrote:
>> >
>> > Hi Charles,
>> >
>> > web console tries to start an embedded broker by default. You should
>> try
>> > adding something like this
>> >
>> > webconsole.type=properties
>> > webconsole.jms.url=tcp://localhost:61616
>> > webconsole.jmx.url=service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
>> > webconsole.jmx.user=smx
>> > webconsole.jmx.password=smx
>> >
>> > to etc/system.properties to make it connect to the remote broker.
>> >
>> > See http://activemq.apache.org/osgi-integration.html for more details
>> >
>> > Cheers
>> > --
>> > Dejan Bosanac - http://twitter.com/dejanb
>> >
>> > Open Source Integration - http://fusesource.com/
>> > ActiveMQ in Action - http://www.manning.com/snyder/
>> > Blog - http://www.nighttale.net
>> >
>> >
>> > On Fri, Jan 8, 2010 at 12:08 PM, cmoulliard <cm...@gmail.com>
>> wrote:
>> >
>> >>
>> >> I have deployed ActiveMQ 5.3 top of ServiceMix 4.1.0-SNAPSHOT and
>> >> installed
>> >> a
>> >> activemq-broker.xml configuration file
>> >>
>> >> Here is my osgi bundle list
>> >>
>> >> [  43] [Active     ] [            ] [       ] [   60] activemq-core
>> >> (5.3.0)
>> >> [  44] [Active     ] [            ] [       ] [   60] activemq-ra
>> (5.3.0)
>> >> [  45] [Active     ] [            ] [       ] [   60] activemq-console
>> >> (5.3.0)
>> >> [  46] [Active     ] [            ] [       ] [   60] activemq-pool
>> >> (5.3.0)
>> >> [  47] [Active     ] [Created     ] [       ] [   60] Apache
>> ServiceMix
>> >> Features :: ActiveMQ Commands (4.1.0.SNAPSHOT)
>> >> [  59] [Active     ] [            ] [       ] [   60]
>> activemq-broker.xml
>> >> (0.0.0)
>> >>
>> >> To admin activemq, I have also deployed the activemq web console
>> >>
>> >> [  84] [Active     ] [            ] [       ] [   60]
>> >> mvn_org.apache.activemq_activemq-web-console_5.3.0_war (0)
>> >>
>> >> Unfortunately, the following error is reported in the log
>> >>
>> >> {code}
>> >> karaf@root> 2010-01-08 11:24:47,062 [Thread-5       ] INFO
>> >> ResourceXmlApplicationContext  - Refreshing
>> >> org.apache.xbean.spring.context.ResourceXmlApp
>> >> licationContext@ff87dc: display name
>> >>
>> [org.apache.xbean.spring.context.ResourceXmlApplicationContext@ff87dc];
>> >> startup date [Fri Jan 08 11:24:47 CET 201
>> >> 0]; parent:
>> >>
>> org.springframework.web.context.support.XmlWebApplicationContext@1930ebb
>> >> 2010-01-08 11:24:47,093 [Thread-5       ] INFO
>> >>  XBeanXmlBeanDefinitionReader
>> >> - Loading XML bean definitions from ServletContext resource
>> [/WEB-INF/a
>> >> ctivemq.xml]
>> >> 2010-01-08 11:24:49,718 [Thread-5       ] INFO
>> >> ResourceXmlApplicationContext  - Bean factory for application context
>> >> [org.apache.xbean.spring.context
>> >> .ResourceXmlApplicationContext@ff87dc]:
>> >>
>> >>
>> org.springframework.beans.factory.support.DefaultListableBeanFactory@1a6ac39
>> >> 2010-01-08 11:24:50,593 [Thread-5       ] INFO  BrokerService
>> >> - Using Persistence Adapter:
>> AMQPersistenceAdapter(activemq-data\localh
>> >> ost)
>> >> 2010-01-08 11:24:50,593 [Thread-5       ] INFO  AMQPersistenceAdapter
>> >> - AMQStore starting using directory: activemq-data\localhost
>> >> 2010-01-08 11:24:50,687 [Thread-5       ] INFO  KahaStore
>> >> - Kaha Store using data directory
>> activemq-data\localhost\kr-store\stat
>> >> e
>> >> 2010-01-08 11:24:50,843 [Thread-5       ] INFO  AMQPersistenceAdapter
>> >> - Active data files: []
>> >> 2010-01-08 11:24:51,046 [Thread-5       ] INFO  BrokerService
>> >> - ActiveMQ null JMS Message Broker (localhost) is starting
>> >> 2010-01-08 11:24:51,046 [Thread-5       ] INFO  BrokerService
>> >> - For help or more information please see: http://activemq.apache.org/
>> >> 2010-01-08 11:24:51,328 [Thread-5       ] INFO  KahaStore
>> >> - Kaha Store using data directory
>> activemq-data\localhost\kr-store\data
>> >>
>> >> 2010-01-08 11:24:51,906 [JMX connector  ] INFO  ManagementContext
>> >> - JMX consoles can connect to
>> service:jmx:rmi:///jndi/rmi://localhost:1
>> >> 099/jmxrmi
>> >> 2010-01-08 11:24:51,984 [Thread-5       ] INFO
>> >>  TransportServerThreadSupport
>> >> - Listening for connections at: tcp://localhost:61616
>> >> 2010-01-08 11:24:52,000 [Thread-5       ] INFO  TransportConnector
>> >> - Connector openwire Started
>> >> 2010-01-08 11:24:52,031 [Thread-5       ] INFO
>> >>  TransportServerThreadSupport
>> >> - Listening for connections at: stomp://localhost:61613
>> >> 2010-01-08 11:24:52,031 [Thread-5       ] INFO  TransportConnector
>> >> - Connector stomp Started
>> >> 2010-01-08 11:24:52,109 [Thread-5       ] INFO
>> >>  TransportServerThreadSupport
>> >> - Listening for connections at: xmpp://localhost:61222
>> >> 2010-01-08 11:24:52,109 [Thread-5       ] INFO  TransportConnector
>> >> - Connector xmpp Started
>> >> 2010-01-08 11:24:52,109 [Thread-5       ] INFO  NetworkConnector
>> >> - Network Connector defaultNetwork Started
>> >> 2010-01-08 11:24:52,109 [Thread-5       ] INFO  BrokerService
>> >> - ActiveMQ JMS Message Broker (localhost,
>> ID:dell-charles-3782-12629462
>> >> 91109-0:0) started
>> >> 2010-01-08 11:24:52,171 [Thread-5       ] INFO  TransportConnector
>> >> - Connector vm://localhost Started
>> >> 2010-01-08 11:24:52,750 [Thread-5       ] INFO  WebConsoleStarter
>> >> - ActiveMQ WebConsole initialized.
>> >>
>> >> Exception in thread "SpringOsgiExtenderThread-2"
>> >> org.springframework.beans.factory.BeanCreationException: Error
>> creating
>> >> bean
>> >> with name 'org.apache.ac
>> >> tivemq.xbean.XBeanBrokerService#0' defined in URL
>> >> [bundle://59.0:0/META-INF/spring/activemq-broker.xml]: Invocation of
>> init
>> >> method failed; nested exce
>> >> ption is java.io.IOException: Transport Connector could not be
>> registered
>> >> in
>> >> JMX: Failed to bind to server socket: tcp://0.0.0.0:61616 due to:
>> java.ne
>> >> t.BindException: Address already in use: JVM_Bind
>> >>
>> >> QUESTION :
>> >>
>> >> The war file of activemq-console contains in the folder WEB-INF, an
>> >> activemq.xml file. Is it this file which is in conflict with the
>> >> activemq-broker.xml files and responsible of this error ?
>> >> If I remove this file from the WAR, can the activemq web console work
>> ?
>> >>
>> >> Regards,
>> >>
>> >> Charles Moulliard
>> >> Senior Enterprise Architect
>> >> Apache Camel Committer
>> >>
>> >> *****************************
>> >> blog : http://cmoulliard.blogspot.com
>> >> twitter : http://twitter.com/cmoulliard
>> >> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>> >>
>> >> Apache Camel Group :
>> >> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>> >>
>> >> -----
>> >> Charles Moulliard
>> >> SOA Architect
>> >>
>> >> My Blog :  http://cmoulliard.blogspot.com/
>> >> http://cmoulliard.blogspot.com/
>> >> --
>> >> View this message in context:
>> >>
>> http://old.nabble.com/java.io.IOException%3A-Transport-Connector-could-not-be-registered-in-JMX%3A-Failed-to-bind-to-server-socket%3A-tcp%3A--0.0.0.0%3A61616-due-to%3A-java.ne-t.BindException%3A-Address-already-in-use%3A-JVM_Bind-tp27074390p27074390.html
>> >> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>> >>
>> >>
>> >
>> >
>> > -----
>> > Dejan Bosanac
>> >
>> > Open Source Integration - http://fusesource.com/
>> > ActiveMQ in Action - http://www.manning.com/snyder/
>> > Blog - http://www.nighttale.net
>> >
>>
>>
>> -----
>> Charles Moulliard
>> SOA Architect
>>
>> My Blog :  http://cmoulliard.blogspot.com/
>> http://cmoulliard.blogspot.com/
>> --
>> View this message in context:
>> http://old.nabble.com/java.io.IOException%3A-Transport-Connector-could-not-be-registered-in-JMX%3A-Failed-to-bind-to-server-socket%3A-tcp%3A--0.0.0.0%3A61616-due-to%3A-java.ne-t.BindException%3A-Address-already-in-use%3A-JVM_Bind-tp27074390p27075724.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
> 
> 
> -----
> Dejan Bosanac
> 
> Open Source Integration - http://fusesource.com/
> ActiveMQ in Action - http://www.manning.com/snyder/
> Blog - http://www.nighttale.net
> 


-----
Charles Moulliard
SOA Architect

My Blog :  http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/  
-- 
View this message in context: http://old.nabble.com/java.io.IOException%3A-Transport-Connector-could-not-be-registered-in-JMX%3A-Failed-to-bind-to-server-socket%3A-tcp%3A--0.0.0.0%3A61616-due-to%3A-java.ne-t.BindException%3A-Address-already-in-use%3A-JVM_Bind-tp27074390p27076650.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Re: java.io.IOException: Transport Connector could not be registered in JMX: Failed to bind to server socket: tcp://0.0.0.0:61616 due to: java.ne t.BindException: Address already in use: JVM_Bind

Posted by Dejan Bosanac <de...@nighttale.net>.
Hi Charles,

seems like web console cannot connect to the that JMX url. Found this issue
http://issues.apache.org/activemq/browse/AMQ-509

Can you also check if JConsole can connect to your ActiveMQ instance?

Cheers
--
Dejan Bosanac - http://twitter.com/dejanb

Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net


On Fri, Jan 8, 2010 at 2:12 PM, cmoulliard <cm...@gmail.com> wrote:

>
> Hi Dejan,
>
> Many thanks for the tip.
>
> A new error is returned now which is related to JMX stuff :
>
> Caused by: java.lang.RuntimeException: java.io.IOException: Failed to
> retrieve RMIServer stub: javax.naming.NameNotFoundException: jmxrmi
>        at
>
> org.apache.activemq.web.RemoteJMXBrokerFacade.createConnection(RemoteJMXBrokerFacade.java:164)
>        at
>
> org.apache.activemq.web.RemoteJMXBrokerFacade.getMBeanServerConnection(RemoteJMXBrokerFacade.java:113)
>        at
>
> org.apache.activemq.web.RemoteJMXBrokerFacade.getBrokerAdmin(RemoteJMXBrokerFacade.java:87)
>        at
>
> org.apache.activemq.web.RemoteJMXBrokerFacade.getBrokerName(RemoteJMXBrokerFacade.java:100)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>        at
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>        at java.lang.reflect.Method.invoke(Method.java:597)
>        at javax.el.BeanELResolver.getValue(BeanELResolver.java:62)
>        ... 44 more
> Caused by: java.io.IOException: Failed to retrieve RMIServer stub:
> javax.naming.NameNotFoundException: jmxrmi
>        at
> javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:338)
>        at
>
> javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
>        at
>
> org.apache.activemq.web.RemoteJMXBrokerFacade.createConnection(RemoteJMXBrokerFacade.java:145)
>        ... 52 more
> Caused by: javax.naming.NameNotFoundException: jmxrmi
>        at
> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:99)
>        at
>
> com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:185)
>        at javax.naming.InitialContext.lookup(InitialContext.java:392)
>        at
>
> javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1886)
>        at
>
> javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1856)
>        at
> javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:257)
>        ... 54 more
>
> REMARK : This point has been mentioned this morning by scott petterson when
> he used the command activemq:query (see mail posted in servicemix forum)
>
> For your information, I have created the following jira ticket because when
> we deploy the activemq-browser feature to deploy activemq, than the command
> activemq:browse, activemq:list, ... returns null
>
> https://issues.apache.org/activemq/browse/SMX4-458
>
> To simplify the deployment of JSP projects like activemq, camel web console
> and synchornised version between karaf, servicemix and camel, I have posted
> different tickets :
>
> https://issues.apache.org/activemq/browse/SMX4-446
>
> https://issues.apache.org/jira/browse/FELIX-1949
>
> Regards,
>
> Charles
>
> Dejan Bosanac wrote:
> >
> > Hi Charles,
> >
> > web console tries to start an embedded broker by default. You should try
> > adding something like this
> >
> > webconsole.type=properties
> > webconsole.jms.url=tcp://localhost:61616
> > webconsole.jmx.url=service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
> > webconsole.jmx.user=smx
> > webconsole.jmx.password=smx
> >
> > to etc/system.properties to make it connect to the remote broker.
> >
> > See http://activemq.apache.org/osgi-integration.html for more details
> >
> > Cheers
> > --
> > Dejan Bosanac - http://twitter.com/dejanb
> >
> > Open Source Integration - http://fusesource.com/
> > ActiveMQ in Action - http://www.manning.com/snyder/
> > Blog - http://www.nighttale.net
> >
> >
> > On Fri, Jan 8, 2010 at 12:08 PM, cmoulliard <cm...@gmail.com>
> wrote:
> >
> >>
> >> I have deployed ActiveMQ 5.3 top of ServiceMix 4.1.0-SNAPSHOT and
> >> installed
> >> a
> >> activemq-broker.xml configuration file
> >>
> >> Here is my osgi bundle list
> >>
> >> [  43] [Active     ] [            ] [       ] [   60] activemq-core
> >> (5.3.0)
> >> [  44] [Active     ] [            ] [       ] [   60] activemq-ra
> (5.3.0)
> >> [  45] [Active     ] [            ] [       ] [   60] activemq-console
> >> (5.3.0)
> >> [  46] [Active     ] [            ] [       ] [   60] activemq-pool
> >> (5.3.0)
> >> [  47] [Active     ] [Created     ] [       ] [   60] Apache ServiceMix
> >> Features :: ActiveMQ Commands (4.1.0.SNAPSHOT)
> >> [  59] [Active     ] [            ] [       ] [   60]
> activemq-broker.xml
> >> (0.0.0)
> >>
> >> To admin activemq, I have also deployed the activemq web console
> >>
> >> [  84] [Active     ] [            ] [       ] [   60]
> >> mvn_org.apache.activemq_activemq-web-console_5.3.0_war (0)
> >>
> >> Unfortunately, the following error is reported in the log
> >>
> >> {code}
> >> karaf@root> 2010-01-08 11:24:47,062 [Thread-5       ] INFO
> >> ResourceXmlApplicationContext  - Refreshing
> >> org.apache.xbean.spring.context.ResourceXmlApp
> >> licationContext@ff87dc: display name
> >> [org.apache.xbean.spring.context.ResourceXmlApplicationContext@ff87dc];
> >> startup date [Fri Jan 08 11:24:47 CET 201
> >> 0]; parent:
> >> org.springframework.web.context.support.XmlWebApplicationContext@1930ebb
> >> 2010-01-08 11:24:47,093 [Thread-5       ] INFO
> >>  XBeanXmlBeanDefinitionReader
> >> - Loading XML bean definitions from ServletContext resource [/WEB-INF/a
> >> ctivemq.xml]
> >> 2010-01-08 11:24:49,718 [Thread-5       ] INFO
> >> ResourceXmlApplicationContext  - Bean factory for application context
> >> [org.apache.xbean.spring.context
> >> .ResourceXmlApplicationContext@ff87dc]:
> >>
> >>
> org.springframework.beans.factory.support.DefaultListableBeanFactory@1a6ac39
> >> 2010-01-08 11:24:50,593 [Thread-5       ] INFO  BrokerService
> >> - Using Persistence Adapter: AMQPersistenceAdapter(activemq-data\localh
> >> ost)
> >> 2010-01-08 11:24:50,593 [Thread-5       ] INFO  AMQPersistenceAdapter
> >> - AMQStore starting using directory: activemq-data\localhost
> >> 2010-01-08 11:24:50,687 [Thread-5       ] INFO  KahaStore
> >> - Kaha Store using data directory activemq-data\localhost\kr-store\stat
> >> e
> >> 2010-01-08 11:24:50,843 [Thread-5       ] INFO  AMQPersistenceAdapter
> >> - Active data files: []
> >> 2010-01-08 11:24:51,046 [Thread-5       ] INFO  BrokerService
> >> - ActiveMQ null JMS Message Broker (localhost) is starting
> >> 2010-01-08 11:24:51,046 [Thread-5       ] INFO  BrokerService
> >> - For help or more information please see: http://activemq.apache.org/
> >> 2010-01-08 11:24:51,328 [Thread-5       ] INFO  KahaStore
> >> - Kaha Store using data directory activemq-data\localhost\kr-store\data
> >>
> >> 2010-01-08 11:24:51,906 [JMX connector  ] INFO  ManagementContext
> >> - JMX consoles can connect to service:jmx:rmi:///jndi/rmi://localhost:1
> >> 099/jmxrmi
> >> 2010-01-08 11:24:51,984 [Thread-5       ] INFO
> >>  TransportServerThreadSupport
> >> - Listening for connections at: tcp://localhost:61616
> >> 2010-01-08 11:24:52,000 [Thread-5       ] INFO  TransportConnector
> >> - Connector openwire Started
> >> 2010-01-08 11:24:52,031 [Thread-5       ] INFO
> >>  TransportServerThreadSupport
> >> - Listening for connections at: stomp://localhost:61613
> >> 2010-01-08 11:24:52,031 [Thread-5       ] INFO  TransportConnector
> >> - Connector stomp Started
> >> 2010-01-08 11:24:52,109 [Thread-5       ] INFO
> >>  TransportServerThreadSupport
> >> - Listening for connections at: xmpp://localhost:61222
> >> 2010-01-08 11:24:52,109 [Thread-5       ] INFO  TransportConnector
> >> - Connector xmpp Started
> >> 2010-01-08 11:24:52,109 [Thread-5       ] INFO  NetworkConnector
> >> - Network Connector defaultNetwork Started
> >> 2010-01-08 11:24:52,109 [Thread-5       ] INFO  BrokerService
> >> - ActiveMQ JMS Message Broker (localhost, ID:dell-charles-3782-12629462
> >> 91109-0:0) started
> >> 2010-01-08 11:24:52,171 [Thread-5       ] INFO  TransportConnector
> >> - Connector vm://localhost Started
> >> 2010-01-08 11:24:52,750 [Thread-5       ] INFO  WebConsoleStarter
> >> - ActiveMQ WebConsole initialized.
> >>
> >> Exception in thread "SpringOsgiExtenderThread-2"
> >> org.springframework.beans.factory.BeanCreationException: Error creating
> >> bean
> >> with name 'org.apache.ac
> >> tivemq.xbean.XBeanBrokerService#0' defined in URL
> >> [bundle://59.0:0/META-INF/spring/activemq-broker.xml]: Invocation of
> init
> >> method failed; nested exce
> >> ption is java.io.IOException: Transport Connector could not be
> registered
> >> in
> >> JMX: Failed to bind to server socket: tcp://0.0.0.0:61616 due to:
> java.ne
> >> t.BindException: Address already in use: JVM_Bind
> >>
> >> QUESTION :
> >>
> >> The war file of activemq-console contains in the folder WEB-INF, an
> >> activemq.xml file. Is it this file which is in conflict with the
> >> activemq-broker.xml files and responsible of this error ?
> >> If I remove this file from the WAR, can the activemq web console work ?
> >>
> >> Regards,
> >>
> >> Charles Moulliard
> >> Senior Enterprise Architect
> >> Apache Camel Committer
> >>
> >> *****************************
> >> blog : http://cmoulliard.blogspot.com
> >> twitter : http://twitter.com/cmoulliard
> >> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
> >>
> >> Apache Camel Group :
> >> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
> >>
> >> -----
> >> Charles Moulliard
> >> SOA Architect
> >>
> >> My Blog :  http://cmoulliard.blogspot.com/
> >> http://cmoulliard.blogspot.com/
> >> --
> >> View this message in context:
> >>
> http://old.nabble.com/java.io.IOException%3A-Transport-Connector-could-not-be-registered-in-JMX%3A-Failed-to-bind-to-server-socket%3A-tcp%3A--0.0.0.0%3A61616-due-to%3A-java.ne-t.BindException%3A-Address-already-in-use%3A-JVM_Bind-tp27074390p27074390.html
> >> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >>
> >>
> >
> >
> > -----
> > Dejan Bosanac
> >
> > Open Source Integration - http://fusesource.com/
> > ActiveMQ in Action - http://www.manning.com/snyder/
> > Blog - http://www.nighttale.net
> >
>
>
> -----
> Charles Moulliard
> SOA Architect
>
> My Blog :  http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/
> --
> View this message in context:
> http://old.nabble.com/java.io.IOException%3A-Transport-Connector-could-not-be-registered-in-JMX%3A-Failed-to-bind-to-server-socket%3A-tcp%3A--0.0.0.0%3A61616-due-to%3A-java.ne-t.BindException%3A-Address-already-in-use%3A-JVM_Bind-tp27074390p27075724.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>

Re: java.io.IOException: Transport Connector could not be registered in JMX: Failed to bind to server socket: tcp://0.0.0.0:61616 due to: java.ne t.BindException: Address already in use: JVM_Bind

Posted by cmoulliard <cm...@gmail.com>.
Hi Dejan,

Many thanks for the tip. 

A new error is returned now which is related to JMX stuff :

Caused by: java.lang.RuntimeException: java.io.IOException: Failed to
retrieve RMIServer stub: javax.naming.NameNotFoundException: jmxrmi
	at
org.apache.activemq.web.RemoteJMXBrokerFacade.createConnection(RemoteJMXBrokerFacade.java:164)
	at
org.apache.activemq.web.RemoteJMXBrokerFacade.getMBeanServerConnection(RemoteJMXBrokerFacade.java:113)
	at
org.apache.activemq.web.RemoteJMXBrokerFacade.getBrokerAdmin(RemoteJMXBrokerFacade.java:87)
	at
org.apache.activemq.web.RemoteJMXBrokerFacade.getBrokerName(RemoteJMXBrokerFacade.java:100)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at javax.el.BeanELResolver.getValue(BeanELResolver.java:62)
	... 44 more
Caused by: java.io.IOException: Failed to retrieve RMIServer stub:
javax.naming.NameNotFoundException: jmxrmi
	at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:338)
	at
javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
	at
org.apache.activemq.web.RemoteJMXBrokerFacade.createConnection(RemoteJMXBrokerFacade.java:145)
	... 52 more
Caused by: javax.naming.NameNotFoundException: jmxrmi
	at
com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:99)
	at
com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:185)
	at javax.naming.InitialContext.lookup(InitialContext.java:392)
	at
javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1886)
	at
javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1856)
	at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:257)
	... 54 more

REMARK : This point has been mentioned this morning by scott petterson when
he used the command activemq:query (see mail posted in servicemix forum)

For your information, I have created the following jira ticket because when
we deploy the activemq-browser feature to deploy activemq, than the command
activemq:browse, activemq:list, ... returns null

https://issues.apache.org/activemq/browse/SMX4-458

To simplify the deployment of JSP projects like activemq, camel web console
and synchornised version between karaf, servicemix and camel, I have posted
different tickets :

https://issues.apache.org/activemq/browse/SMX4-446

https://issues.apache.org/jira/browse/FELIX-1949

Regards,

Charles

Dejan Bosanac wrote:
> 
> Hi Charles,
> 
> web console tries to start an embedded broker by default. You should try
> adding something like this
> 
> webconsole.type=properties
> webconsole.jms.url=tcp://localhost:61616
> webconsole.jmx.url=service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
> webconsole.jmx.user=smx
> webconsole.jmx.password=smx
> 
> to etc/system.properties to make it connect to the remote broker.
> 
> See http://activemq.apache.org/osgi-integration.html for more details
> 
> Cheers
> --
> Dejan Bosanac - http://twitter.com/dejanb
> 
> Open Source Integration - http://fusesource.com/
> ActiveMQ in Action - http://www.manning.com/snyder/
> Blog - http://www.nighttale.net
> 
> 
> On Fri, Jan 8, 2010 at 12:08 PM, cmoulliard <cm...@gmail.com> wrote:
> 
>>
>> I have deployed ActiveMQ 5.3 top of ServiceMix 4.1.0-SNAPSHOT and
>> installed
>> a
>> activemq-broker.xml configuration file
>>
>> Here is my osgi bundle list
>>
>> [  43] [Active     ] [            ] [       ] [   60] activemq-core
>> (5.3.0)
>> [  44] [Active     ] [            ] [       ] [   60] activemq-ra (5.3.0)
>> [  45] [Active     ] [            ] [       ] [   60] activemq-console
>> (5.3.0)
>> [  46] [Active     ] [            ] [       ] [   60] activemq-pool
>> (5.3.0)
>> [  47] [Active     ] [Created     ] [       ] [   60] Apache ServiceMix
>> Features :: ActiveMQ Commands (4.1.0.SNAPSHOT)
>> [  59] [Active     ] [            ] [       ] [   60] activemq-broker.xml
>> (0.0.0)
>>
>> To admin activemq, I have also deployed the activemq web console
>>
>> [  84] [Active     ] [            ] [       ] [   60]
>> mvn_org.apache.activemq_activemq-web-console_5.3.0_war (0)
>>
>> Unfortunately, the following error is reported in the log
>>
>> {code}
>> karaf@root> 2010-01-08 11:24:47,062 [Thread-5       ] INFO
>> ResourceXmlApplicationContext  - Refreshing
>> org.apache.xbean.spring.context.ResourceXmlApp
>> licationContext@ff87dc: display name
>> [org.apache.xbean.spring.context.ResourceXmlApplicationContext@ff87dc];
>> startup date [Fri Jan 08 11:24:47 CET 201
>> 0]; parent:
>> org.springframework.web.context.support.XmlWebApplicationContext@1930ebb
>> 2010-01-08 11:24:47,093 [Thread-5       ] INFO
>>  XBeanXmlBeanDefinitionReader
>> - Loading XML bean definitions from ServletContext resource [/WEB-INF/a
>> ctivemq.xml]
>> 2010-01-08 11:24:49,718 [Thread-5       ] INFO
>> ResourceXmlApplicationContext  - Bean factory for application context
>> [org.apache.xbean.spring.context
>> .ResourceXmlApplicationContext@ff87dc]:
>>
>> org.springframework.beans.factory.support.DefaultListableBeanFactory@1a6ac39
>> 2010-01-08 11:24:50,593 [Thread-5       ] INFO  BrokerService
>> - Using Persistence Adapter: AMQPersistenceAdapter(activemq-data\localh
>> ost)
>> 2010-01-08 11:24:50,593 [Thread-5       ] INFO  AMQPersistenceAdapter
>> - AMQStore starting using directory: activemq-data\localhost
>> 2010-01-08 11:24:50,687 [Thread-5       ] INFO  KahaStore
>> - Kaha Store using data directory activemq-data\localhost\kr-store\stat
>> e
>> 2010-01-08 11:24:50,843 [Thread-5       ] INFO  AMQPersistenceAdapter
>> - Active data files: []
>> 2010-01-08 11:24:51,046 [Thread-5       ] INFO  BrokerService
>> - ActiveMQ null JMS Message Broker (localhost) is starting
>> 2010-01-08 11:24:51,046 [Thread-5       ] INFO  BrokerService
>> - For help or more information please see: http://activemq.apache.org/
>> 2010-01-08 11:24:51,328 [Thread-5       ] INFO  KahaStore
>> - Kaha Store using data directory activemq-data\localhost\kr-store\data
>>
>> 2010-01-08 11:24:51,906 [JMX connector  ] INFO  ManagementContext
>> - JMX consoles can connect to service:jmx:rmi:///jndi/rmi://localhost:1
>> 099/jmxrmi
>> 2010-01-08 11:24:51,984 [Thread-5       ] INFO
>>  TransportServerThreadSupport
>> - Listening for connections at: tcp://localhost:61616
>> 2010-01-08 11:24:52,000 [Thread-5       ] INFO  TransportConnector
>> - Connector openwire Started
>> 2010-01-08 11:24:52,031 [Thread-5       ] INFO
>>  TransportServerThreadSupport
>> - Listening for connections at: stomp://localhost:61613
>> 2010-01-08 11:24:52,031 [Thread-5       ] INFO  TransportConnector
>> - Connector stomp Started
>> 2010-01-08 11:24:52,109 [Thread-5       ] INFO
>>  TransportServerThreadSupport
>> - Listening for connections at: xmpp://localhost:61222
>> 2010-01-08 11:24:52,109 [Thread-5       ] INFO  TransportConnector
>> - Connector xmpp Started
>> 2010-01-08 11:24:52,109 [Thread-5       ] INFO  NetworkConnector
>> - Network Connector defaultNetwork Started
>> 2010-01-08 11:24:52,109 [Thread-5       ] INFO  BrokerService
>> - ActiveMQ JMS Message Broker (localhost, ID:dell-charles-3782-12629462
>> 91109-0:0) started
>> 2010-01-08 11:24:52,171 [Thread-5       ] INFO  TransportConnector
>> - Connector vm://localhost Started
>> 2010-01-08 11:24:52,750 [Thread-5       ] INFO  WebConsoleStarter
>> - ActiveMQ WebConsole initialized.
>>
>> Exception in thread "SpringOsgiExtenderThread-2"
>> org.springframework.beans.factory.BeanCreationException: Error creating
>> bean
>> with name 'org.apache.ac
>> tivemq.xbean.XBeanBrokerService#0' defined in URL
>> [bundle://59.0:0/META-INF/spring/activemq-broker.xml]: Invocation of init
>> method failed; nested exce
>> ption is java.io.IOException: Transport Connector could not be registered
>> in
>> JMX: Failed to bind to server socket: tcp://0.0.0.0:61616 due to: java.ne
>> t.BindException: Address already in use: JVM_Bind
>>
>> QUESTION :
>>
>> The war file of activemq-console contains in the folder WEB-INF, an
>> activemq.xml file. Is it this file which is in conflict with the
>> activemq-broker.xml files and responsible of this error ?
>> If I remove this file from the WAR, can the activemq web console work ?
>>
>> Regards,
>>
>> Charles Moulliard
>> Senior Enterprise Architect
>> Apache Camel Committer
>>
>> *****************************
>> blog : http://cmoulliard.blogspot.com
>> twitter : http://twitter.com/cmoulliard
>> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>>
>> Apache Camel Group :
>> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>>
>> -----
>> Charles Moulliard
>> SOA Architect
>>
>> My Blog :  http://cmoulliard.blogspot.com/
>> http://cmoulliard.blogspot.com/
>> --
>> View this message in context:
>> http://old.nabble.com/java.io.IOException%3A-Transport-Connector-could-not-be-registered-in-JMX%3A-Failed-to-bind-to-server-socket%3A-tcp%3A--0.0.0.0%3A61616-due-to%3A-java.ne-t.BindException%3A-Address-already-in-use%3A-JVM_Bind-tp27074390p27074390.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
> 
> 
> -----
> Dejan Bosanac
> 
> Open Source Integration - http://fusesource.com/
> ActiveMQ in Action - http://www.manning.com/snyder/
> Blog - http://www.nighttale.net
> 


-----
Charles Moulliard
SOA Architect

My Blog :  http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/  
-- 
View this message in context: http://old.nabble.com/java.io.IOException%3A-Transport-Connector-could-not-be-registered-in-JMX%3A-Failed-to-bind-to-server-socket%3A-tcp%3A--0.0.0.0%3A61616-due-to%3A-java.ne-t.BindException%3A-Address-already-in-use%3A-JVM_Bind-tp27074390p27075724.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.