[ODLPARENT-6] Running karaf leads to JMX RuntimeException Created: 22/Oct/14  Updated: 25/Jun/20  Resolved: 25/Jun/20

Status: Resolved
Project: odlparent
Component/s: General
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Wojciech Dec Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 2240

 Description   

Starting karaf leads to Exception in thread "JMX Connector Thread [service:jmx:rmi://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:258)
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]

The issue appears due to host name resolution and the use of 0.0.0.0 in org.apache.karaf.management.cfg and
org.apache.karaf.shell.cfg files. Changing these to 127.0.0.1, resolves the issue.

 Comments   
Comment by Wojciech Dec [ 22/Oct/14 ]

Seen on latest helium/stable, but also other recent code pulls.

Comment by Tony Tkacik [ 23/Oct/14 ]

Seems to be related to:

https://wiki.opendaylight.org/view/Potential_Third_Party_Component_Bugs
https://issues.apache.org/jira/browse/KARAF-3147

When doing builds on OS-X, I’ve been unable to run integration tests on both controller and ovsdb projects.
It consistently fails here [1]: Running org.opendaylight.yangtools.featuretest.SingleFeatureTest … Exception in thread "JMX Connector Thread [service:jmx:rmi://0.0.0.0:44444/jndi/" java.lang.RuntimeException: Could not start JMX connector server at org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:258) Caused by: java.io.IOException: Cannot bind to URL [ 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]

Comment by Carol Sanders [ 04/May/15 ]

This bug is part of the project to Move all ADSAL associated component bugs to ADSAL

Comment by Ryan Goulding [ 17/Nov/15 ]

Ping Wojciech to see if this is still an issue in current releases.

Comment by Robert Varga [ 01/Aug/16 ]

Move to odlparent

Comment by Robert Varga [ 25/Jun/20 ]

No response from reporter, not seen anywhere in the infra, closing.

Generated at Wed Feb 07 20:27:21 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.