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

Deadlock when uploading XAR file into package manager #1184

Open
dizzzz opened this issue Nov 21, 2016 · 1 comment
Open

Deadlock when uploading XAR file into package manager #1184

dizzzz opened this issue Nov 21, 2016 · 1 comment
Labels
investigate issues being looked at

Comments

@dizzzz
Copy link
Member

dizzzz commented Nov 21, 2016

I tried to upload a newer version of a XAR file into the dashboard/package manager. The XAR contains native Java code. The 'old' XAR has been used, so the classes have been loaded. Upon upload of the new XAR I fetched two stack traces:

  • one with the YourKit profiler
  • on on stdout

deadlock_yourkit.txt
deadlock_stdout.txt

  • eXist-db / develop
  • macOS / Java8u111
  • messaging/replication extension

Upon stop:

21 Nov 2016 19:50:29,851 [Thread-3] INFO  (JettyStart.java [lifeCycleStopping]:615) - Jetty server stopping... 
SYSTEM INFO
Database instance: exist
-------------------------------------------------------------------
Threads currently waiting for a lock:
=====================================
Thread: qtp138536309-40
           Lock type: COLLECTION
           Lock mode: READ
             Lock id: /db/apps
             Held by: [qtp138536309-27]
             Held by: [qtp138536309-27]
             Held by: [qtp138536309-27]
    Waiting for read: []
   Waiting for write: []
@dizzzz dizzzz added the investigate issues being looked at label Nov 21, 2016
@adamretter
Copy link
Contributor

Your stdout seems to indicate that you have quite a few errors when doing something with the XAR, did you get to the bottom of those first?

Otherwise, we need the jstack output...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
investigate issues being looked at
Projects
None yet
Development

No branches or pull requests

2 participants