Exception org.openqa.selenium.json.JsonException: Unable to determine type from: E. Last 1 characters read: error only in Jenkins runs

0

We get the following error when doing large runs in Jenkins lately. It started only happening once in a while, but several tests fail regularly with every run now. The test XML runs fine locally. Has anyone come across this issue before and what was your fix? Thanks in advance.

Error:

Completed executing following method : TestSetup.beforeMetod
Exception org.openqa.selenium.json.JsonException
Message: Unable to determine type from: E. Last 1 characters read: E Build info: version: '3.141.0', revision: '2ecb7d9a', time: '2018-10-31T20:09:30' System info: host: 'OKC4AUTOQA-1', ip: '10.60.10.217', os.name: 'Windows Server 2012 R2', os.arch: 'amd64', os.version: '6.3', java.version: '11.0.2' Driver info: driver.version: RemoteWebDriverStacktrace:


at org.openqa.selenium.json.JsonInput.peek(JsonInput.java:122)
at org.openqa.selenium.json.JsonTypeCoercer.lambda$null$6(JsonTypeCoercer.java:140)
at org.openqa.selenium.json.JsonTypeCoercer.coerce(JsonTypeCoercer.java:126)
at org.openqa.selenium.json.Json.toType(Json.java:69)
at org.openqa.selenium.json.Json.toType(Json.java:55)
at org.openqa.selenium.json.Json.toType(Json.java:50)
at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:87)
at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:158)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:552)
at org.openqa.selenium.remote.RemoteWebDriver$RemoteWebDriverOptions$RemoteTimeouts.implicitlyWait(RemoteWebDriver.java:780)
at utils.CustomFunctions.manageDriver(CustomFunctions.java:6633)
at setup.TestSetup.beforeMetod(TestSetup.java:832)
at jdk.internal.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:124)
at org.testng.internal.MethodInvocationHelper.invokeMethodConsideringTimeout(MethodInvocationHelper.java:59)
at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:458)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:222)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:523)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:719)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:989)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)

That looks to be a selenium error not Jenkins. Jenkins isn’t in the stack trace at all

That’s part of what is puzzling us.
The tests run fine when ran locally through selenium.
Thanks for the reply.