APOC 5.14.0 Crashes Neo4j On Startup #548
Assignees
Comments
|
Hi @inf3rnus, this sounds concerning. I have not heard this from anyone else and our testing of 5.14 did not indicate any issues. According to the stacktrace this seems to be the main issue:
CurrentFrame and Frame are part of ow2.asm. In our dependencies trees I can see:
I guess there might be some conflict between the different versions here, but it surprises me that others have not seen it. Do you have some other plugin/library apart from APOC installed? |
|
Yeah, definitely is gnarly
Nope, this occurs when instantiating a brand new 5.14 db and then installing the plugin. Checked the plugins folder as well and there's only the jwt plugin and the apoc plugin installed. If it's useful, what I have not done is attempted to download Neo4j Desktop completely fresh. Current version I'm using has been upgraded over a few years gradually. I doubt that is a likely culprit, but I suppose it's possible. If you guys have VM's I'd see if you can replicate it on Ubuntu 18.04 with virtual box or something, if so, that would certainly eliminate something specific with my machine from the mix/make it easier to hunt down the bug. |
|
One other thing, previous versions, e.g. 5.13 work fine with their respective APOC plugin |
|
@inf3rnus Are you using AuraDS or some sort of GDS plugin? Because I can see GDS output in your stacktrace |
|
O you're right, here's the stack trace with it uninstalled |
|
Hi there, OS: ubuntu 20.04 running in a virtualbox virtual machine I used neo4j desktop to create a fresh new neo4j 5.14.0 database. With apoc I get a very familier looking Stacktrace: |
|
Extending upon my previous comment. I found a solution that seems to work for my use case. I managed to get this to work by manually copying the latest core release apoc-5.15.0-core.jar plus apoc-5.14.0-extended.jar into my plugin directory (see screenshot) Links: Maybe that helps locating the problem.
|
|
I am seeing same behavior after upgrading my desktop project from 5.14.0 (which was actually working just fine) to 5.15.0. Uninstalling APOC (version 5.15.0) allows the server to start normally, but reinstalling APOC causes the issue to reappear. |
|
I installed a new 5.14.0 Desktop project, and Desktop automatically installed APOC 5.15.0 (and GDS 2.5.6) along with it. The 5.14.0 server started up with no problems. So, for me, version 5.14.0 of the server can start when using version 5.15.0 of APOC. But version 5.15.0 of the server cannot. |
|
Hello! We have investigated this a little more and are working on a fix, in the meantime, our local testing shows it is related to the naming of the jar that Desktop is giving, so a temporary workaround would be to rename the file: In Neo4j Desktop:
Let me know if this works in the meantime :) Sorry for the inconvenience |
|
This worked for me on 5.15. Thank you |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior (Mandatory)
Inits DB successfully
Actual Behavior (Mandatory)
Does not init DB successfully
How to Reproduce the Problem
Specifications (Mandatory)
Versions
java 21.0.1 2023-10-17 LTS(Also failed foropenjdk 17.0.7 2023-04-18)Some logs for your convenience:
Chat GPT says there's a mismatch between the compiled libraries and the libraries they rely on. .jar's too complex for me to make any progress on myself in a reasonable amount of time, although it is a tempting bug hunt.
I'm probably not the only one experiencing this problem, but it's really frustrating because the thing I need to test is a .dump from Aura and that .dump does not work on lower versions of neo4j.
With that said,
apoc-5.14.0-core.jardoes work with neo4j-enterprise via the .tar.gz based install (neo4j being run directly from the terminal)... And if this is useful info, it was not working earlier this week, and now happens to be working on my machine today... So either the contents of the .jar with the labelapoc-5.14.0-core.jarchanged on your releases page, or something weird is happening with specifically my machine.O yeah, one other thing I tried was taking
apoc-5.14.0-core.jarthat's working on the .tar.gz based install, and I tried adding it as a plugin to the version of neorj 5.14.0 that I'm running in Neo4j Desktop. This produced the same error. Config file says to allow all apoc.* procedures, so hopefully that's also some useful info.Team neo4j to the rescue! Please save me <3
The text was updated successfully, but these errors were encountered: