JIRA Log Files Fail to Load Due to a 'Is Not a Valid Plugin Artifact' Error
Symptoms
On startup, JIRA reports following in the log file:
atlassian-jira-http-access.log: The artifact URI file:/opt/atlassian-jira/plugins/installed-plugins/atlassian-jira-http-access.log is not a valid plugin artifact
atlassian-jira.log: The artifact URI file:/opt/atlassian-jira/plugins/installed-plugins/atlassian-jira.log is not a valid plugin artifact
atlassian-jira-http-dump.log: The artifact URI file:/opt/atlassian-jira/plugins/installed-plugins/atlassian-jira-http-dump.log is not a valid plugin artifact
atlassian-jira-soap-access.log: The artifact URI file:/opt/atlassian-jira/plugins/installed-plugins/atlassian-jira-soap-access.log is not a valid plugin artifact
atlassian-jira-sql.log: The artifact URI file:/opt/atlassian-jira/plugins/installed-plugins/atlassian-jira-sql.log is not a valid plugin artifact
atlassian-jira-slow-queries.log: The artifact URI file:/opt/atlassian-jira/plugins/installed-plugins/atlassian-jira-slow-queries.log is not a valid plugin artifact
atlassian-jira-soap-dump.log: The artifact URI file:/opt/atlassian-jira/plugins/installed-plugins/atlassian-jira-soap-dump.log is not a valid plugin artifact
Cause
JIRA creates its log file in the directory that the application was started from. JIRA treats any file inside <JIRA home>plugins/installed-plugin as a plugin file and attempt to load the file on start up resulting in the errors.
Resolution
Remove any log files from the <JIRA home>/plugins/installed-plugin directory and avoid starting up the application from within <JIRA home>/plugins/installed-plugin. Also, remove any sub-directory inside this folder.
Last modified on Mar 30, 2016
Powered by Confluence and Scroll Viewport.