exception containing itself as nested exception, causing maven endless loop about asciidoctorj HOT 7 OPEN

The AsciidoctorCoreException is simply wrapping the exception coming from JRuby, with no manipulation.

Can you provide a reproducer or the repo that's causing the issue? That way we can look further and see what flow inside JRuby is causing it.

from asciidoctorj.

That's weird.
Intuitively I would say that I see such circular references every day when debugging any problem in whatever software.
Or am I totally wrong here?

Also looking at this old question on SO it seems like this is not uncommon:
https://stackoverflow.com/questions/9233638/is-there-any-reason-to-set-an-exceptions-cause-to-itself

We can of cause argue whether it's a bad design or not, but I would say that if this is common in many libraries Maven should be able to handle that.

from asciidoctorj.

That's weird.
Intuitively I would say that I see such circular references every day when debugging any problem in whatever software.
Or am I totally wrong here?

Not weird, I had to research too because I had the same idea 😄 It's normal but getCause should return the null if there's such self-reference.

Seeing the stacktrace from the JIRA it comes from RubyLoadError which in turn ends up extending this suspicious method https://github.com/jruby/jruby/blob/73d3c1e3b5d0b6f5b774e32c30303a8d2bddb3c6/core/src/main/java/org/jruby/RubyException.java#L411-L413. But I'd like to confirm, hence the reproducer, we had had plenty of JRuby errors and never looped, I'd like to know what is the origin of the error.

from asciidoctorj.

Just FTR Maven 3.9.4 (coming soon) have a fix for this issue, while we still think this is "not our bad".
apache/maven@36db1e3

Also reported to JRuby jruby/jruby#7861

from asciidoctorj.

Just FTR Maven 3.9.4 (coming soon) have a fix for this issue, while we still think this is "not our bad". apache/maven@36db1e3

Also reported to JRuby jruby/jruby#7861

We are aware, I saw the posts, but I think we can do better than cross-posting. I am personally working on assumptions, not even the versions for asciidoctor-maven-plugin or AsciidoctorJ have been provided, and I haven't been able to cause a similar error on the latest releases.
If a reproducer can be provided, which I assume exists and is likely to be an open-source repo, I can pinpoint the exact repo, branch, and line of code. That will help to move the upstream fix much quicker and reduce guesses.

from asciidoctorj.

@abelsromero Unfortunately this is in a company project, and it hasn't even build a build on a commit, but rather on uncommitted changes. Since I've only found that looping process several hours later, and investigated it via heap dump, I can't even say what had been done when it was started. I do know that I had played around with enabling hyphenation, and that I had caused an error message by using a non supported language code via <hyphens>en</hyphens> in asciidoctor-maven-plugin attributes (instead of the correct en_us or en_uk), but I have not been able to reproduce that error situation by running several variations of this. I'm sorry, but it seems I cannot provide a reproducer.

from asciidoctorj.

Thanks, at least that's something, we know now it's PDF with a theme. We found a suspicious method in jRuby. It's a matter of making a path between those 2 points.

from asciidoctorj.