Jira logs multiple FileNotFoundExceptions about missing JARs in common/lib


To reproduce:

  1. Create a new Jira plugin using atlas-create-jira-plugin.

  2. Change into the newly created plugin directory.

  3. Execute mvn jira:run. Jira starts up but logs pages of errors like this one:

This entire log message is repeated for the following JARs:

  • classes12.jar

  • p6psy.jar

  • commons-cli.jar

  • jts1_0.jar

  • carol.jar

  • jonas_timer.jar

There's a KB article about this, but it's aimed at production instances, not instances spun up by AMPS.

There's a Community question about it, with no solutions given (apart from forcing Tomcat 7, which is not correct, since Jira 7.x uses Tomcat 8).

The log messages above are benign, but they:

  • potentially obscure genuine stack traces

  • give a bad impression to ecosystem developers


ATLAS Version: 6.3.10
ATLAS Home: /usr/local/Cellar/atlassian-plugin-sdk/6.2.14/libexec
ATLAS Scripts: /usr/local/Cellar/atlassian-plugin-sdk/6.2.14/libexec/bin
ATLAS Maven Home: /usr/local/Cellar/atlassian-plugin-sdk/6.2.14/libexec/apache-maven-3.2.1
AMPS Version: 6.3.15
Executing: /usr/local/bin/mvn --version -gs /usr/local/Cellar/atlassian-plugin-sdk/6.2.14/libexec/apache-maven-3.2.1/conf/settings.xml
[MVNVM] Using maven: 3.3.9
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256M; support was removed in 8.0
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-11T03:41:47+11:00)
Maven home: /Users/aswan/.mvnvm/apache-maven-3.3.9
Java version: 1.8.0_131, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre
Default locale: en_AU, platform encoding: UTF-8
OS name: "mac os x", version: "10.13.3", arch: "x86_64", family: "mac"

Testing Notes

Add notes...


Andrew S
February 12, 2019, 9:07 AM

AMPS 8.0 was released with the fix on Feb 5, 2019.

Adil Bhayani
January 24, 2019, 1:05 AM

Hi Nazar,

Thanks for your comment. Andrew Swan has performed this piece of work and it should be released as part of the upcoming 8.0 release.

Kind regards,
Adil Bhayani

Nazar Sobchuk
January 24, 2019, 12:53 AM

Hi Adil, thanks for fixing this.

How can we get this fix into our dev environment?

Nicolaj Græsholt
December 18, 2018, 10:20 AM

While not really a viable solution, at least the output can be surpressed during development by reconfiguring Catalina to skip the jars in question.

1. run the application to generate the target folder.
2. navigate to target\container\tomcat8x\apache-tomcat-8.5.32\conf\catalina.properties <- your path might vary...
3. "around" line 108 the tomcat.util.scan.StandardJarScanFilter.jarsToSkip is configured. You can add more jars here.

I had to change line 134-136 from:


This is a nuisance, but at least the warnings are gone (for now.)

Prem Chudziński
November 1, 2018, 11:05 AM

@Alexander well said!!!



Andrew S


Andrew S

Add-on Type