Thanks to visit codestin.com
Credit goes to github.com

Skip to content

fix: Fix spurious NullPointerExceptions during executable war shutdown #588

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Oct 26, 2025
Merged

fix: Fix spurious NullPointerExceptions during executable war shutdown #588

merged 1 commit into from
Oct 26, 2025

Conversation

@chadlwilson
Copy link
Contributor

Executable wars don't set the classloader, because they do not initialize the scripting engine.

Currently you get the below during shutdown

ERROR: java.lang.NullPointerException: Cannot invoke "Object.getClass()" because "self" is null
java.lang.NullPointerException: Cannot invoke "Object.getClass()" because "self" is null
	at JarMain.invokeMethod(JarMain.java:268)
	at JarMain.invokeMethod(JarMain.java:263)
	at JarMain.run(JarMain.java:225)
	at WarMain.run(WarMain.java:367)
	at java.base/java.lang.Thread.run(Thread.java:1583)

@chadlwilson
fix: Fix spurious NullPointerExceptions during executable war shutdown
ce45eab 
Executable wars don't set the classloader, because they do not initialize the scripting engine.
@chadlwilson chadlwilson added this to the 2.1.1 milestone Oct 26, 2025
@chadlwilson chadlwilson merged commit 5ecf4c2 into jruby:master Oct 26, 2025
10 checks passed
@chadlwilson chadlwilson deleted the fix-cleanup-for-war branch October 26, 2025 11:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

2.1.1

Development

Successfully merging this pull request may close these issues.

1 participant

@chadlwilson