Error in jetty setup : Failed to connect to remote VM. Connection refused. Connection refused: connect ?
Hello,
I am trying Jetty server setup on CLM 6.0.1 which is installed on WAS 8.5.5.
I have successfully completed WorskshopSetup and now stuck on the debug step with the error "Failed to connect to remote VM. Connection refused.
Connection refused: connect"
"java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:412)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:271)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:258)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:376)
at java.net.Socket.connect(Socket.java:546)
at java.net.Socket.connect(Socket.java:495)
at java.net.Socket.<init>(Socket.java:392)
at java.net.Socket.<init>(Socket.java:203)
at org.eclipse.jdi.internal.connect.SocketTransportService$2.run(SocketTransportService.java:136)
at java.lang.Thread.run(Thread.java:767)"
Any solution for this error ?
Thanks
I am trying Jetty server setup on CLM 6.0.1 which is installed on WAS 8.5.5.
I have successfully completed WorskshopSetup and now stuck on the debug step with the error "Failed to connect to remote VM. Connection refused.
Connection refused: connect"
"java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:412)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:271)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:258)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:376)
at java.net.Socket.connect(Socket.java:546)
at java.net.Socket.connect(Socket.java:495)
at java.net.Socket.<init>(Socket.java:392)
at java.net.Socket.<init>(Socket.java:203)
at org.eclipse.jdi.internal.connect.SocketTransportService$2.run(SocketTransportService.java:136)
at java.lang.Thread.run(Thread.java:767)"
Any solution for this error ?
Thanks
One answer
This question does not make a lot of sense to me.
Please provide the step in the workshop you are stuck.
If you are talking about launching a Jetty based development server, I would expect more log information.
If you are trying to connect remotely to WAS to debug an extension, the workshop is basically done for Tomcat and the same steps work with WAS Liberty and there is no notion of any other WAS app server based debug in it.
Debugging might or might not work with the description with a full WAS (I doubt it), in any case the changes to the server.startup.bat that are described in the workshop would have to be done in the WAS Admin console.
I would suggest you follow the workshop closely. Since there is no description for 6.0.1 yet, here what I have seen with WAS liberty in 6.0.1:
You can basically follow the Tomcat description and replace Tomcat with WAS liberty and it works.
Please provide the step in the workshop you are stuck.
If you are talking about launching a Jetty based development server, I would expect more log information.
If you are trying to connect remotely to WAS to debug an extension, the workshop is basically done for Tomcat and the same steps work with WAS Liberty and there is no notion of any other WAS app server based debug in it.
Debugging might or might not work with the description with a full WAS (I doubt it), in any case the changes to the server.startup.bat that are described in the workshop would have to be done in the WAS Admin console.
I would suggest you follow the workshop closely. Since there is no description for 6.0.1 yet, here what I have seen with WAS liberty in 6.0.1:
You can basically follow the Tomcat description and replace Tomcat with WAS liberty and it works.
Comments
