It's all about the answers!

Ask a question

Have the issues with Honza's RTC WF Visualizer on Scrum templates ever been resolved ?

long TRUONG (3654118146) | asked Jun 24 '14, 6:35 p.m.
 Honza's RTC Workflow Visualizer has been a god-sent for me, I used it everywhere and greatly appreciate it. But I am getting into issues on some Scrum templates similar to those of the one post on the original Honza's perspective, just wonder if someone has resolved them or seen their resolution. The Visualizer did work with the OOTB Scrum template on 4.0.3.

My error messages:
C:\Users\gr4truo\Documents\junk\workflows\PASwf\20140623>java -jar ..\..\2createDiagrams\visualiser.jar -d "C:\Program Files (x86)
\Graphviz2.32\bin\dot.exe" PAStemplate.txt Invalid byte 1 of 1-byte UTF-8 sequence.
        at Source)
        at Source)
        at Source)
        at Source)
        at Source)
        at Source)
        at Source)
        at$ Source)
        at Source)
        at Source)
        at Source)
        at Source)
        at Source)
        at Source)
        at Source)
        at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
        at com.stastnarodina.workflowVisualiser.Parser.parse(
        at com.stastnarodina.workflowVisualiser.Main.main(

Original post of this issue:
  1. Jirong Hu says:


    I am able to generate the pdf files for Simple and Traditional process template, but failed in Scrum one (process.xml is from the sample JUnit project). Here is the error:

    C:\build>java -jar „C:\build\visu­aliser.jar“ -o„V:\HOST_C\Ji­rong\Youth2011\RTC\W­ork Item\Workflow\S
    rum“ -d „C:\Program Files\Graphviz 2.28\bin\dot.exe“ Srum_process.xml­­ternal.impl.i­o.MalformedBy­teSequenceExcep­tion: Invalid byte 1 of 1-byte
    UTF-8 sequence.
    at­­ternal.impl.i­­validByte(Unknown Source)
    at­­ternal.impl.i­­ad(Unknown Source)
    at­­ternal.impl.XMLEn­tityScanner.lo­ad(Unknown Source)
    at­­ternal.impl.XMLEn­­ekChar(Unknown Source)
    at­­ternal.impl.XMLDo­cumentFragmen­tScannerImpl$Frag­mentContentDri Source)
    at­­ternal.impl.XMLDo­cumentScannerIm­ Source)
    wn Source)
    at­­ternal.parser­s.XML11Configu­ration.parse(Un­known Source)
    at­­ternal.parser­s.XML11Configu­ration.parse(Un­known Source)
    at­­ternal.parser­s.XMLParser.par­se(Unknown Source)
    at­­ternal.parser­s.DOMParser.par­se(Unknown Source)
    at­­ternal.jaxp.Do­cumentBuilderIm­pl.parse(Unknown Source)
    at javax.xml.par­sers.DocumentBu­ilder.parse(Un­known Source)
    at com.stastnaro­dina.workflow­Visualiser.Par­ser.parse(Par­
    at com.stastnaro­dina.workflow­Visualiser.Ma­in.main(Main.ja­va:46)

  1. honza says:

    Hi Jirong,
    thanks for the comment. It seems that the XML parser does not like some character in you process template XML file. Could you, please, send me the xml file to, as the XML got corrupted in your post.

One answer

permanent link
long TRUONG (3654118146) | answered Jun 26 '14, 6:41 p.m.
edited Jun 26 '14, 6:42 p.m.
 Found the issue and got the fix from in-house scripting guru:

The issue was the presence of non-UTF-8 encoding: And the fix is to either manually or with a script, remove any non-UTF-8 encoding off the xml, and voila you get your WFs. We replaced any non-UTF-8 char with 00.

Note that embedded tabs, CRs, LFs (may have been introduced by cutting and pasting to get the XML) would not crash the visualizer.

Now the question is why there are any non-UTF-8 encoding in the process xml, is it a bug ? This seem to be in existence only in Scrum templstes, though we did not have any issue with the OOTB Scrum Template.

This can't be marked as the right answer, but it is.

Your answer

Register or to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.