Bug 367959 - Could not open selected VM debug port (8700) - Android ADT
Summary: Could not open selected VM debug port (8700) - Android ADT
Status: VERIFIED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.8   Edit
Hardware: PC Linux
: P3 critical (vote)
Target Milestone: 3.8 M5   Edit
Assignee: Ayushman Jain CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-05 11:35 EST by Varun Kumar CLA
Modified: 2012-01-23 08:21 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Varun Kumar CLA 2012-01-05 11:35:03 EST 
Build Identifier: Version 3.7.1

Hi have Eclipse 3.7.1 with Android SDK. It was working fine till yesterday (Although I have faced same problem earlier and I had to install OS again for this particular problem). The problem is below - 
I get this message when I open Eclipse - 
Could not open selected VM debug port (8700). Make sure you do not have another instance of DDMS or the eclipse plugin running. If it's being used by something else, choose a new port number in the preferences.
I checked in processes and I can see that even when eclipse is closed, there is one eclipse process running on my machine. I kill that process but I still get same error message. When I launch android emulator, it runs first time but if I reload it, it will stuck on 27% and I have to exit from eclipse.
It is creating a lot of problem Please check.

Reproducible: Always

Steps to Reproduce:
1. Install android SDK
2. Open Eclipse
3. Run an android Project
Comment 1 Ayushman Jain CLA 2012-01-05 12:02:22 EST 
This seems like a problem arising out of the DDMS perspective of ADT. This is not an Eclipse bug, in all probability, but a configuration issue. Can you try this in Window -> Preferences -> Android -> DDMS

- Set Base local debugger port to "8601"
- Check the box that says "Use ADBHOST" and the value should be "127.0.0.1"

Please respond back if this works. I intend to close this is as WORKSFORME, since I don't see this issue with 3.7.1
Comment 2 Varun Kumar CLA 2012-01-05 19:46:21 EST 
It was related to one android SDK configuration. Eclipse developer told me that and that fixed the issue.
Comment 3 Satyam Kandula CLA 2012-01-23 08:21:26 EST 
Verified for 3.8M5