Run PlantUML on your own tomcat server issue !!

[sujanrajs]

• I want to run it to my own server

• I have downloaded plantuml.war file

• Run it in my tomcat 10 server

• The server made the folder this way: apache-tomcat-10\webapps\plantuml

• I have tried using sample.war file

• The server made the folder his way apache-tomcat-10\webapps\sample

• This file uses hello.jsp file and it works fine but not plantUML !

I have received the following issue as shown below:

http://localhost:8080/plantuml/uml/SyfFKj2rKt3CoKnELR1Io4ZDoSa70000

HTTP Status 503 – Service Unavailable
Type Status Report
Message Servlet [jsp] is currently unavailable
Description The server is currently unable to handle the request due to a temporary overload or scheduled maintenance, which will likely be alleviated after some delay.

Apache Tomcat/10.1.7

[Shamino0]

I just saw this today and figured out a solution. At least for my installation.

First off, ignore the link from the main PlantUML to the SourceForge download page. Instead download the latest release from this GitHub site: https://github.com/plantuml/plantuml-server/releases

Within each release, you will find four WAR files. Two for JRE8 and two that don't specify a JRE version (I assume for JRE11, which I'm using). Within each pair, there is a "JSP" version and a non-JSP version.

You want to copy one of the JSP files to your webapps directory. This is the version that has the editor that I assume you're looking for. Maybe rename it to "plantuml.war" when you do, so the access-URL will be easy to type

The non-JSP version doesn't have the editor system. It can render PlantUML sources (via the encoded URL) into images (e.g. http://localhost:8080/plantuml/png/SyfFKj2rKt3CoKnELR1Io4ZDoSa70000 or http://localhost:8080/plantuml/svg/SyfFKj2rKt3CoKnELR1Io4ZDoSa70000 ) but it display the servelet unavailable error if you try to pull up the editor (e.g. http://localhost:8080/plantuml/uml/SyfFKj2rKt3CoKnELR1Io4ZDoSa70000 )

It's a bug that the default URL ends up doing this instead of telling you what URLs it supports, but I did find that using the JSP version of the WAR file works as expected.