Tomcat Reports Package Scanner Found Duplicates when Starting Jira
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
When Jira is started, Tomcat will report WARN errors, indicating duplicate packages are found.
The following appears in the atlassian-jira.log file:
1
2
3
4
5
6
7
8
9
10
2012-12-08 04:50:09,499 pool-2-thread-1 INFO [atlassian.plugin.manager.DefaultPluginManager] Initialising the plugin system
2012-12-08 04:50:10,236 pool-2-thread-1 WARN [org.twdata.pkgscanner.ExportPackageListBuilder] Package Scanner found duplicates for package 'javax.el' with different versions. Files: tomcat-el-api-2.2.jar and tomcat-i18n-es-7.0.26.jar
'/usr/share/java/tomcat-el-api-2.2.jar'
'/usr/share/java/tomcat-i18n-es-7.0.26.jar'
2012-12-08 04:50:10,321 pool-2-thread-1 WARN [org.twdata.pkgscanner.ExportPackageListBuilder] Package Scanner found duplicates for package 'javax.el' with different versions. Files: tomcat-i18n-es-7.0.26.jar and tomcat-el-api-2.2.jar
'/usr/share/java/tomcat-i18n-es-7.0.26.jar'
'/usr/share/java/tomcat-el-api-2.2.jar'
2012-12-08 04:50:10,331 pool-2-thread-1 WARN [org.twdata.pkgscanner.ExportPackageListBuilder] Package Scanner found duplicates for package 'org.apache.commons.pool.impl' with different versions. Files: commons-pool-1.5.4.jar and commons-pool-1.5.6.jar
'/var/lib/tomcat7/webapps/jira_5.2.1/WEB-INF/lib/commons-pool-1.5.4.jar'
'/usr/share/java/commons-pool-1.5.6.jar'Cause
Java packages (JAR files) in Tomcat, Java and JIRA's lib directories are conflicting, indicating there are multiple versions installed for the same Java package. This error is more likely to occur on Tomcat EAR/WAR installations.
Resolution
As per updating your Tomcat libraries, ensure that if installing JIRA WAR into a Tomcat that is not bundled, there are no conflicting Java packages. In the above example:
The
Tomcat-i18n-espackage relates to Spanish translations and can be safely ignored. If Spanish translations are not required, this package can be removed.The
commons-poolpackage conflict can cause problems as there are version mismatches, and JIRA have may not been tested with the 1.5.6 version. This could cause problems with the usage of JIRA and the recommended fix is to remove thecommons-poolpackage from Tomcat.
These JARs are actually located in /usr/share/tomcat7/lib - they are symbolic links to /usr/share/java. For example:
1
2
3
[aquaman@avengersmansion|16:10:52 /usr/share/tomcat7/lib]
$ ll commons-pool.jar
lrwxrwxrwx 1 root root 27 2011-09-08 23:24 commons-pool.jar -> ../../java/commons-pool.jarThey can be removed by removing the symbolic link in /usr/share/tomcat7/lib. This will prevent other WAR files from using them, however we do not support deployment of multiple applications into the same Tomcat.
ℹ️ We recommend using the bundled Tomcat installer as it is significantly easier to use, maintain, upgrade and support. Additionally, these instructions are for Debian/Ubuntu. If you have any concerns about using them, please use the recommended installer, as in our Installing Jira docs.
Was this helpful?