question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Issue Type:

  • defect report
  • enhancement request

Current Behavior:

The dependency track application crashes fairly frequently. In a matter of hours, is what I am observing.

I have attached log output at the end from when the crashing starts. The exception repeats every second until I kill it.

It is not very clear from the log (to me) what the origin of the problem might be.

Steps to Reproduce (if defect):

Let DT run, pushing data to it from Jenkins.

Expected Behavior:

It should keep running 😃

Environment:

  • Dependency-Track Version: 3.2.1
  • Distribution: Embedded WAR
  • BoM Format & Version:
  • Database Server: H2
  • Browser:

I run it in a Docker container with 4GB RAM using Oracle 8_181.

I use H2 trying to see it working before I set up a proper DB. There does not appear to be problems with memory or CPU load.

It is not clear to me (from the stack trace) that using H2 should be the root of the problem?!

I guess I will try to set up an external DB to see if it changes anything.

Other Details:

2018-10-11 11:24:37,011 [] INFO [org.dependencytrack.tasks.MetricsUpdateTask] Executing metrics update on project: 737124f6-8660-469c-988f-f9dcb6ffe88b
2018-10-11 11:24:37,059 [] INFO [org.dependencytrack.tasks.MetricsUpdateTask] Executing metrics update on project: 7919dc7e-67ac-480e-a647-6aba4700ebb1
2018-10-11 11:49:59,297 [] ERROR [alpine.event.framework.LoggableUncaughtExceptionHandler] An unknown error occurred in an asynchronous event or notification thread
org.apache.lucene.store.AlreadyClosedException: this IndexWriter is closed
        at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:720)
        at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:734)
        at org.apache.lucene.index.IndexWriter.deleteDocuments(IndexWriter.java:1420)
        at org.dependencytrack.search.ComponentIndexer.remove(ComponentIndexer.java:95)
        at org.dependencytrack.search.ComponentIndexer.remove(ComponentIndexer.java:39)
        at org.dependencytrack.tasks.IndexTask.inform(IndexTask.java:50)
        at alpine.event.framework.BaseEventService.lambda$publish$0(BaseEventService.java:90)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
2018-10-11 11:49:59,297 [] ERROR [alpine.event.framework.LoggableUncaughtExceptionHandler] An unknown error occurred in an asynchronous event or notification thread
org.apache.lucene.store.AlreadyClosedException: this IndexWriter is closed
        at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:720)
        at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:734)
        at org.apache.lucene.index.IndexWriter.deleteDocuments(IndexWriter.java:1420)
        at org.dependencytrack.search.ComponentIndexer.remove(ComponentIndexer.java:95)
        at org.dependencytrack.search.ComponentIndexer.remove(ComponentIndexer.java:39)
        at org.dependencytrack.tasks.IndexTask.inform(IndexTask.java:50)
        at alpine.event.framework.BaseEventService.lambda$publish$0(BaseEventService.java:90)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:5 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
jskov-jyskebank-dkcommented, Oct 26, 2018

Yes, sorry about the silence (vacation, and then swamped with other stuff).

My plan is to try again with 3.3 and an external DB. Probably next week.

Cheers.

0reactions
lock[bot]commented, Jan 28, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Why do Computers Crash? Top 5 Reasons Your PC Might ...
If you've run through all of the preceding possibilities and continue experiencing frequent crashes, a hardware issue could be to blame. An easy...
Read more >
Why does My PC Keep Crashing? Here're 10 Fast Fixes!
A computer crash happens when the drivers are outdated, there is a fault in the hardware, or there is not sufficient airflow due...
Read more >
Top 10 Reasons Why Your Computer Keeps Crashing
1. A Device Is Not Correctly Seated · 2. Heat Can Cause Computers to Crash · 3. Your PC Is Crashing Because of...
Read more >
Why Does My Computer Keeps Crashing? Here Are Answers ...
Fixes for PC Keeps Crashing · Fix 1: Detect and Repair Bad Sectors on the Hard Disk · Fix 2: Ensure That Your...
Read more >
Why does my computer keep crashing? - Just Ask Thales EN
Why does my computer keep crashing? · Heat. An overheating computer is the most common cause of random crashes. · Hardware. If you...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found