TXT version results in Java traceback

[Mark Lawrence]

Trying to look at the TXT version of the Timing diagram example:

@startuml
robust “Web Browser” as WB
concise “Web User” as WU

@0
WU is Idle
WB is Idle

@100
WU -> WB : URL
WU is Waiting
WB is Processing

@200
WB is Waiting

@300
WB is Waiting

@enduml

`
java.lang.UnsupportedOperationException: UTXT
at net.sourceforge.plantuml.ugraphic.ImageBuilder.createUGraphic(ImageBuilder.java:386)
at net.sourceforge.plantuml.ugraphic.ImageBuilder.writeImageInternal(ImageBuilder.java:232)
at net.sourceforge.plantuml.ugraphic.ImageBuilder.writeImageTOBEMOVED(ImageBuilder.java:173)
at net.sourceforge.plantuml.timingdiagram.TimingDiagram.exportDiagramInternal(TimingDiagram.java:105)
at net.sourceforge.plantuml.UmlDiagram.exportDiagramNow(UmlDiagram.java:228)
at net.sourceforge.plantuml.AbstractPSystem.exportDiagram(AbstractPSystem.java:135)
at net.sourceforge.plantuml.servlet.DiagramResponse.sendDiagramInternal(DiagramResponse.java:183)
at net.sourceforge.plantuml.servlet.DiagramResponse.sendDiagram(DiagramResponse.java:140)
at net.sourceforge.plantuml.servlet.UmlDiagramService.doGet(UmlDiagramService.java:79)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:717)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1644)
at org.eclipse.jetty.websocket.server.WebSocketUpgradeFilter.doFilter(WebSocketUpgradeFilter.java:164)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1615)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:550)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:568)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:221)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1110)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:479)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:183)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1044)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:199)
at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:109)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
at org.eclipse.jetty.server.Server.handle(Server.java:459)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:281)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:232)
at org.eclipse.jetty.io.AbstractConnection$1.run(AbstractConnection.java:505)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:607)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:536)
at java.lang.Thread.run(Thread.java:724)

An error has occured : java.lang.UnsupportedOperationException: UTXT
We’re not gonna sit in silence, we’re not gonna live with fear

Diagram size: 19 lines / 207 characters.

PlantUML (1.2018.01) cannot parse result from dot/GraphViz.

Please go to http://plantuml.com/graphviz-dot to check your GraphViz version.

Java Runtime: Java(TM) SE Runtime Environment
JVM: Java HotSpot(TM) 64-Bit Server VM
Java Version: 1.7.0_25-b15
Operating System: Linux
Default Encoding: UTF-8
Language: en
Country: US
PLANTUML_LIMIT_SIZE: 2000
Processors: 1
Max Memory: 194,641,920
Total Memory: 134,410,240
Free Memory: 41,327,600
Used Memory: 93,082,640
Thread Active Count: 16

This may be caused by :
– a bug in PlantUML
– a problem in GraphViz

You should send this diagram and this image to plantuml@gmail.com or
post to http://plantuml.com/qa to solve this issue.
You can try to turn arround this issue by simplifing your diagram.
`

[Arwen Vaughan]

Yeah, the txt option does not always work. I notice hat all the time. This is not a planttext issue though. Planttext just sends the plantuml to the plantuml server. If it errors out with this stuff then it had some issue with the plantuml text or converting it to dito. Sorry, but planttext is just a GUI to plantuml. I do not have anything to do with the plantuml software that generates the images…or in this case errors in java. 🙁

[Ariel]

Same here

[Author]

Posts