Known issues
Table of contents:
- 1 Data Protection and Security Toolkit plugin
- 1.1 Plugin triggers WARNs upon Jira instance restart
- 1.1.1 Symptoms
- 1.1.2 Cause
- 1.1.3 Resolution
- 1.2 Insight fields cannot be anonymized
- 1.2.1 Symptoms:
- 1.2.2 Cause:
- 1.2.3 Resolutions:
- 1.1 Plugin triggers WARNs upon Jira instance restart
- 2 Announcements & Notifications
- 2.1 Not possible to create/update an announcement with large content
- 2.1.1 Symptoms
- 2.1.2 Cause
- 2.1.3 Resolution
- 2.1 Not possible to create/update an announcement with large content
- 3 How do I get information about known issue status?
Data Protection and Security Toolkit plugin
Plugin triggers WARNs upon Jira instance restart
Symptoms
0000-00-00 00:00:00,570+0100 FelixShutdown WARN [o.s.context.annotation.CommonAnnotationBeanPostProcessor] Destroy method on bean with name 'dataCleanerTaskJobStarter' threw an exception: java.lang.IllegalArgumentException: Job descriptor not found for job 'de.actonic.jira.gdpr.datacleaner.scheduling.DataCleanerTaskJobStarter:job'
0000-00-00 00:00:00,581+0100 FelixShutdown WARN [o.s.b.factory.support.DisposableBeanAdapter] Invocation of destroy method failed on bean with name 'sharedObjectsAnonymizer': java.lang.NullPointerException
0000-00-00 00:00:00,581+0100 FelixShutdown WARN [o.s.b.factory.support.DisposableBeanAdapter] Invocation of destroy method failed on bean with name 'clearProfileAnonymizer': java.lang.NullPointerException
0000-00-00 00:00:00,581+0100 FelixShutdown WARN [o.s.b.factory.support.DisposableBeanAdapter] Invocation of destroy method failed on bean with name 'removeFromGroupsAnonymizer': java.lang.NullPointerException
0000-00-00 00:00:00,582+0100 FelixShutdown WARN [o.s.context.annotation.CommonAnnotationBeanPostProcessor] Destroy method on bean with name 'dataLevelRulesJobStarter' threw an exception: java.lang.IllegalArgumentException: Job descriptor not found for job 'de.actonic.jira.gdpr.scheduling.DataLevelRulesJob:job'
where 0000-00-00 00:00:00 is date and time
Cause
The classes we use in some of our jobs are destroyed before our jobs. These are the subtleties of completing the job due to compatibility with different versions of Jira.
Resolution
As it doesn't affect the server and the jobs will run without issue after restarting jira, the fix is delayed.
Insight fields cannot be anonymized
Symptoms:
Insight fields data cannot be anonymized.
Cause:
Unfortunately, we could not achieve full content anonymization for objects are stored in apps and not in Jira itself. Insight as an app (add-on) is acting on the top of Jira API and provide additional content and relations for object, which are stores in a separated AO (Active Objects) tables.
Resolutions:
At the moment, we cannot implement full content anonymization for Insight app.
Announcements & Notifications
Not possible to create/update an announcement with large content
Symptoms
There is no maximum limit stipulated on an announcement size in Data Protection and Security Toolkit app. However, if an announcement is very large, a user may experience two problems:
Not possible to create a new announcement, some “Error 500” warning occurs on the “Create Announcement” page.
Not possible to update a new announcement, some “Error 500” warning occurs on the “Create Announcement” page.
Cause
This error manifests for large announcements, on the order of 2 MB or more. Apache Tomcat 5, by default, sets the maximum size of the acceptable HTTP POST request to 2MB.
Resolution
You can reconfigure Tomcat to accept larger requests. This can be done by increasing the allowable limit or just simply disabling this functionality.
Edit is
<Tomcat-Dir>/server.xml
.Set the Tomcat configuration parameter maxPostSize for the HTTPConnector to a larger value (in bytes) to increase the limit. Setting it to 0 will disable the size check.
See the Tomcat Configuration Reference for more information:
maxPostSize - "The maximum size in bytes of the POST which will be handled by the container FORM URL parameter parsing. The feature can be disabled by setting this attribute
to a value inferior or equal to 0. If not specified, this attribute is set to 2097152 (2 megabytes)."If using Apache web server, add the same parameter to the AJP connector instead.
How do I get information about known issue status?
Some changes of known issues can be implemented and published in major versions.
To get regular updates about new versions and release notes, you can start watching app updates by using Watch App option on Marketplace.
Please navigate to Overview page, scroll down to Resources and click on Watch App.