Open sbernard31 opened 6 years ago
Correct me, but this sounds easy to fix and it's not been fixed just to provide backwards compatibility? for over a year?
If so, I will begin using another library.
I still face this issue sporadically... This is pretty annoying :confused:
Any chance to get a fix this ?
@pstanton to you still face this issue ?
This project is mostly unmaintained, as far as I know. I would suggest either forking it or migrating to a new JSON dependency if this is giving you problems.
Don't get me wrong: I also really liked this library, but sometimes OSS just gets abandoned.
Just to let you know we finally switch to Jackson.
@sbernard31 can you tell me on which JVMs (versions too) you were able to reproduce this problem?
Hard question as this was a long time ago. If I remember correctly OpenJDK 7 and 8 I guess. I'm not able to give you more precise information. :disappointed:
IIRC I convinced myself at some point that this was a JDK issue, as the apparent race condition seemed to be fine according to the language specification. I have a strong impression that I never saw it on Oracle JDKs.
you might be right - i've reproduced using OpenJDK Runtime Environment (build 1.8.0_232-8u232-b09-1~deb9u1-b09)
however the issue is easily fixed and i patched our copy of this lib before moving away from it since. nfi why that wasn't just done years ago.
I don't think it could have been patched in any way without breaking existing code. That, combined with the slow death of the project, is why I think this wasn't and will never be fixed.
Regarding moving on from this project: I'd say existing users should either fork (possibly still as OSS, as there may be more people interested) or go for something that is actively maintained. Nobody should at this point add a dependency to this project.
ok, i can't disagree however i would have thought a major version update would have been fine. it is ok to have non-backwards-compatible changes occasionally - especially if it is to solve critical issues such as this.
If anybody is still interested in this: I took the PR from pstanton (https://github.com/ralfstx/minimal-json/pull/115), created a version 1.0.0 for it and published a binary in a new fork: https://github.com/tobiasbaum/minimal-json/releases/tag/v1.0.0
If anybody knows how to publish this to Maven Central, I'd be happy to know.
I face some deadlock during JUnit tests of my maven build. Some time ago, I was using v0.9.4 and deadlock was always reproducible. Since v0.9.5 and #77, I face it only sporadically.
Here is a thread dump when tests are stucked with v0.9.5
``` "pool-1-thread-11" #21 daemon prio=5 os_prio=0 tid=0x00007ff840403000 nid=0x16da in Object.wait() [0x00007ff80eb4f000] java.lang.Thread.State: RUNNABLE at com.eclipsesource.json.Json.