Ohhh, let me check something.

On 07/02/2013 09:22 PM, Charles Moulliard wrote:
I use the by default config file (coming from distro 3.0.0.RC1) and here is
what we have

#
# The service URL for the JMXConnectorServer
#
serviceUrl = service:jmx:rmi://0.0.0.0:${rmiServerPort}/jndi/rmi://0.0.0.0:
${rmiRegistryPort}/karaf-${karaf.name}

Of course, I don't any error if I replace 0.0.0.0 by 127.0.0.1


On Tue, Jul 2, 2013 at 9:15 PM, Jean-Baptiste Onofré <j...@nanthrax.net>wrote:

Hi Charles,

Karaf should not use 0.0.0.0 (it works fine on my machine).

Could you check what you have in etc/org.apache.karaf.**management.cfg
file ?

Regards
JB


On 07/02/2013 07:57 PM, Charles Moulliard wrote:

Hi,

Don't know if this a bug already reported or not but would like to report
that with Karaf 3.0.0.RC1 when it is started ?

karaf@root()> Exception in thread "JMX Connector Thread
[service:jmx:rmi://
0.0.0.0:44444/jndi/rmi://0.0.**0.0:1099/karaf-root<http://0.0.0.0:44444/jndi/rmi://0.0.0.0:1099/karaf-root>
]"
java.lang.RuntimeException: Could not start JMX connector server
at
org.apache.karaf.management.**ConnectorServerFactory$1.run(**
ConnectorServerFactory.java:**247)
Caused by: java.io.IOException: Cannot bind to URL [rmi://
0.0.0.0:1099/karaf-root]: javax.naming.**ServiceUnavailableException
[Root
exception is java.rmi.ConnectException: Connection refused to host:
0.0.0.0; nested exception is:
java.net.ConnectException: Operation timed out]
at
javax.management.remote.rmi.**RMIConnectorServer.**newIOException(**
RMIConnectorServer.java:827)
at
javax.management.remote.rmi.**RMIConnectorServer.start(**
RMIConnectorServer.java:432)
at
org.apache.karaf.management.**ConnectorServerFactory$1.run(**
ConnectorServerFactory.java:**234)
Caused by: javax.naming.**ServiceUnavailableException [Root exception is
java.rmi.ConnectException: Connection refused to host: 0.0.0.0; nested
exception is:
java.net.ConnectException: Operation timed out]
at com.sun.jndi.rmi.registry.**RegistryContext.bind(**
RegistryContext.java:143)
at
com.sun.jndi.toolkit.url.**GenericURLContext.bind(**
GenericURLContext.java:226)
at javax.naming.InitialContext.**bind(InitialContext.java:419)
at
javax.management.remote.rmi.**RMIConnectorServer.bind(**
RMIConnectorServer.java:644)
at
javax.management.remote.rmi.**RMIConnectorServer.start(**
RMIConnectorServer.java:427)
... 1 more
Caused by: java.rmi.ConnectException: Connection refused to host: 0.0.0.0;
nested exception is:
java.net.ConnectException: Operation timed out
at sun.rmi.transport.tcp.**TCPEndpoint.newSocket(**TCPEndpoint.java:619)
at sun.rmi.transport.tcp.**TCPChannel.createConnection(**
TCPChannel.java:216)
at sun.rmi.transport.tcp.**TCPChannel.newConnection(**
TCPChannel.java:202)
at sun.rmi.server.UnicastRef.**newCall(UnicastRef.java:340)
at sun.rmi.registry.RegistryImpl_**Stub.bind(Unknown Source)
at com.sun.jndi.rmi.registry.**RegistryContext.bind(**
RegistryContext.java:137)
... 5 more
Caused by: java.net.ConnectException: Operation timed out
at java.net.PlainSocketImpl.**socketConnect(Native Method)
at
java.net.**AbstractPlainSocketImpl.**doConnect(**
AbstractPlainSocketImpl.java:**339)
at
java.net.**AbstractPlainSocketImpl.**connectToAddress(**
AbstractPlainSocketImpl.java:**198)
at
java.net.**AbstractPlainSocketImpl.**connect(**
AbstractPlainSocketImpl.java:**182)
at java.net.SocksSocketImpl.**connect(SocksSocketImpl.java:**391)
at java.net.Socket.connect(**Socket.java:579)
at java.net.Socket.connect(**Socket.java:528)
at java.net.Socket.<init>(Socket.**java:425)
at java.net.Socket.<init>(Socket.**java:208)
at
sun.rmi.transport.proxy.**RMIDirectSocketFactory.**createSocket(**
RMIDirectSocketFactory.java:**40)
at
sun.rmi.transport.proxy.**RMIMasterSocketFactory.**createSocket(**
RMIMasterSocketFactory.java:**146)
at sun.rmi.transport.tcp.**TCPEndpoint.newSocket(**TCPEndpoint.java:613)
... 10 more

Regards,


--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com





--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Reply via email to