Upgrade DependencyTrack apiserver fails without exception on computing severity where value is NULL about dependency-track HOT 3 CLOSED

Are you running on an orchestrator such as Kubernetes, that could be killing the pod if it doesn't become healthy in a certain amount of time?

Thanks, that is exactly what happened.

I am indeed using docker compose to start the container in an Azure App Service. According to Azure App Service on Linux FAQ there is a default timeout of 230s for the container to start up.

After increasing the timeout, I could see that Computing severities for vulnerabilities where severity is currently NULL took ~12 minutes and the upgrade ran through successful.

from dependency-track.

When the upgrade fails, it will log a stack trace, and it will not automatically shut down.

Are you running on an orchestrator such as Kubernetes, that could be killing the pod if it doesn't become healthy in a certain amount of time?

How much time passes between Computing severities for vulnerabilities where severity is currently NULL being logged and the container being shut down?

from dependency-track.

Hmmm, 12min is a lot for this operation. It already utilizes SQL statement batching so it doesn't perform a lot of requests to the database.

Do you have high latency between API server and database?

from dependency-track.