You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Christopher Mihaly <cm...@hotmail.com> on 2006/07/11 01:01:42 UTC
JMX Connector problems
I am getting Failed to start jmx connector:
javax.naming.NameAlreadyBoundException: jmxrmi [Root exception is
java.rmi.AlreadyBoundException: jmxrmi] in my startup of activemq. I
beleive this is being caused by a server we are running that uses port 1099.
This is the port that I believe activemq jmx server uses by default. I
tried changing the value in conf/activemq.xml or by adding
-Dcom.sun.management.jmxremote.port=1090 to the activemq command line but it
does not make any difference. It still tries to use port 1099.
Strnagely, if I run activemq as a different user than our server, it does
work, and creates a jmx port at 1099.
Not sure what is worng here, and not sure how to change the jmx port. Any
ideas?
Thanks
Chris
--
View this message in context: http://www.nabble.com/JMX-Connector-problems-tf1921424.html#a5260856
Sent from the ActiveMQ - User forum at Nabble.com.
Re: JMX Connector problems
Posted by Christopher Mihaly <cm...@hotmail.com>.
I'm sorry, I never got a stack track or a dump, just a fail message. Is
there something I need to turn on to get this?
I was able to resolve this. I changed the port in the activemq.conf to 1080
(and after a few times, I noticed the whole block is commented out, so
uncommented it) and it now works correctly on port 1080. I do believe the
problem was that port 1099 is being used by another program at the time.
Thanks
Chris
--
View this message in context: http://www.nabble.com/JMX-Connector-problems-tf1921424.html#a5313432
Sent from the ActiveMQ - User forum at Nabble.com.
Re: JMX Connector problems
Posted by bizcenter <bi...@gmail.com>.
connectorPath in ManagementContext is jmxrmi, if you create more instances
of ManageContext, the error above will occur.
change connectorPath (or port).
On Fri, Aug 16, 2013 at 1:02 AM, Ashwini Kuntamukkala [via ActiveMQ] <
ml-node+s2283324n4670430h48@n4.nabble.com> wrote:
> Here is the stacktrace
> DEBUG | Reason for failed jmx connector start | org.ap
>
> ache.activemq.broker.jmx.ManagementContext |
> JMX connector
> java.io.IOException: Cannot bind to URL [rmi://localhost:1099/jmxrmi]:
> javax.nam
>
> ing.NameAlreadyBoundException: jmxrmi [Root exception is
> java.rmi.AlreadyBoundEx
>
> ception: jmxrmi]
> at
> javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConn
>
> ectorServer.java:818)
> at
> javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServ
>
> er.java:431)
> at
> org.apache.activemq.broker.jmx.ManagementContext$1.run(ManagementCont
>
> ext.java:131)
> Caused by: javax.naming.NameAlreadyBoundException: jmxrmi [Root exception
> is jav
>
> a.rmi.AlreadyBoundException: jmxrmi]
> at
> com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:1
>
> 39)
> at
> com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.jav
>
> a:226)
> at javax.naming.InitialContext.bind(InitialContext.java:417)
> at
> javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServe
>
> r.java:639)
> at
> javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServ
>
> er.java:426)
> ... 1 more
> Caused by: java.rmi.AlreadyBoundException: jmxrmi
> at sun.rmi.registry.RegistryImpl.bind(RegistryImpl.java:131)
> at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
> at
> sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:390
>
> )
> at
> sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:248)
> at sun.rmi.transport.Transport$1.run(Transport.java:159)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
> at
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:5
>
> 35)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTranspor
>
> t.java:790)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport
>
> .java:649)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
>
> utor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
>
> .java:908)
> at java.lang.Thread.run(Thread.java:662)
> at
> sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Stream
>
> RemoteCall.java:273)
> at
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:
>
> 251)
> at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:377)
> at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
> at
> com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:1
>
> 37)
> ... 5 more
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://activemq.2283324.n4.nabble.com/JMX-Connector-problems-tp2346442p4670430.html
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805h73@n4.nabble.com
> To unsubscribe from ActiveMQ, click here<http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2341804&code=Yml6Y2VudGVybmV0QGdtYWlsLmNvbXwyMzQxODA0fC02NTk4MzI2MTg=>
> .
> NAML<http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://activemq.2283324.n4.nabble.com/JMX-Connector-problems-tp2346442p4670501.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: JMX Connector problems
Posted by Ashwini Kuntamukkala <ak...@gmail.com>.
Here is the stacktrace
DEBUG | Reason for failed jmx connector start | org.ap
ache.activemq.broker.jmx.ManagementContext | JMX connector
java.io.IOException: Cannot bind to URL [rmi://localhost:1099/jmxrmi]:
javax.nam
ing.NameAlreadyBoundException: jmxrmi [Root exception is
java.rmi.AlreadyBoundEx
ception: jmxrmi]
at
javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConn
ectorServer.java:818)
at
javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServ
er.java:431)
at
org.apache.activemq.broker.jmx.ManagementContext$1.run(ManagementCont
ext.java:131)
Caused by: javax.naming.NameAlreadyBoundException: jmxrmi [Root exception is
jav
a.rmi.AlreadyBoundException: jmxrmi]
at
com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:1
39)
at
com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.jav
a:226)
at javax.naming.InitialContext.bind(InitialContext.java:417)
at
javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServe
r.java:639)
at
javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServ
er.java:426)
... 1 more
Caused by: java.rmi.AlreadyBoundException: jmxrmi
at sun.rmi.registry.RegistryImpl.bind(RegistryImpl.java:131)
at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
at
sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:390
)
at
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:248)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:5
35)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTranspor
t.java:790)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport
.java:649)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:908)
at java.lang.Thread.run(Thread.java:662)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Stream
RemoteCall.java:273)
at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:
251)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:377)
at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
at
com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:1
37)
... 5 more
--
View this message in context: http://activemq.2283324.n4.nabble.com/JMX-Connector-problems-tp2346442p4670430.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: JMX Connector problems
Posted by James Strachan <ja...@gmail.com>.
On 7/11/06, Christopher Mihaly <cm...@hotmail.com> wrote:
>
> I am getting Failed to start jmx connector:
> javax.naming.NameAlreadyBoundException: jmxrmi [Root exception is
> java.rmi.AlreadyBoundException: jmxrmi] in my startup of activemq.
Could you post a full stack trace please?
> I
> beleive this is being caused by a server we are running that uses port 1099.
NameAlreadyBoundException sounds like the connection worked fine, its
an ObjectName is already bound. From you rmail I've just no idea what
kind of ObjectName (there are lots).
--
James
-------
http://radio.weblogs.com/0112098/