Should RTC Extensions Workshop work with RTC 6.0.6.1 and Eclipse Neon.3 Release (4.6.3)
![](http://jazz.net/_images/myphoto/a28854a1e978fad22bdf570a24ccda32.jpg)
The RTC Extensions Workshop is failing at step 33 Attach the Eclipse debugger to the RTC development server.
Problem occurred when click Debug in Debug Configurations:
The cmd window from server.startup.bat displayed the following lines:
Listening for transport dt_docket at address: 52674
Problem Occurred dialog:
Error Log entry:
!ENTRY org.eclipse.jdt.launching 4 113 2021-03-17 10:41:17.317
!MESSAGE Failed to connect to remote VM. Connection refused.
!STACK 0
java.net.ConnectException: Connection refused: connect
at java.net.DualStackPlainSocketImpl.connect0(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:90)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:380)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:236)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:218)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:183)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:403)
at java.net.Socket.connect(Socket.java:666)
at java.net.Socket.connect(Socket.java:606)
at java.net.Socket.<init>(Socket.java:469)
at java.net.Socket.<init>(Socket.java:239)
at org.eclipse.jdi.internal.connect.SocketTransportService$2.run(SocketTransportService.java:148)
at java.lang.Thread.run(Thread.java:812)
Accepted answer
![](http://jazz.net/_images/myphoto/a28854a1e978fad22bdf570a24ccda32.jpg)
This has worked for me with the versions mentioned above. Some observations:
1. The workshop defines and uses a different port.
2. I have seen an issue with the remote debugging with the latest 7.0.1 and 7.0.2 that start with newer Java versions, that crash the server when starting it with the added lines for debugging. See https://rsjazz.wordpress.com/2021/03/03/ewm-rtc-extensions-workshop-works-with-ewm-7-0-x/
3. I have found a different mechanism to do the debugging, but I am still verifying if I can adjust that a bit closer to the current behavior. I have not published a how to yet.
I would suggest you remove the lines you added to the server.startup.bat that enable remote debugging and skip this step in the lab. The issue will not prevent any other labs I am aware of.
Comments
![](http://jazz.net/_images/myphoto/e5e63d5878217b64611c1df9401b7cd3.jpg)
https://rsjazz.wordpress.com/2021/03/18/ewm-extensions-workshop-remote-debugging-in7-0-x/ shows how to use the built in debug option. This is also available in 6.0.6.1.