Skip to content
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

Issues uploading a BOM #4390

Open
2 tasks done
khaledgithubwl opened this issue Nov 18, 2024 · 1 comment
Open
2 tasks done

Issues uploading a BOM #4390

khaledgithubwl opened this issue Nov 18, 2024 · 1 comment
Labels
defect Something isn't working pending more information

Comments

@khaledgithubwl
Copy link

Current Behavior

Hello,

We encountered an issue while attempting to upload a BOM into Dependency Track. Although our request returned a 200 status, we noticed that nothing was actually uploaded. Upon reviewing the logs, we found the following error:

ERROR [alpine.event.framework.LoggableUncaughtExceptionHandler] An unknown error occurred in an asynchronous event or notification thread
java.lang.NoClassDefFoundError: org/dependencytrack/model/ComponentProperty$Identity
at org.dependencytrack.parser.cyclonedx.util.ModelConverter.lambdasconvertToComponentProperties$2(ModelConverter.java:274)

The problem was resolved after restarting Dependency Track. Could anyone provide insight into why this error occurred?

Best regards,

Steps to Reproduce

I don't know

Expected Behavior

The BOM will either be uploaded successfully, or an error status code (not 200) will be displayed.

Dependency-Track Version

4.11.x

Dependency-Track Distribution

Executable WAR

Database Server

PostgreSQL

Database Server Version

No response

Browser

Google Chrome

Checklist

@khaledgithubwl khaledgithubwl added defect Something isn't working in triage labels Nov 18, 2024
@nscuro
Copy link
Member

nscuro commented Nov 19, 2024

This happens because the embedded Jetty extracts the WAR's contents to /tmp, and some OS automatically wipe the /tmp directory. This is not an issue for containerized deployments, but since you're deploying on bare metal, it is in your case.

See also the FAQ:

Dependency Track stops working after 1-2 weeks

This might happen if your OS cleans-up temp storage without checking for open files. This has been observed with Windows and CentOS. Deleting temporary files is a problem for the embedded Jetty server used by Dependency Track. When launching Dependency Track, try adding -Djava.io.tmpdir=/path/to/tmpdir to the command and specify an alternative path to where you want DT temp files to reside.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
defect Something isn't working pending more information
Projects
None yet
Development

No branches or pull requests

2 participants