Remote Debugging: Breakpoints not getting hit..

Hi Everyone, we are trying to get CFBuilder debugging against remote CF MX8 servers.  We've gotten a good deal of the way there but are hung up with an issue that probably has to do with incorrectly mapping the setup instructions found here into our particular environment.

So for the brave and willing here are the details...

We followed the setup instructions in the CF_builder_beta_help.pdf document for Remote Server Setup.

See here:

<snip>

Create a remote server:

Before you create a remote server in ColdFusion Builder, do the following tasks.

Run the Admin server instance in the remote ColdFusion server

Depending on your remote server version and configuration, do the necessary tasks.

Standalone remote server version 7.0.2, 8.0.1

Unzip the file AdminServerComponents.zip to {CFHome}

The following files are copied to {cfhome}/runtime/bin:

adminstart.sh

The Admin Server instance is copied to {cfhome}/runtime/servers

Go to {cfhome}/runtime/bin and run adminstart.sh (for Mac OS/Unix)

</snip>

This brings up a webserver on port 8000.  When I hit it, am getting:

500 - There is no web application configured to service your request.

--------------------------------------------------------------------------------------------------

The net effect of this is that I get this when CFBuilder attempts to hook up to the server:

[cfmx.blah.com], Error, 09/22 at 05:50:44, Connection reset by peer: socket write error

[cfmx.blah.com], (09/22 at 05:50:44): Server is available. Getting server settings from Server

----------------------------------------------------------------------------------------------------

Some environmental information that might help those of you who've read this far.

1.  The CF instance is being hosted by Sun Java One Server, not on builtin webserver.  (Is using AdminComponents's adminstart.sh proper for this env?)

2.  CF is installed StandAlone.

3.  I can see the ColdFusin Data Sources for this cfmx.blah.com just fine in the RDS DataViewer.

4.  We have enabled LineDebugging in CFAdministrator.

The only thing that appears not to be working is that my breakpoints are not getting hit when I debug.  This is of course the whole reason for this excercise..

I suspect that this line in the above Console log holds the reason: [cfmx.blah.com], Error, 09/22 at 05:50:44, Connection reset by peer: socket write error