Home/ Questions/Q 8816047
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-14T04:31:33+00:00

I didn’t find information on this annoying problem, and it seem quite common to

  • 0

I didn’t find information on this annoying problem, and it seem quite common to me, so perhaps I’m missing something obvious.

I’m developing a client server application: AppEngine on one side, Android on the other.
If both workspaces are on the same Eclipse, I find it confusing to debug and develop (same Java perspective..).
So I have two separate installations of Eclipse, one for each.

Both Eclipse require a full Google stack each, including ADT.
The problem is that adb is in a race condition, and very often the AppEngine Eclipse wins, and the attached device or emulators appears only on the wrong Eclipse.
I can’t debug until I close that Eclipse and restart adb.

  1. Is there a way to shut down adb in the AppEngine Eclipse?
  2. Is there a better way to develop&debug client server, where both are Google stack?

Thank you!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I think I’ve found a workaround:

    In the Eclipse instance you want to disable DDMS, select: 

    Windows > Preferences > DDMS

    And change the “Base local debugger port to some unused port number (such as 22222).

    There is an error messages about not being able to connect to DDMS, but after dismissing it, it stops competing with the other Eclipse.

    • 0