When start a BrokerService, I got a WARN log saying:
JMX connector WARN
(org.apache.activemq.broker.jmx.ManagementContext.run:135) - Failed to
start jmx connector: Cannot bind to URL [rmi://localhost:1099/jmxrmi]:
javax.naming.NoInitialContextException: Need to specify class name in
I wonder, does it work when you use this configuration:
There is generally no need to set useJmx="true" in the broker element. At least
I never specify it.
Regards,
Torsten Mielke
tors...@fusesource.com
tmie...@blogspot.com
I have managementContext defined.
Any suggestions?
WARN org.apache.activemq.broker.jmx.ManagementContext [JMX
connector]: Failed to start jmx connector: Cannot bind to URL
[rmi://localhost:1099/jmxrmi]: javax.naming.NameAlreadyBoundException:
jmxrmi [Root exception is java.rmi.AlreadyBound
Found a way to monitor amq mbeans via jboss jmx-console.
Instructions given on wiki (Integrating Apache ActiveMQ with JBoss) resulted
with:
[ManagementContext ] Failed to start jmx connector: Cannot bind to URL
[rmi://localhost:1099/jmxrmi]: javax.naming.CommunicationException [Root
exception
Hi,
Does anyone have ever experience this ?
I have tried to search in forum, and googled around, but found no help.
11:41:27,191 WARN [ManagementContext] Failed to start jmx connector: Cannot
bind to URL [rmi://localhost:1099/jmxrmi]:
javax.naming.CommunicationException [Root exception is
] INFO TransportConnector
> - Connector openwire Started
> 2007-06-14 12:32:38,593 [JMX connector ] WARN ManagementContext
> - Failed to start jmx connector: javax.naming.CommunicationException [Root
> exception is java.rmi.ServerException: RemoteException occur
://centraldb:61616
2007-06-14 12:32:38,453 [main ] INFO TransportConnector
- Connector openwire Started
2007-06-14 12:32:38,593 [JMX connector ] WARN ManagementContext
- Failed to start jmx connector: javax.naming.CommunicationException [Root
exception is
