Details
-
Bug
-
Resolution: Answered
-
Low
-
None
-
7.5.0
-
None
-
7.05
-
1
-
Severity 2 - Major
-
2
-
-
Description
Issue Summary
Duplicate JIRA license of the same type (Core, Software, or Service Desk ) will cause JIRA instance to go down.
Steps to Reproduce
- Input any of the JIRA license type, let's say Software license in this case into a JIRA instance.
- Access the database directly and update another Software license into the database table productlicense.
Expected Results
Jira will able to still start up or work properly but warn the administrators about the duplicate license.
Actual Results
The JIRA unable to start up / not working.
The below exception is thrown in the xxxxxxx.log file:
2019-01-14 13:32:40,653 ThreadPoolAsyncTaskExecutor::Thread 7 ERROR [c.a.p.osgi.factory.OsgiPlugin] Unable to start the plugin container for plugin 'com.atlassian.analytics.analytics-client' org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'productEventListener' defined in URL [bundle://19.0:0/META-INF/spring/atlassian-plugins-components.xml]: Unsatisfied dependency expressed through constructor argument with index 4 of type [com.atlassian.analytics.client.logger.AnalyticsLogger]: Error creating bean with name 'analyticsLogger' defined in URL [bundle://19.0:0/META-INF/spring/atlassian-plugins-components.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.atlassian.analytics.client.logger.Log4jAnalyticsLogger]: Constructor threw exception; nested exception is com.atlassian.cache.CacheException: java.lang.IllegalStateException: More than once license contains access to 'jira-software'. The licenses are: License for [jira-software]: AAAB2w0ODAoPeNp9kkFvozAQhe/+FZb2FskE2.... and License for [jira-software]: AAAB2g0ODAoPeNp9kk9vozAQxe/+FJb2Fskkk.....; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'analyticsLogger' defined in URL [bundle://19.0:0/META-INF/spring/atlassian-plugins-components.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.atlassian.analytics.client.logger.Log4jAnalyticsLogger]: Constructor threw exception; nested exception is com.atlassian.cache.CacheException: java.lang.IllegalStateException: More than once license contains access to 'jira-software'. The licenses are: License for [jira-software]: AAAB2w0ODAoPeNp9kkFvozAQhe/+FZb2FskE2.... and License for [jira-software]: AAAB2g0ODAoPeNp9kk9vozAQxe/+FJb2Fskkk..... at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:749) at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:185) at ... ... Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'analyticsLogger' defined in URL [bundle://19.0:0/META-INF/spring/atlassian-plugins-components.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.atlassian.analytics.client.logger.Log4jAnalyticsLogger]: Constructor threw exception; nested exception is com.atlassian.cache.CacheException: java.lang.IllegalStateException: More than once license contains access to 'jira-software'. The licenses are: License for [jira-software]: AAAB2w0ODAoPeNp9kkFvozAQhe/+FZb2FskE2.... and License for [jira-software]: AAAB2g0ODAoPeNp9kk9vozAQxe/+FJb2Fskkk..... at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:275)
Notes
- This issue was encountered in one of the Atlassian Support tickets and it was not reproducible without having to modify it through the database. So the actual cause of the issue is not known yet other than being able to reproduce the error.
- This issue is major as it will block the instance from starting up, so a mechanism for this to fail-safe or catch the exception is required.
Workaround
Simply compare the license key in the productlicense database table with the license key from My Atlassian (https://my.atlassian.com/) and remove the non-valid/old license key by the following SQL query by replacing the 12345, 54321 with the duplicate IDs:
DELETE FROM productlicense WHERE id = (12345,54321);
Attachments
Issue Links
- is superseded by
-
JRASERVER-76240 Applying a Jira product license might break the whole instance with duplicate license keys in the database
- Closed