Launching and stopping appium server programmtically

this issue is fixed by setting up the ANDROID_HOME path globally.

You successfully managed to start the Appium server programmatically as I can see (because the node.exe process exists in the Task Manager).

The problem seems to be with Appium server configurations or capabilities. Please provide both of them.

@Hassan_Radi: Thanks for response. In another way , manually started Appium server , executed script from setting server capabilities without any issues.

The issue is appearing only when Appium server and same Appium capabilities are running through code. However please see below code (values are driven from spreadsheet part of framework.

String strJ4uBuildFilePath = ReadGlobalConfiguration.globalConfigprop.getProperty("J4uApp_BuildFilePath");
String strJ4uBuildFile = ReadGlobalConfiguration.globalConfigprop.getProperty("J4uApp_Android_BuildFileName");
FwConstants.fwSetDesiredCapability();

     File appDir = new File(strJ4uBuildFilePath);
	 File app = new File(appDir,strJ4uBuildFile);

	 FwConstants.Appiumcapabiliy.setCapability("automationName", FwConstants.strArg_AutomationName_Val);
	 FwConstants.Appiumcapabiliy.setCapability("platformName",FwConstants.strArg_PlatformName_Val);
	 FwConstants.Appiumcapabiliy.setCapability("platformVersion",FwConstants.strArg_Arg_PlatformVersion_Val);
	 FwConstants.Appiumcapabiliy.setCapability("deviceName",FwConstants.strArg_DeviceName_Val);
	 FwConstants.Appiumcapabiliy.setCapability("app-package",FwConstants.strArg_Package_Val);
	 FwConstants.Appiumcapabiliy.setCapability("app-activity",FwConstants.strArg_Activity_Val);

	 FwConstants.Appiumcapabiliy.setCapability("app", app.getAbsolutePath());
	 fwSetDriverToAppiumServer();

below code is part of above method fwSetDriverToAppiumServer();

FwConstants.fwSetDesiredCapability();

	 try {
		 FwConstants.AndDriver = new AndroidDriver (new URL(FwConstants.strArg_URL),FwConstants.Appiumcapabiliy);
		} catch (MalformedURLException e) {
			// TODO Auto-generated catch block
			e.printStackTrace();
		}

	 FwConstants.AndDriver.manage().timeouts().implicitlyWait(60, TimeUnit.SECONDS);

Please let me know if you need further information.

Regards,
Kiran

@Hassan_Radi: Thanks for requesting log.
After your hint i did check the log , found "deviceName" is missing listed in the log. Due to code error , appiumcapability object is setting hence it is not finding "deviceName" , I have fixed framework code and working fine (starting and stopping server through code). This is happening only when I execute the script in "Debug" mode. When I initiated the script as "Run" mode , it is not starting the server. I have checked the task manager , I didn't see "node.exe" process.
Please see below log details and I request guidance in this.

[TestNG] Running:
C:\Users\kedupuganti\AppData\Local\Temp\testng-eclipse--511367850\testng-customsuite.xml

FAILED CONFIGURATION: @BeforeMethod testscriptInitialization
org.openqa.selenium.remote.UnreachableBrowserException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
Build info: version: '2.44.0', revision: '76d78cf', time: '2014-10-23 20:03:00'
System info: host: 'CSCINDAE751814', ip: '10.31.24.67', os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version: '1.7.0_71'
Driver info: driver.version: AndroidDriver
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:593)
at io.appium.java_client.AppiumDriver.execute(AppiumDriver.java:180)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:240)
at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:126)
at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:153)
at io.appium.java_client.AppiumDriver.(AppiumDriver.java:109)
at io.appium.java_client.android.AndroidDriver.(AndroidDriver.java:39)
at app.Framework.CommonLibs.AppiumServerLib.fwSetDriverToAppiumServer(AppiumServerLib.java:156)
at app.Framework.CommonLibs.AppiumServerLib.fwGetAppInstallAndInitialize(AppiumServerLib.java:120)
at app.TestSuite.POCTestScripts.Mob_SignIn_ValidateForValidCustomer.testscriptInitialization(Mob_SignIn_ValidateForValidCustomer.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:653)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
at org.testng.TestRunner.privateRun(TestRunner.java:767)
at org.testng.TestRunner.run(TestRunner.java:617)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1149)
at org.testng.TestNG.run(TestNG.java:1057)
at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:111)
at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:204)
at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:175)
Caused by: org.apache.http.conn.HttpHostConnectException: Connect to 127.0.0.1:4789 [/127.0.0.1] failed: Connection refused: connect
at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:140)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:318)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
at org.openqa.selenium.remote.HttpCommandExecutor.fallBackExecute(HttpCommandExecutor.java:215)
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:184)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:572)
... 35 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:72)
at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:123)
... 47 more

SKIPPED CONFIGURATION: @AfterMethod endTestScriptExecution
SKIPPED: Mob_SignIn_ValidateForValidCustomer_TestScript

===============================================
Default test
Tests run: 1, Failures: 0, Skips: 1
Configuration Failures: 1, Skips: 1
===============================================

===============================================
Default suite
Total tests run: 1, Failures: 0, Skips: 1
Configuration Failures: 1, Skips: 1
===============================================

Windows:
http://megettingerror.blogspot.in/2015/02/java-code-to-launch-appium-on-windows.html143

Mac:
http://megettingerror.blogspot.in/2015/01/java-code-to-start-appium-server-on-mac.html189

@Hassan_Radi: line 156 set capabilities to driver

FwConstants.AndDriver = new AndroidDriver (new URL(FwConstants.strArg_URL),FwConstants.Appiumcapabiliy);

url is coming from excel spreadsheet , accessed using Apache POI.

****@Kamal_Girdher:**** Thanks for response and provided links , i built the framework which will access the values dynamically from the spreadsheet during execution. Firstly I am executing on Windows , same code I was referring into dynamic code. It is perfectly running in debug mode (node.exe invoke , setting capabilities and running above mentioned driver code). But during run mode , giving above mentioned error for which Hasan is requesting information. Thanks for your help.

The fact that it fails when starting the Appium session is because starting the server was somehow skipped and it is now trying to reach a server that was not started.

The server starting logic might have failed and was not started successfully without you noticing (It would throw an error message in the command prompt log) because the server might have been already running and trying to start it again with the same IP address and port number will give an error message saying that "The port number is already used by another application"

I recommend checking if the server is already running before you attempt to start it. If it was actually running, then you should stop it and then move to the start logic again. Also when working with the command prompt and executing actions in this manner, you should always print the output of the command execution in your log to be able to refer to that later and know what went wrong.

Hope I helped....

P.S. The IP address you are using "10.31.24.67" doesn't look like a local address on your machine, unless you are doing some loopback tunneling, so please check the IP address and make sure it is not the issue.

@Hassan_Radi:

Thanks for your time and comments.

I am examining and working on your comments.

I have two queries here:
a) How to know whether Appium server is running or not , do you have any reference code or link?
b) Regarding output of the command execution log record , do you have any link or reference code?, so that I will implement and see

The IP address shown in the log file is , Host IP Address. But in the actual code for server start on IP Address is 127.0.0.1 , port 4789

Does this impact when we trying to initiate Appium server through code?

Regards,
Kiran

You will find a node.exe process in your task manager when the server is running.

You can use this function74. The whole class is supposed to start and stop Appium server. Give it a try and let me know how it works.

Hi @Hassan_Radi can you help me in this thread please

How can i start the server and stop it from ruby programmatically?

hey hi,
I am new to the appium i want to launch appium in ubuntu, want to know how to write test scripts..
any help would be very helpful.
thanks in advance.

There is no Appium Gui and Inspector for Ubuntu???