-
-
Notifications
You must be signed in to change notification settings - Fork 230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NoClassDefFoundError java/awt/image/ComponentColorModel for generating PlantUML diagram #1606
Comments
Currently looking at the same problem in a GitLab Instance that uses kroki for rendering PlantUML diagrams after the update to 0.21.3. As far as i can tell seems to happen only for some definitions from awslib includes though. The basic PlantUML stuff works and also some of the awslib definitions. Can also be reproduced with https://kroki.io/#try This works:
This does not work:
|
Will be fixed in https://github.com/yuzutech/plantuml |
When running the Docker image locally on my M2 MacBook Pro using the following command:
docker run -p8000:8000 -e KROKI_COMMAND_TIMEOUT=1m -d yuzutech/kroki
And using the following payload in the HTTP request:
I receive the following error:
An error has occured: java.lang.NoClassDefFoundError: java/awt/image/ComponentColorModel
Diagram size: 35112 lines / 2106549 characters.
PlantUML (1.2023.7) cannot parse result from dot/GraphViz.
Please go to https://plantuml.com/graphviz-dot to check your GraphViz version.
Java Runtime: null
JVM: Substrate VM
Default Encoding: UTF-8
Language: null
Country: null
PLANTUML_LIMIT_SIZE: 4096
This may be caused by :
You should send this diagram and this image to [email protected] or post to https://plantuml.com/qa to solve this issue.
You can try to turn around this issue by simplifing your diagram.
Considering I do not get this error if I use the jar file locally, I figured there must be something related to the Docker image that is causing this error. I did some experimenting changing Java JDK's building my own Docker image locally, but no success.
The text was updated successfully, but these errors were encountered: