Starting a server in debug mode from eclipse

[#1]

Hi

I just created a new project using Eclipse Mars and the archetype 10 in order to deploy it to AEM 6.2 instance.

I'm using the "AEM Developer Tools for Eclipse"  and until 6.1 everything was great, but once I tried (with 6.2) to add a new server in eclipse and start it in debug mode I had this:

org.apache.commons.httpclient.HttpException: Got status code 404 for call to http://localhost:4502/system/sling/tooling/sourceReferences.json
org.apache.commons.httpclient.HttpException: Got status code 404 for call to http://localhost:4502/system/sling/tooling/sourceReferences.json

I can start the server using "Start" mode and deploy all the project (default project in a clean instance) but I can not even start the server in debug mode ....

Can someone Help me on this???

Thanks!!

[#2]

There may be a bug with 6.2. If you have it working on 6.1, then it should work the same.  

[#3]

I am checking with some users that i know that use the plug-in. I personally prefer Maven and Command line to compile projects

[#4]

Hi,

Refer [1] and see if that works for you

[1] http://stackoverflow.com/questions/38388879/setup-aem-in-eclipse-and-create-a-project

[#5]

Hi 

I would ask you to please verify the PORT and Debug PORT.

Make sure that AEM running in debug mode before you connect with eclipse and has the same debug port configured.

Also try the link provided by Lokesh :- http://stackoverflow.com/questions/38388879/setup-aem-in-eclipse-and-create-a-project

I hope this would help you.

~kautuk

[#6]

Any luck? I am facing the same issue on 6.2

[#7]

I'm having virtually the same problem with Eclipse Neon and AEM 6.2.  Getting 500 error trying to access sourceReferences.json when starting AEM (via Eclipse) in Debug mode.

- Jason

[#8]

- Double click the server instance in eclipse

- Expand the Debug section

- Uncheck the option Resolve sources when connecting

​- Save and restart the Server and it should work

[#9]

This works with AEM 6.3 as well. Unchecking the "Resolve sources..." Fixes the issue as Vaibhav suggested. Thanks

[#10]

Uncheck the option Resolve sources when connecting - this step did the magic. Thanks Vaibhav