[JBoss JIRA] (ARQ-1534) There is no way how to set server port of Android Debug Bridge
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1534?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic resolved ARQ-1534.
------------------------------------
Resolution: Won't Fix
The port where Android debug bridge server component communicates when trying to connect to adb clients on emulator can be set by environment property ANDROID_ADB_SERVER_PORT.
This property has to be environment one. You can set environment property e.g. by exporting it in your shell by export command or you can setup your pom.xml as specified in the comment to this issue. Every emulator in that test run will talk to that server instance so it should not collide with the clients of Eclipse's DDMS.
> There is no way how to set server port of Android Debug Bridge
> --------------------------------------------------------------
>
> Key: ARQ-1534
> URL: https://issues.jboss.org/browse/ARQ-1534
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha2
> Reporter: Karel Piwko
> Assignee: Stefan Miklosovic
>
> *Given*:
> I have Android tooling installed in Eclipse/JBDS.
> *When:*
> I use Droidium in tests fro IDE.
> *Expect*:
> No having any errors in DDMS output in IDE.
> *Additional information*:
> It looks like that the problem is that Droidium does not allow to set android bridge server port and hence DDMS is already connected to given port. This leads to various errors logged, as DDMS is not prepared to handle external process changing it's environment on the fly.
> See AndroidDebugBridge.determineAndValidateAdbPort() method for more details. While Drodium allows you to change adbPort for running emulator, it always runs the bridge on default port 5037.
> We need a way how to change this server port in Droidium configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (ARQ-1534) There is no way how to set server port of Android Debug Bridge
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1534?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic edited comment on ARQ-1534 at 10/26/13 7:40 PM:
------------------------------------------------------------------
[~kpiwko]
In connection to this problem, it is good idea to clarify whole adb connections related process. From https://developer.android.com/tools/help/adb.html :
{quote}
Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device. It is a client-server program that includes three components:
*A client*, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
*A server*, which runs as a background process on your development machine. *The server manages communication between the client and the adb daemon running on an emulator or device*.
*A daemon*, which runs as a background process on each emulator or device instance.
When you start an adb client, the client first checks whether there is an adb server process already running. If there isn't, it starts the server process. *When the server starts, it binds to local TCP port 5037* and listens for commands sent from adb clients—*all adb clients use port 5037 to communicate with the adb server*.
The server then sets up connections to all running emulator/device instances. *It locates emulator/device instances by scanning odd-numbered ports in the range 5555 to 5585, the range used by emulators/devices. When the server finds an adb daemon, it sets up a connection to that port.* Note that each emulator/device instance acquires a pair of sequential ports — an even-numbered port for console connections and an odd-numbered port for adb connections.
{quote}
In order to specify adb server port where Android debug bridge should be bound to, you have to set environment variable
{code}
ANDROID_ADB_SERVER_PORT
{code}
to whatever port you want. After it, when new instance of adb server is started, it is bound to that specified server port or to 5037 by default when not specified differently.
When you want to start adb server manually on the command line with non-default port, you have to do it like this
{code}
adb -P 10000 fork-server server
{code}
so by specifying different port every time, you have multiple instances of adb bridge which in turn means that when you are about to start an emulator, ddmlib tries to connect its client to ANDROID_ADB_SERVER_PORT or by default to 5037.
You can set adbPort configuration property right now in arquillian.xml but it serves as "odd-numbered" port mentioned above where emulator instance is bound so that started server daemon on arbitrary port (by env port set) connects afterwards.
It seems that when ANDROID_ADB_SERVER_PORT is set and tests are executed, emulator adb client starts to communicate with server instance bound to that port so it seems that it does not collide with Eclipse.
Moreover, I noticed that error messages are written out to Eclipse console output only when Android emulator is started and I kill the only running instance of Android debug bridge (so no adb server is running) so Eclipse's adb client listens to void which is the cause of that error output.
In addition, that environment property is read from System.getenv and if we wanted to be able to change that port from arquillian.xml, there would have to be kind of ugly hack to modify environment property map after JVM has read that since it can not be modified once created (by default, but it can be hacked afterwards and the result of this is rather questionable).
>From Maven point of view, the way to set that environment property (note the difference between system property), it can be e.g. set like
{code}
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.16</version>
<configuration>
<forkMode>always</forkMode>
<environmentVariables>
<ANDROID_ADB_SERVER_PORT>10000</ANDROID_ADB_SERVER_PORT>
</environmentVariables>
</configuration>
</plugin>
</plugin>
</build>
{code}
When doing so, every emulator in that test run will communicate with ADB server which is started on port 10000 if it is already not.
was (Author: smikloso):
[~kpiwko]
In connection to this problem, it is good idea to clarify whole adb connections related process. From https://developer.android.com/tools/help/adb.html :
{quote}
Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device. It is a client-server program that includes three components:
*A client*, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
*A server*, which runs as a background process on your development machine. *The server manages communication between the client and the adb daemon running on an emulator or device*.
*A daemon*, which runs as a background process on each emulator or device instance.
When you start an adb client, the client first checks whether there is an adb server process already running. If there isn't, it starts the server process. *When the server starts, it binds to local TCP port 5037* and listens for commands sent from adb clients—*all adb clients use port 5037 to communicate with the adb server*.
The server then sets up connections to all running emulator/device instances. *It locates emulator/device instances by scanning odd-numbered ports in the range 5555 to 5585, the range used by emulators/devices. When the server finds an adb daemon, it sets up a connection to that port.* Note that each emulator/device instance acquires a pair of sequential ports — an even-numbered port for console connections and an odd-numbered port for adb connections.
{quote}
In order to specify adb server port where Android debug bridge should be bound to, you have to set environment variable
{code}
ANDROID_ADB_SERVER_PORT
{code}
to whatever port you want. After it, when new instance of adb server is started, it is bound to that specified server port or to 5037 by default when not specified differently.
When you want to start adb server manually on the command line with non-default port, you have to do it like this
{code}
adb -P 10000 fork-server server
{code}
so by specifying different port every time, you have multiple instances of adb bridge which in turn means that when you are about to start an emulator, ddmlib tries to connect its client to ANDROID_ADB_SERVER_PORT or by default to 5037.
You can set adbPort configuration property right now in arquillian.xml but it serves as "odd-numbered" port mentioned above where emulator instance is bound so that started server daemon on arbitrary port (by env port set) connects afterwards.
It seems that when ANDROID_ADB_SERVER_PORT is set and tests are executed, emulator adb client starts to communicate with server instance bound to that port so it seems that it does not collide with Eclipse.
Moreover, I noticed that error messages are written out to Eclipse console output only when Android emulator is started and I kill the only running instance of Android debug bridge (so no adb server is running) so Eclipse's adb client listens to void which is the cause of that error output.
In addition, that environment property is read from System.getenv and if we wanted to be able to change that port from arquillian.xml, there would have to be kind of ugly hack to modify environment property map after JVM has read that since it can not be modified once created (by default, but it can be hacked afterwards and the result of this is rather questionable).
>From Maven point of view, the way to set that environment property (note the difference between system property), it can be e.g. set like
{code}
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.16</version>
<configuration>
<forkMode>always</forkMode>
<environmentVariables>
<ANDROID_ADB_SERVER_PORT>10000</ANDROID_ADB_SERVER_PORT>
</environmentVariables>
</configuration>
</plugin>
</plugin>
</build>
{code}
> There is no way how to set server port of Android Debug Bridge
> --------------------------------------------------------------
>
> Key: ARQ-1534
> URL: https://issues.jboss.org/browse/ARQ-1534
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha2
> Reporter: Karel Piwko
> Assignee: Stefan Miklosovic
>
> *Given*:
> I have Android tooling installed in Eclipse/JBDS.
> *When:*
> I use Droidium in tests fro IDE.
> *Expect*:
> No having any errors in DDMS output in IDE.
> *Additional information*:
> It looks like that the problem is that Droidium does not allow to set android bridge server port and hence DDMS is already connected to given port. This leads to various errors logged, as DDMS is not prepared to handle external process changing it's environment on the fly.
> See AndroidDebugBridge.determineAndValidateAdbPort() method for more details. While Drodium allows you to change adbPort for running emulator, it always runs the bridge on default port 5037.
> We need a way how to change this server port in Droidium configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (ARQ-1534) There is no way how to set server port of Android Debug Bridge
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1534?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic edited comment on ARQ-1534 at 10/26/13 7:38 PM:
------------------------------------------------------------------
[~kpiwko]
In connection to this problem, it is good idea to clarify whole adb connections related process. From https://developer.android.com/tools/help/adb.html :
{quote}
Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device. It is a client-server program that includes three components:
*A client*, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
*A server*, which runs as a background process on your development machine. *The server manages communication between the client and the adb daemon running on an emulator or device*.
*A daemon*, which runs as a background process on each emulator or device instance.
When you start an adb client, the client first checks whether there is an adb server process already running. If there isn't, it starts the server process. *When the server starts, it binds to local TCP port 5037* and listens for commands sent from adb clients—*all adb clients use port 5037 to communicate with the adb server*.
The server then sets up connections to all running emulator/device instances. *It locates emulator/device instances by scanning odd-numbered ports in the range 5555 to 5585, the range used by emulators/devices. When the server finds an adb daemon, it sets up a connection to that port.* Note that each emulator/device instance acquires a pair of sequential ports — an even-numbered port for console connections and an odd-numbered port for adb connections.
{quote}
In order to specify adb server port where Android debug bridge should be bound to, you have to set environment variable
{code}
ANDROID_ADB_SERVER_PORT
{code}
to whatever port you want. After it, when new instance of adb server is started, it is bound to that specified server port or to 5037 by default when not specified differently.
When you want to start adb server manually on the command line with non-default port, you have to do it like this
{code}
adb -P 10000 fork-server server
{code}
so by specifying different port every time, you have multiple instances of adb bridge which in turn means that when you are about to start an emulator, ddmlib tries to connect its client to ANDROID_ADB_SERVER_PORT or by default to 5037.
You can set adbPort configuration property right now in arquillian.xml but it serves as "odd-numbered" port mentioned above where emulator instance is bound so that started server daemon on arbitrary port (by env port set) connects afterwards.
It seems that when ANDROID_ADB_SERVER_PORT is set and tests are executed, emulator adb client starts to communicate with server instance bound to that port so it seems that it does not collide with Eclipse.
Moreover, I noticed that error messages are written out to Eclipse console output only when Android emulator is started and I kill the only running instance of Android debug bridge (so no adb server is running) so Eclipse's adb client listens to void which is the cause of that error output.
In addition, that environment property is read from System.getenv and if we wanted to be able to change that port from arquillian.xml, there would have to be kind of ugly hack to modify environment property map after JVM has read that since it can not be modified once created (by default, but it can be hacked afterwards and the result of this is rather questionable).
>From Maven point of view, the way to set that environment property (note the difference between system property), it can be e.g. set like
{code}
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.16</version>
<configuration>
<forkMode>always</forkMode>
<environmentVariables>
<ANDROID_ADB_SERVER_PORT>10000</ANDROID_ADB_SERVER_PORT>
</environmentVariables>
</configuration>
</plugin>
</plugin>
</build>
{code}
was (Author: smikloso):
[~kpiwko]
In connection to this problem, it is good idea to clarify whole adb connections related process. From https://developer.android.com/tools/help/adb.html :
{quote}
Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device. It is a client-server program that includes three components:
*A client*, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
*A server*, which runs as a background process on your development machine. *The server manages communication between the client and the adb daemon running on an emulator or device*.
*A daemon*, which runs as a background process on each emulator or device instance.
When you start an adb client, the client first checks whether there is an adb server process already running. If there isn't, it starts the server process. *When the server starts, it binds to local TCP port 5037* and listens for commands sent from adb clients—*all adb clients use port 5037 to communicate with the adb server*.
The server then sets up connections to all running emulator/device instances. *It locates emulator/device instances by scanning odd-numbered ports in the range 5555 to 5585, the range used by emulators/devices. When the server finds an adb daemon, it sets up a connection to that port.* Note that each emulator/device instance acquires a pair of sequential ports — an even-numbered port for console connections and an odd-numbered port for adb connections.
{quote}
In order to specify adb server port where Android debug bridge should be bound to, you have to set environment variable
{code}
ANDROID_ADB_SERVER_PORT
{code}
to whatever port you want. After it, when new instance of adb server is started, it is bound to that specified server port or to 5037 by default when not specified differently.
When you want to start adb server manually on the command line with non-default port, you have to do it like this
{code}
adb -P 10000 fork-server server
{code}
so by specifying different port every time, you have multiple instances of adb bridge which in turn means that when you are about to start an emulator, ddmlib tries to connect its client to ANDROID_ADB_SERVER_PORT or by default to 5037.
You can set adbPort configuration property right now in arquillian.xml but it serves as "odd-numbered" port mentioned above where emulator instance is bound so that started server daemon on arbitrary port (by env port set) connects afterwards.
It seems that when ANDROID_ADB_SERVER_PORT is set and tests are executed, emulator adb client starts to communicate with server instance bound to that port so it seems that it does not collide with Eclipse.
Moreover, I noticed that error messages are written out to Eclipse console output only when Android emulator is started and I kill the only running instance of Android debug bridge (so no adb server is running) so Eclipse's adb client listens to void which is the cause of that error output.
In addition, that environment property is read from System.getenv and if we wanted to be able to change that port from arquillian.xml, there would have to be kind of ugly hack to modify environment property map after JVM has read that since it can not be modified once created (by default, but it can be hacked afterwards and the result of this is rather questionable).
> There is no way how to set server port of Android Debug Bridge
> --------------------------------------------------------------
>
> Key: ARQ-1534
> URL: https://issues.jboss.org/browse/ARQ-1534
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha2
> Reporter: Karel Piwko
> Assignee: Stefan Miklosovic
>
> *Given*:
> I have Android tooling installed in Eclipse/JBDS.
> *When:*
> I use Droidium in tests fro IDE.
> *Expect*:
> No having any errors in DDMS output in IDE.
> *Additional information*:
> It looks like that the problem is that Droidium does not allow to set android bridge server port and hence DDMS is already connected to given port. This leads to various errors logged, as DDMS is not prepared to handle external process changing it's environment on the fly.
> See AndroidDebugBridge.determineAndValidateAdbPort() method for more details. While Drodium allows you to change adbPort for running emulator, it always runs the bridge on default port 5037.
> We need a way how to change this server port in Droidium configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (ARQ-1534) There is no way how to set server port of Android Debug Bridge
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1534?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic edited comment on ARQ-1534 at 10/26/13 7:21 PM:
------------------------------------------------------------------
[~kpiwko]
In connection to this problem, it is good idea to clarify whole adb connections related process. From https://developer.android.com/tools/help/adb.html :
{quote}
Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device. It is a client-server program that includes three components:
*A client*, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
*A server*, which runs as a background process on your development machine. *The server manages communication between the client and the adb daemon running on an emulator or device*.
*A daemon*, which runs as a background process on each emulator or device instance.
When you start an adb client, the client first checks whether there is an adb server process already running. If there isn't, it starts the server process. *When the server starts, it binds to local TCP port 5037* and listens for commands sent from adb clients—*all adb clients use port 5037 to communicate with the adb server*.
The server then sets up connections to all running emulator/device instances. *It locates emulator/device instances by scanning odd-numbered ports in the range 5555 to 5585, the range used by emulators/devices. When the server finds an adb daemon, it sets up a connection to that port.* Note that each emulator/device instance acquires a pair of sequential ports — an even-numbered port for console connections and an odd-numbered port for adb connections.
{quote}
In order to specify adb server port where Android debug bridge should be bound to, you have to set environment variable
{code}
ANDROID_ADB_SERVER_PORT
{code}
to whatever port you want. After it, when new instance of adb server is started, it is bound to that specified server port or to 5037 by default when not specified differently.
When you want to start adb server manually on the command line with non-default port, you have to do it like this
{code}
adb -P 10000 fork-server server
{code}
so by specifying different port every time, you have multiple instances of adb bridge which in turn means that when you are about to start an emulator, ddmlib tries to connect its client to ANDROID_ADB_SERVER_PORT or by default to 5037.
You can set adbPort configuration property right now in arquillian.xml but it serves as "odd-numbered" port mentioned above where emulator instance is bound so that started server daemon on arbitrary port (by env port set) connects afterwards.
It seems that when ANDROID_ADB_SERVER_PORT is set and tests are executed, emulator adb client starts to communicate with server instance bound to that port so it seems that it does not collide with Eclipse.
Moreover, I noticed that error messages are written out to Eclipse console output only when Android emulator is started and I kill the only running instance of Android debug bridge (so no adb server is running) so Eclipse's adb client listens to void which is the cause of that error output.
In addition, that environment property is read from System.getenv and if we wanted to be able to change that port from arquillian.xml, there would have to be kind of ugly hack to modify environment property map after JVM has read that since it can not be modified once created (by default, but it can be hacked afterwards and the result of this is rather questionable).
was (Author: smikloso):
[~kpiwko]
In connection to this problem, it is good idea to clarify whole adb connections related process. From https://developer.android.com/tools/help/adb.html :
{quote}
Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device. It is a client-server program that includes three components:
*A client*, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
*A server*, which runs as a background process on your development machine. *The server manages communication between the client and the adb daemon running on an emulator or device*.
*A daemon*, which runs as a background process on each emulator or device instance.
When you start an adb client, the client first checks whether there is an adb server process already running. If there isn't, it starts the server process. *When the server starts, it binds to local TCP port 5037* and listens for commands sent from adb clients—*all adb clients use port 5037 to communicate with the adb server*.
The server then sets up connections to all running emulator/device instances. *It locates emulator/device instances by scanning odd-numbered ports in the range 5555 to 5585, the range used by emulators/devices. When the server finds an adb daemon, it sets up a connection to that port.* Note that each emulator/device instance acquires a pair of sequential ports — an even-numbered port for console connections and an odd-numbered port for adb connections.
{quote}
In order to specify adb server port where Android debug bridge should be bound to, you have to set environment variable
{code}
ANDROID_ADB_SERVER_PORT
{code}
to whatever port you want. After it, when new instance of adb server is started, it is bound to that specified server port or to 5037 by default when not specified differently.
When you want to start adb server manually on the command line with non-default port, you have to do it like this
{code}
adb -P 10000 fork-server server
{code}
so by specifying different port every time, you have multiple instances of adb bridge which in turn means that when you are about to start an emulator, ddmlib tries to connect its client to ANDROID_ADB_SERVER_PORT or by default to 5037.
You can set adbPort configuration property right now in arquillian.xml but it serves as "odd-numbered" port mentioned above where emulator instance is bound so that started server daemon on arbitrary port (by env port set) connects afterwards.
It seems that when ANDROID_ADB_SERVER_PORT is set and tests are executed, emulator adb client starts to communicate with server instance bound to that port so it seems that it does not collide with Eclipse.
Moreover, I noticed that error messages are written out to Eclipse console output only when Android emulator is started and I kill the only running instance of Android debug bridge (so no adb server is running) so Eclipse's adb client listens to void which is the cause of that error output.
> There is no way how to set server port of Android Debug Bridge
> --------------------------------------------------------------
>
> Key: ARQ-1534
> URL: https://issues.jboss.org/browse/ARQ-1534
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha2
> Reporter: Karel Piwko
> Assignee: Stefan Miklosovic
>
> *Given*:
> I have Android tooling installed in Eclipse/JBDS.
> *When:*
> I use Droidium in tests fro IDE.
> *Expect*:
> No having any errors in DDMS output in IDE.
> *Additional information*:
> It looks like that the problem is that Droidium does not allow to set android bridge server port and hence DDMS is already connected to given port. This leads to various errors logged, as DDMS is not prepared to handle external process changing it's environment on the fly.
> See AndroidDebugBridge.determineAndValidateAdbPort() method for more details. While Drodium allows you to change adbPort for running emulator, it always runs the bridge on default port 5037.
> We need a way how to change this server port in Droidium configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (ARQ-1534) There is no way how to set server port of Android Debug Bridge
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1534?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic edited comment on ARQ-1534 at 10/26/13 7:05 PM:
------------------------------------------------------------------
[~kpiwko]
In connection to this problem, it is good idea to clarify whole adb connections related process. From https://developer.android.com/tools/help/adb.html :
{quote}
Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device. It is a client-server program that includes three components:
*A client*, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
*A server*, which runs as a background process on your development machine. *The server manages communication between the client and the adb daemon running on an emulator or device*.
*A daemon*, which runs as a background process on each emulator or device instance.
When you start an adb client, the client first checks whether there is an adb server process already running. If there isn't, it starts the server process. *When the server starts, it binds to local TCP port 5037* and listens for commands sent from adb clients—*all adb clients use port 5037 to communicate with the adb server*.
The server then sets up connections to all running emulator/device instances. *It locates emulator/device instances by scanning odd-numbered ports in the range 5555 to 5585, the range used by emulators/devices. When the server finds an adb daemon, it sets up a connection to that port.* Note that each emulator/device instance acquires a pair of sequential ports — an even-numbered port for console connections and an odd-numbered port for adb connections.
{quote}
In order to specify adb server port where Android debug bridge should be bound to, you have to set environment variable
{code}
ANDROID_ADB_SERVER_PORT
{code}
to whatever port you want. After it, when new instance of adb server is started, it is bound to that specified server port or to 5037 by default when not specified differently.
When you want to start adb server manually on the command line with non-default port, you have to do it like this
{code}
adb -P 10000 fork-server server
{code}
so by specifying different port every time, you have multiple instances of adb bridge which in turn means that when you are about to start an emulator, ddmlib tries to connect its client to ANDROID_ADB_SERVER_PORT or by default to 5037.
You can set adbPort configuration property right now in arquillian.xml but it serves as "odd-numbered" port mentioned above where emulator instance is bound so that started server daemon on arbitrary port (by env port set) connects afterwards.
It seems that when ANDROID_ADB_SERVER_PORT is set and tests are executed, emulator adb client starts to communicate with server instance bound to that port so it seems that it does not collide with Eclipse.
Moreover, I noticed that error messages are written out to Eclipse console output only when Android emulator is started and I kill the only running instance of Android debug bridge (so no adb server is running) so Eclipse's adb client listens to void which is the cause of that error output.
was (Author: smikloso):
In connection to this problem, it is good idea to clarify whole adb connections related process. From https://developer.android.com/tools/help/adb.html :
{quote}
Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device. It is a client-server program that includes three components:
*A client*, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
*A server*, which runs as a background process on your development machine. *The server manages communication between the client and the adb daemon running on an emulator or device*.
*A daemon*, which runs as a background process on each emulator or device instance.
When you start an adb client, the client first checks whether there is an adb server process already running. If there isn't, it starts the server process. *When the server starts, it binds to local TCP port 5037* and listens for commands sent from adb clients—*all adb clients use port 5037 to communicate with the adb server*.
The server then sets up connections to all running emulator/device instances. *It locates emulator/device instances by scanning odd-numbered ports in the range 5555 to 5585, the range used by emulators/devices. When the server finds an adb daemon, it sets up a connection to that port.* Note that each emulator/device instance acquires a pair of sequential ports — an even-numbered port for console connections and an odd-numbered port for adb connections.
{quote}
In order to specify adb server port where Android debug bridge should be bound to, you have to set environment variable
{code}
ANDROID_ADB_SERVER_PORT
{code}
to whatever port you want. After it, when new instance of adb server is started, it is bound to that specified server port or to 5037 by default when not specified differently.
When you want to start adb server manually on the command line with non-default port, you have to do it like this
{code}
adb -P 10000 fork-server server
{code}
so by specifying different port every time, you have multiple instances of adb bridge which in turn means that when you are about to start an emulator, ddmlib tries to connect its client to ANDROID_ADB_SERVER_PORT or by default to 5037.
You can set adbPort configuration property right now in arquillian.xml but it serves as "odd-numbered" port mentioned above where emulator instance is bound so that started server daemon on arbitrary port (by env port set) connects afterwards.
It seems that when ANDROID_ADB_SERVER_PORT is set and tests are executed, emulator adb client starts to communicate with server instance bound to that port so it seems that it does not collide with Eclipse.
Moreover, I noticed that error messages are written out to Eclipse console output only when Android emulator is started and I kill the only running instance of Android debug bridge (so no adb server is running) so Eclipse's adb client listens to void which is the cause of that error output.
> There is no way how to set server port of Android Debug Bridge
> --------------------------------------------------------------
>
> Key: ARQ-1534
> URL: https://issues.jboss.org/browse/ARQ-1534
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha2
> Reporter: Karel Piwko
> Assignee: Stefan Miklosovic
>
> *Given*:
> I have Android tooling installed in Eclipse/JBDS.
> *When:*
> I use Droidium in tests fro IDE.
> *Expect*:
> No having any errors in DDMS output in IDE.
> *Additional information*:
> It looks like that the problem is that Droidium does not allow to set android bridge server port and hence DDMS is already connected to given port. This leads to various errors logged, as DDMS is not prepared to handle external process changing it's environment on the fly.
> See AndroidDebugBridge.determineAndValidateAdbPort() method for more details. While Drodium allows you to change adbPort for running emulator, it always runs the bridge on default port 5037.
> We need a way how to change this server port in Droidium configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (ARQ-1534) There is no way how to set server port of Android Debug Bridge
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1534?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic commented on ARQ-1534:
----------------------------------------
In connection to this problem, it is good idea to clarify whole adb connections related process. From https://developer.android.com/tools/help/adb.html :
{quote}
Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device. It is a client-server program that includes three components:
*A client*, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
*A server*, which runs as a background process on your development machine. *The server manages communication between the client and the adb daemon running on an emulator or device*.
*A daemon*, which runs as a background process on each emulator or device instance.
When you start an adb client, the client first checks whether there is an adb server process already running. If there isn't, it starts the server process. *When the server starts, it binds to local TCP port 5037* and listens for commands sent from adb clients—*all adb clients use port 5037 to communicate with the adb server*.
The server then sets up connections to all running emulator/device instances. *It locates emulator/device instances by scanning odd-numbered ports in the range 5555 to 5585, the range used by emulators/devices. When the server finds an adb daemon, it sets up a connection to that port.* Note that each emulator/device instance acquires a pair of sequential ports — an even-numbered port for console connections and an odd-numbered port for adb connections.
{quote}
In order to specify adb server port where Android debug bridge should be bound to, you have to set environment variable
{code}
ANDROID_ADB_SERVER_PORT
{code}
to whatever port you want. After it, when new instance of adb server is started, it is bound to that specified server port or to 5037 by default when not specified differently.
When you want to start adb server manually on the command line with non-default port, you have to do it like this
{code}
adb -P 10000 fork-server server
{code}
so by specifying different port every time, you have multiple instances of adb bridge which in turn means that when you are about to start an emulator, ddmlib tries to connect its client to ANDROID_ADB_SERVER_PORT or by default to 5037.
You can set adbPort configuration property right now in arquillian.xml but it serves as "odd-numbered" port mentioned above where emulator instance is bound so that started server daemon on arbitrary port (by env port set) connects afterwards.
It seems that when ANDROID_ADB_SERVER_PORT is set and tests are executed, emulator adb client starts to communicate with server instance bound to that port so it seems that it does not collide with Eclipse.
Moreover, I noticed that error messages are written out to Eclipse console output only when Android emulator is started and I kill the only running instance of Android debug bridge (so no adb server is running) so Eclipse's adb client listens to void which is the cause of that error output.
> There is no way how to set server port of Android Debug Bridge
> --------------------------------------------------------------
>
> Key: ARQ-1534
> URL: https://issues.jboss.org/browse/ARQ-1534
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha2
> Reporter: Karel Piwko
> Assignee: Stefan Miklosovic
>
> *Given*:
> I have Android tooling installed in Eclipse/JBDS.
> *When:*
> I use Droidium in tests fro IDE.
> *Expect*:
> No having any errors in DDMS output in IDE.
> *Additional information*:
> It looks like that the problem is that Droidium does not allow to set android bridge server port and hence DDMS is already connected to given port. This leads to various errors logged, as DDMS is not prepared to handle external process changing it's environment on the fly.
> See AndroidDebugBridge.determineAndValidateAdbPort() method for more details. While Drodium allows you to change adbPort for running emulator, it always runs the bridge on default port 5037.
> We need a way how to change this server port in Droidium configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (ARQ-1551) GlassFishContainer NullPointerException when reading network listeners
by Xavi Arias (JIRA)
Xavi Arias created ARQ-1551:
-------------------------------
Summary: GlassFishContainer NullPointerException when reading network listeners
Key: ARQ-1551
URL: https://issues.jboss.org/browse/ARQ-1551
Project: Arquillian
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: GlassFish Containers
Affects Versions: 1.0.0.CR4
Environment: IntelliJ 12, Windows XP SP3
Reporter: Xavi Arias
GlassFishContainer class fetches CommandRunner results in the form of comma separated elements.
There is a bug when reading network-listeners, the list is splitted but not trimmed what generates a NulPointerException when fetching the string:
"configs.config.server-config.network-config.network-listeners.network-listener. https-listener.enabled"
Notice the space in the dotted path "network-listener. https-listener".
The patch could just trim the string:
429: Integer listenPort = readNetworkListenerPort(config, networkListener.trim());
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months