search cancel

"Exception Initializing test:AUTO" occurred when running the "Execute External Command step"

book

Article ID: 113059

calendar_today

Updated On:

Products

CA Application Test

Issue/Introduction

After defining the "Execute External Command step" with the Output encoding changes as "Auto-detect" and running test case by using the ITR is not problem.

However, when running the same test case by using the Staging test with Coordinator Server as [email protected], then getting the error dialog below from DevTest Workstation.

User-added image

After that the staging test becomes infinite loop.


By checking the same test case for several test runs in DevTest, the results were below:

  1. ITR ... No Problem
  2. Staging with Coordinator Server as [email protected] ... NG
  3. Staging with Coordinator Server as Blank ... No Problem
  4. Stage a Quick Test with Stage Instance To as [email protected] ... NG
  5. Stage a Quick Test with Stage Instance To as Stage Local ... No Problem
  6. CVS ... Cannot get any errors from DevTest Workstation but same error messages like below were recorded in simulator.log level ... NG

2018-08-31 00:58:39,647Z (09:58) [ServerRequestResponder 1] ERROR com.itko.lisa.net.ServerRequestHandler - Caught throwable sending message for mid <unknown> code: <null> message AUTO : AUTO
---- Debugging information ----
message             : AUTO
cause-exception     : java.nio.charset.UnsupportedCharsetException
cause-message       : AUTO
class               : java.nio.charset.Charset
required-type       : java.nio.charset.Charset
converter-type      : com.thoughtworks.xstream.converters.SingleValueConverterWrapper
wrapped-converter   : com.thoughtworks.xstream.converters.extended.CharsetConverter
path                : /com.itko.lisa.test.TestCase/nodes/com.itko.lisa.utils.CommandLineExecNode/charset
line number         : 1966
class[1]            : com.itko.lisa.utils.CommandLineExecNode
converter-type[1]   : com.thoughtworks.xstream.converters.reflection.ReflectionConverter
class[2]            : java.util.ArrayList
converter-type[2]   : com.thoughtworks.xstream.converters.collections.CollectionConverter
class[3]            : com.itko.lisa.test.TestCase
version             : 1.4.8
-------------------------------
com.thoughtworks.xstream.converters.ConversionException: AUTO : AUTO
---- Debugging information ----
message             : AUTO
cause-exception     : java.nio.charset.UnsupportedCharsetException
cause-message       : AUTO
class               : java.nio.charset.Charset
required-type       : java.nio.charset.Charset
converter-type      : com.thoughtworks.xstream.converters.SingleValueConverterWrapper
wrapped-converter   : com.thoughtworks.xstream.converters.extended.CharsetConverter
path                : /com.itko.lisa.test.TestCase/nodes/com.itko.lisa.utils.CommandLineExecNode/charset
line number         : 1966
class[1]            : com.itko.lisa.utils.CommandLineExecNode
converter-type[1]   : com.thoughtworks.xstream.converters.reflection.ReflectionConverter
class[2]            : java.util.ArrayList
converter-type[2]   : com.thoughtworks.xstream.converters.collections.CollectionConverter
class[3]            : com.itko.lisa.test.TestCase
version             : 1.4.8
-------------------------------
    at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79)

Cause

This is a character set handling problem for xstream.

Environment

Release: All supported DevTest releases

Component: Execute External Command step

Windows Environment.

Resolution

The workaround is to set the suitable character set for encoding to the "Output Encoding:" value  in the "Execute External Command step" .

Attachments