Please help me, i am stuck up last 3 days for this issue, i am new to this. plz plz help me.
FAILED CONFIGURATION: @BeforeTest setUp
org.openqa.selenium.SessionNotCreatedException: A new session could not be created. (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 100.42 seconds
Build info: version: ‘2.53.0’, revision: ‘35ae25b’, time: ‘2016-03-15 16:57:40’
System info: host: ‘JMSNB013’, ip: ‘172.27.139.15’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: ‘1.8.0_101’
Driver info: org.openqa.selenium.remote.RemoteWebDriver
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:206)
at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:158)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:678)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:249)
at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:131)
at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:158)
at androidemulator.jabordLogin.setUp(jabordLogin.java:56)
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:85)
at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:510)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:211)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:138)
at org.testng.TestRunner.beforeRun(TestRunner.java:648)
at org.testng.TestRunner.run(TestRunner.java:616)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:359)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:354)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:312)
at org.testng.SuiteRunner.run(SuiteRunner.java:261)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1215)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1140)
at org.testng.TestNG.run(TestNG.java:1048)
at org.testng.remote.AbstractRemoteTestNG.run(AbstractRemoteTestNG.java:126)
at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:152)
at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:57)
Appium Log:
Launching Appium server with command: C:\Program Files\Appium\node.exe lib\server\main.js --address 127.0.0.1 --port 4723 --device-ready-timeout 15 --platform-name Android --platform-version 21 --automation-name Appium --log-no-color
info: Welcome to Appium v1.4.16 (REV ae6877eff263066b26328d457bd285c0cc62430d)
info: Appium REST http interface listener started on 127.0.0.1:4723
info: [debug] Non-default server args: {“address”:“127.0.0.1”,“logNoColors”:true,“androidDeviceReadyTimeout”:“15”,“platformName”:“Android”,“platformVersion”:“21”,“automationName”:“Appium”}
info: Console LogLevel: debug
info: → POST /wd/hub/session {“desiredCapabilities”:{“appPackage”:“com.jmi.jabord_mobile.android.client”,“appActivity”:“com.jmi.jabord.mobile.client.ui.activity.SplashAct”,“app-wait-package”:“com.jmi.jabord_mobile.android.client”,“app-wait-activity”:“com.jmi.jabord.mobile.client.ui.activity.SplashAct”,“browserName”:“Android”,“platformName”:“Android”,“deviceName”:“Android Emulator”,“version”:“5.0.2”}}
info: Client User-Agent string: Apache-HttpClient/4.5.1 (Java/1.8.0_101)
info: [debug] The following desired capabilities were provided, but not recognized by appium. They will be passed on to any other services running on this server. : app-wait-package, app-wait-activity, version
info: [debug] Didn’t get app but did get Android package, will attempt to launch it on the device
info: [debug] Creating new appium session 9a7c80c0-ffa9-4e91-857e-9d3e7bfc285c
info: Starting android appium
info: [debug] Getting Java version
info: Java version is: 1.8.0_101
info: [debug] Checking whether adb is present
info: [debug] Using adb from D:\MobileTesting\SDK\platform-tools\adb.exe
warn: No app capability, can’t parse package/activity
info: [debug] Using fast reset? true
info: [debug] Preparing device for session
info: [debug] Not checking whether app is present since we are assuming it’s already on the device
info: Retrieving device
info: [debug] Trying to find a connected android device
info: [debug] Getting connected devices…
info: [debug] executing cmd: D:\MobileTesting\SDK\platform-tools\adb.exe devices
info: [debug] 1 device(s) connected
info: Found device emulator-5554
info: [debug] Setting device id to emulator-5554
info: [debug] Waiting for device to be ready and to respond to shell commands (timeout = 15)
info: [debug] executing cmd: D:\MobileTesting\SDK\platform-tools\adb.exe -s emulator-5554 wait-for-device
info: [debug] executing cmd: D:\MobileTesting\SDK\platform-tools\adb.exe -s emulator-5554 shell “echo ‘ready’”
info: [debug] Retrying restartAdb
info: [debug] executing cmd: D:\MobileTesting\SDK\platform-tools\adb.exe -s emulator-5554 kill-server
info: [debug] Getting connected devices…
info: [debug] executing cmd: D:\MobileTesting\SDK\platform-tools\adb.exe -s emulator-5554 devices
info: [debug] 1 device(s) connected
info: [debug] Waiting for device to be ready and to respond to shell commands (timeout = 15)
info: [debug] executing cmd: D:\MobileTesting\SDK\platform-tools\adb.exe -s emulator-5554 wait-for-device
info: [debug] executing cmd: D:\MobileTesting\SDK\platform-tools\adb.exe -s emulator-5554 shell “echo ‘ready’”
info: [debug] Retrying restartAdb
info: [debug] executing cmd: D:\MobileTesting\SDK\platform-tools\adb.exe -s emulator-5554 kill-server
info: [debug] Getting connected devices…
info: [debug] executing cmd: D:\MobileTesting\SDK\platform-tools\adb.exe -s emulator-5554 devices
info: [debug] 1 device(s) connected
info: [debug] Waiting for device to be ready and to respond to shell commands (timeout = 15)
info: [debug] executing cmd: D:\MobileTesting\SDK\platform-tools\adb.exe -s emulator-5554 wait-for-device
info: [debug] executing cmd: D:\MobileTesting\SDK\platform-tools\adb.exe -s emulator-5554 shell “echo ‘ready’”
info: [debug] Retrying restartAdb
info: [debug] executing cmd: D:\MobileTesting\SDK\platform-tools\adb.exe -s emulator-5554 kill-server
info: [debug] Getting connected devices…
info: [debug] executing cmd: D:\MobileTesting\SDK\platform-tools\adb.exe -s emulator-5554 devices
info: [debug] 1 device(s) connected
info: [debug] Waiting for device to be ready and to respond to shell commands (timeout = 15)
info: [debug] executing cmd: D:\MobileTesting\SDK\platform-tools\adb.exe -s emulator-5554 wait-for-device
info: [debug] executing cmd: D:\MobileTesting\SDK\platform-tools\adb.exe -s emulator-5554 shell “echo ‘ready’”
info: [debug] executing cmd: D:\MobileTesting\SDK\platform-tools\adb.exe -s emulator-5554 kill-server
info: [debug] Getting connected devices…
info: [debug] executing cmd: D:\MobileTesting\SDK\platform-tools\adb.exe -s emulator-5554 devices
info: [debug] 1 device(s) connected
info: [debug] Waiting for device to be ready and to respond to shell commands (timeout = 15)
info: [debug] executing cmd: D:\MobileTesting\SDK\platform-tools\adb.exe -s emulator-5554 wait-for-device
info: [debug] executing cmd: D:\MobileTesting\SDK\platform-tools\adb.exe -s emulator-5554 shell “echo ‘ready’”
info: [debug] Sent shutdown command, waiting for UiAutomator to stop…
warn: UiAutomator did not shut down fast enough, calling it gone
info: [debug] Cleaning up android objects
info: [debug] Cleaning up appium session
error: Failed to start an Appium session, err was: Device did not become ready in 15 secs; are you sure it’s powered on?
info: [debug] undefined
info: [debug] Responding to client with error: {“status”:33,“value”:{“message”:“A new session could not be created.”,“origValue”:“Device did not become ready in 15 secs; are you sure it’s powered on?”},“sessionId”:null}
info: ← POST /wd/hub/session 500 100193.357 ms - 172