AnsweredAssumed Answered

unable to open VSM after Workstation hang

Question asked by sdetweil2 on Jul 1, 2015
Latest reply on Jul 14, 2015 by sdetweil2

I've spent all day integrating my groovy classes into the vsm process flow.


edit, fix, run itr,

reset itr, rerun

edit fix,




suddenly request the ITR panel and noting. Workstation won't paint main page.


30 minutes gone by,  press close


workstation ends




attempt to reopen VSM.. get stacktrace, failure



com.thoughtworks.xstream.converters.ConversionException: Could not call : null

---- Debugging information ----

message             : Could not call

cause-exception     : java.lang.RuntimeException

cause-message       : null

class               :

required-type       :

converter-type      : com.thoughtworks.xstream.converters.reflection.SerializableConverter

path                : /com.itko.lisa.dynexec.InvocationEx/caught/cause/collector/errors/org.codehaus.groovy.control.messages.SyntaxErrorMessage/source/classLoader/parent/parent/parent/defaultDomain/codesource/

line number         : 32130

class[1]            :

converter-type[1]   : com.thoughtworks.xstream.converters.reflection.ReflectionConverter

class[2]            : sun.misc.Launcher$ExtClassLoader

class[3]            : sun.misc.Launcher$AppClassLoader

class[4]            : com.itko.lisa.test.TestExecClassLoader

class[5]            : groovy.lang.GroovyClassLoader

class[6]            : org.codehaus.groovy.control.SourceUnit

class[7]            : org.codehaus.groovy.control.messages.SyntaxErrorMessage

class[8]            : java.util.LinkedList



both documents (vsm & rsp)look like they were closed ok


short of calling support,  anyone have a magic bullet to recover from this?


I can at least recover the code from the rsp..  but all the logic setup in the VSM will be more troublesome