-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: 3.13
-
Component/s: Infrastructure & Services - Application Lifecycle
-
3.13
As per the subject, this is part of the JiraStartupLogger:
___ Listeners ____________________
Instance Count : 4
Issue Cache Listener : com.atlassian.jira.event.listeners.cache.IssueCacheListener
Mail Listener : com.atlassian.jira.event.listeners.mail.MailListener
Issue Index Listener : com.atlassian.jira.event.listeners.search.IssueIndexListener
Support Kundenkommentar : com.atlassian.jira.toolkit.listener.AutoTransitionListener
JIRA 3.13 build: 330 (Enterprise Edition) started. You can now access JIRA through your web browser.
****************************************************************************************************************************************************************
2008-09-24 12:49:40,240 JiraQuartzScheduler_Worker-3 ERROR [action.admin.export.DefaultSaxEntitiesExporter] An exception occuring while writing the JIRA system info start commment
com.opensymphony.module.propertyset.InvalidPropertyTypeException
at com.opensymphony.module.propertyset.ofbiz.OFBizPropertySet.get(OFBizPropertySet.java:198)
at com.opensymphony.module.propertyset.AbstractPropertySet.getObject(AbstractPropertySet.java:327)
at com.atlassian.jira.startup.JiraSystemInfo.obtainListeners(JiraSystemInfo.java:467)
...
To replicate this error:
- Create a new JIRA 3.13 instance
- Install JIRA Toolkit plugin for this JIRA version
- Create a AutoTransitionListener
- Restart JIRA to view the error
This happens only when 3rd party listeners & services are installed into JIRA
