No route to host: connect
Hello,
what it can be "No route to host: connect"
Best regards
Mark
INFO [2008-02-13 16:43:00,375] Starting WSO2 Mashup Server 1.0.1 (Powered by Apache Axis2)
INFO [2008-02-13 16:43:00,390] Using Java Home : E:\space-JAVA\install\jdk1.5.0_12\jre
INFO [2008-02-13 16:43:00,390] Using Java Version : 1.5.0_12
INFO [2008-02-13 16:43:00,390] Using WSO2 Mashup Server Home : E:\SPACE-~1\WSO2\WSO2-M~1.1\bin\..
INFO [2008-02-13 16:43:02,906] Using Server Info Class: org.wso2.wsas.serverinfo.EmbeddedTomcatServerInfo
INFO [2008-02-13 16:43:11,437] Deploying module: addressing-1.35 - file:/E:/SPACE-~1/WSO2/WSO2-M~1.1/bin/../modules/addressing-1.35.mar
INFO [2008-02-13 16:43:11,656] Deploying module: rahas-1.35 - file:/E:/SPACE-~1/WSO2/WSO2-M~1.1/bin/../modules/rahas-1.35.mar
INFO [2008-02-13 16:43:11,859] Deploying module: rampart-1.35 - file:/E:/SPACE-~1/WSO2/WSO2-M~1.1/bin/../modules/rampart-1.35.mar
INFO [2008-02-13 16:43:12,046] Deploying module: DynamicResponseHandler-1.0 - file:/E:/SPACE-~1/WSO2/WSO2-M~1.1/bin/../modules/wso2dynamic-response-1.0.ma
INFO [2008-02-13 16:43:12,093] Deploying module: wso2mashup-admin - file:/E:/SPACE-~1/WSO2/WSO2-M~1.1/bin/../modules/wso2mashup-adminModule.mar
INFO [2008-02-13 16:43:12,140] Deploying module: wso2mex-2.2 - file:/E:/SPACE-~1/WSO2/WSO2-M~1.1/bin/../modules/wso2mex-2.2.mar
INFO [2008-02-13 16:43:12,375] Deploying module: sandesha2-2.2 - file:/E:/SPACE-~1/WSO2/WSO2-M~1.1/bin/../modules/wso2sandesha2-persistence-2.2.mar
INFO [2008-02-13 16:43:12,390] Deploying module: wso2statistics-2.2 - file:/E:/SPACE-~1/WSO2/WSO2-M~1.1/bin/../modules/wso2statistics-2.2.mar
INFO [2008-02-13 16:43:12,468] Deploying module: wso2throttle-2.2 - file:/E:/SPACE-~1/WSO2/WSO2-M~1.1/bin/../modules/wso2throttle-2.2.mar
INFO [2008-02-13 16:43:12,500] Deploying module: wso2tracer-2.2 - file:/E:/SPACE-~1/WSO2/WSO2-M~1.1/bin/../modules/wso2tracer-2.2.mar
INFO [2008-02-13 16:43:12,500] Deploying module: wso2wsas-admin-2.21 - file:/E:/SPACE-~1/WSO2/WSO2-M~1.1/bin/../modules/wso2wsas-admin-2.21.mar
INFO [2008-02-13 16:43:12,531] Deploying module: wso2xfer-2.2 - file:/E:/SPACE-~1/WSO2/WSO2-M~1.1/bin/../modules/wso2xfer-2.2.mar
INFO [2008-02-13 16:43:12,921] Deploying module: addressing-1.35 - file:/E:/space-JAVA/WSO2/wso2-mashup-server-1.0.1/lib/axis2-1.35.jar
INFO [2008-02-13 16:43:12,937] Deploying module: wso2mex-2.2 - file:/E:/space-JAVA/WSO2/wso2-mashup-server-1.0.1/lib/wso2mex-2.2.jar
INFO [2008-02-13 16:43:12,937] Deploying module: wso2xfer-2.2 - file:/E:/space-JAVA/WSO2/wso2-mashup-server-1.0.1/lib/wso2xfer-2.2.jar
INFO [2008-02-13 16:43:13,046] Job execution threads will use class loader of thread: Thread-1
INFO [2008-02-13 16:43:13,078] Quartz Scheduler v.1.5.2 created.
INFO [2008-02-13 16:43:13,093] RAMJobStore initialized.
INFO [2008-02-13 16:43:13,093] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
INFO [2008-02-13 16:43:13,093] Quartz scheduler version: 1.5.2
INFO [2008-02-13 16:43:13,093] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
INFO [2008-02-13 16:43:16,968] Deploying Web service: archive-validator.aar - file:/E:/SPACE-~1/WSO2/WSO2-M~1.1/bin/../services/archive-validator.aar
INFO [2008-02-13 16:43:17,359] Deploying Web service: wsdlconverter.aar - file:/E:/SPACE-~1/WSO2/WSO2-M~1.1/bin/../services/wsdlconverter.aar
INFO [2008-02-13 16:43:17,390] Deploying Web service: wsdlview.aar - file:/E:/SPACE-~1/WSO2/WSO2-M~1.1/bin/../services/wsdlview.aar
INFO [2008-02-13 16:43:17,953] Deploying Web service: wso2codegen.aar - file:/E:/SPACE-~1/WSO2/WSO2-M~1.1/bin/../services/wso2codegen.aar
INFO [2008-02-13 16:43:18,078] Deploying Web service: wso2mashup-adminServices.aar - file:/E:/SPACE-~1/WSO2/WSO2-M~1.1/bin/../services/wso2mashup-adminSer
s.aar
INFO [2008-02-13 16:43:18,109] Deploying Web service: wso2mashup-coreservices-JSStubGenaratorService.aar - file:/E:/SPACE-~1/WSO2/WSO2-M~1.1/bin/../servic
so2mashup-coreservices-JSStubGenaratorService.aar
INFO [2008-02-13 16:43:18,156] Deploying Web service: wso2mashup-coreservices-servicemetadatalister.aar - file:/E:/SPACE-~1/WSO2/WSO2-M~1.1/bin/../service
o2mashup-coreservices-servicemetadatalister.aar
INFO [2008-02-13 16:43:18,187] Deploying Web service: wso2mashup-coreservices-servicesharinghelper.aar - file:/E:/SPACE-~1/WSO2/WSO2-M~1.1/bin/../services
2mashup-coreservices-servicesharinghelper.aar
INFO [2008-02-13 16:43:18,843] Deploying Web service: wso2mashup-coreservices-sharingservice.aar - file:/E:/SPACE-~1/WSO2/WSO2-M~1.1/bin/../services/wso2m
p-coreservices-sharingservice.aar
INFO [2008-02-13 16:43:19,312] Deploying Web service: wso2mashup-scraperService.aar - file:/E:/SPACE-~1/WSO2/WSO2-M~1.1/bin/../services/wso2mashup-scraper
ice.aar
INFO [2008-02-13 16:43:20,140] Deploying Web service: wso2wsas-administration.aar - file:/E:/SPACE-~1/WSO2/WSO2-M~1.1/bin/../services/wso2wsas-administrat
aar
INFO [2008-02-13 16:43:22,953] Deploying Web service: digit2image.js - {1}
INFO [2008-02-13 16:43:23,390] Deploying Web service: storexml.js - {1}
INFO [2008-02-13 16:43:23,890] Deploying Web service: upgradeChecker.js - {1}
INFO [2008-02-13 16:43:24,296] Deploying Web service: version.js - {1}
INFO [2008-02-13 16:43:25,718]
INFO [2008-02-13 16:43:25,718] Repository : E:\SPACE-~1\WSO2\WSO2-M~1.1\bin\../
ERROR [2008-02-13 16:43:53,015] Could not initialize MBean server
java.io.IOException: Cannot bind to URL [rmi://127.0.0.1:7999/server]: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: E
tion creating connection to: 127.0.0.1; nested exception is:
java.net.NoRouteToHostException: No route to host: connect]
at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
at org.wso2.wsas.DefaultServerInitializer.startJMXService(DefaultServerInitializer.java:159)
at org.wso2.wsas.DefaultServerInitializer.init(DefaultServerInitializer.java:135)
at org.wso2.wsas.ServerManager.runIntializers(ServerManager.java:222)
at org.wso2.wsas.ServerManager.start(ServerManager.java:127)
at org.wso2.wsas.MainServlet.start(MainServlet.java:249)
at org.wso2.mashup.transport.MainServlet.start(MainServlet.java:36)
at org.wso2.wsas.MainServlet.init(MainServlet.java:185)
at org.wso2.mashup.transport.MainServlet.init(MainServlet.java:51)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:932)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3915)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4176)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
at org.wso2.wsas.TomcatRepositoryListener.run(TomcatRepositoryListener.java:107)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: Exception creating connection to: 127.0.0.1; nested exception
java.net.NoRouteToHostException: No route to host: connect]
at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:122)
at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:208)
at javax.naming.InitialContext.bind(InitialContext.java:359)
at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:635)
at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427)
... 17 more
Caused by: java.rmi.ConnectIOException: Exception creating connection to: 127.0.0.1; nested exception is:
java.net.NoRouteToHostException: No route to host: connect
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:587)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
- Login or register to post comments
- Printer friendly version
- 396 reads











You can get the server running by turning off JMX
Hi Mark,
It appears that your localhost IP address [127.0.0.1] is somehow not available/reachable. It's definitely not a port conflict, which is generally the more common scenario, as the error message is different.
Anyway, to start off, you should be able to get your Mashup Server running by turning off JMX. Just comment the line as shown below in your server.xml file found in the conf directory of your installation.
<!--<JMX>7999</JMX>-->
Please do let me know if you still continue to have problems after disabling JMX and also what may be non-typical in your TCP/IP setup.
Bye,
Channa.