Jira plugin failing to load locally after Java SDK update: 404 error encountered

Other Questions Jira
1

I’m having trouble with a Jira plugin I made. After updating to Oracle SDK 23 I can’t access http://localhost:2990/jira/. The browser shows a 404 error.

The error message says:

HTTP Status 404 – Not Found
Description: The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.

The logs mention something about Illegal access: this web application instance has been stopped already. Could not load [com.google.gson.GsonBuilder].

I’ve tried:

  • Restarting the server
  • Running atlas-clean
  • Deleting the .m2/repository folder

None of these fixed it. My Java version is 23.0.1 and ATLAS Version is 8.2.7.

Any ideas what could be causing this? How can I get my plugin working again?

2

I’ve been through this headache too. Sounds like a classic case of version mismatch. Java 23 is pretty bleeding edge for Jira right now. Here’s what worked for me:

  1. Rolled back to Java 17. It’s rock-solid with current Jira setups.
  2. Double-checked JAVA_HOME was pointing to the right Java version.
  3. Updated my Atlassian SDK to the latest stable release.
  4. Ran ‘atlas-mvn clean install’ to rebuild everything from scratch.

Also, keep an eye on your plugin’s pom.xml. Sometimes dependencies can cause conflicts after major Java updates. If you’re still stuck, try running ‘atlas-debug’ and watch for any specific error messages during startup.

Remember, Atlassian usually lags a bit behind the latest Java releases for stability reasons. Sticking with LTS Java versions is often safer for plugin development.

3

hey there, i had a similar issue. try downgrading ur java version to 17 or 11. jira’s not fully compatible with java 23 yet. also, check if ur atlas-mvn is using the right java version. hope this helps!

4

I’ve encountered a similar issue, and in my experience the problem is linked to compatibility issues between Java 23 and the current version of the Atlassian SDK. I resolved the problem by downgrading to Java 17, which proved much more stable with Jira plugins. It is also important to ensure that the JAVA_HOME environment variable is set to the correct installation of Java. Updating the Atlassian SDK and clearing the Maven cache helped as well. Rebuilding the project and reviewing the plugin dependencies for any conflicts also contributed to resolving the issue.