Getting error trying to debug in VSCode with the Adobe Coldfusion extension

[lerxst3]

I keep getting this error: 

ERROR: transport error 202: bind failed: Address already in use ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [:732]

However, nothing is running on that port except CF!  So what is it complaining about?  Do I have something misconfigured?  

I have CF 2021 running on my localhost w/ default settings (so it's running on localhost:8500).  In VSCode, I have the server set as localhost:8500.  

Thanks!  

[elegant_glamour7397]

When I checked the "Use Windows Service to start/stop the server. (Not available for J2EE configuration)" checkbox in the Server Settings for the CF Server in VS Code, it worked.

[Charlie Arehart]

@elegant_glamour7397, when you say your step "worked", do you mean you'd been getting the exact error lerxst3 reported? If so, are you saying you changed that service setting from unchecked to checked? 

To be clear, that setting simply controls how cfb would attempt to start the named cf instance, if you used the feature in cfb to try to start (or stop) cf. I can't see at all how merely checking (or unchecking) that setting (alone) could have any impact.

Hope you can elaborate a bit more. I appreciate you're trying to help @lerxst3 and others following along. 

[elegant_glamour7397]

When I say it "worked", I mean that the Adobe ColdFusion Extension previously gave the same exact error in the original message, and when I used the option describe above, I no longer received the error and I was able to execute a ColdFusion Security Scan successfully.

[Charlie Arehart]

@lerxst3, a couple things.

First, when you say "that port", what do you mean? 8500 or something else? It's unclear from your post. 

Secind, that error would normally happen when starting cf. You refer to this as happening when you try to user the debug feature of cfb. Do you mean you are using the feature within the cf servers ui to try to start the instance? If it's already running, that's not neededa (and the debug feature does not itself try to start cf). 

To be specific, the port conflict indicated by that error (and its reference to jdwp) is NOT about the port 8500 you named...though it could be affected by your having that cf instance running.

It's about the debug port that Cf would listen on to be talked to by this debugger in cfb. The default is 5005. You can find it indicated in the cf admin debugger settings page and in the jvm.config file which gets modified by that admin page. 

As for finding what's listening on that port, when you get this error, there are cli and ui tools for each os. Tell us what you're using and i/we can offer more (or you may know, or you may tell us that you no longer get the error.) 

[BKBK]

@lerxst3 , JDWP stands for Java Debug Wire Protocol. This is the protocol used for communication between the debugger of a Java application, such as ColdFusion, and the Java Virtual Machine. This communication requires a dedicated port. In ColdFusion the JVM settings to enable debugging are located in /cfusion/bin/jvm.config, and look like this:

As you can see, the debug port in this case is 5005. Find out what your own debug port is.

The error you're getting suggests one of two things:

1.  Another process is already listening on the port that your ColdFusion application is using for debugging (maybe another ColdFusion instance or another Java application).
2.   You started debugging twice, and the previous JVM hadn’t released the port yet.
   
   Case 1 is the more common. So let's assume another process is using the port. You can identify the process.
   
   Take, for example, my debugging port, 5005. I am on Windows. To identify the process running on port 5005, I open Windows PowerShell as Administrator, and run the following command
   

   Get-Process -Id (Get-NetTCPConnection -LocalPort 5005).OwningProcess​

   The result is:
   

   Note that the result includes the ProcessName and ID. I am happy with process 15728.
   
   But let's suppose, on the contrary, that a process with that ID (15728) was in the way of my debugging. Then I could "kill" it.
   
   To do so, I would just have to run the following command within the same PowerShell window:

    taskkill /PID 15728

   

   Killing a task might lead to other issues. An alternative, perhaps simpler, way to avoid the port conflict is to change ColdFusion's JDWP port. 
   Again using my case for example, the steps would be:
   1.  In jvm.config, change the port("address") value from 5005 to, say, 5007. (Of course, after having confirmed that the port 5007 is free.)

   # Arguments to VM
   java.args=-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5007 -server ...etc

   
   2.  Restart ColdFusion.