testing a JIRA upgrade from 6.4 =>7.0
i have a plugin that provides 2 mail handlers. I removed one of the handlers. I removed the class that defines the handler. I removed the corresponding <message-handler> entry from the atlassian-plugin.xml file.
However, upon server startup, throws error "<class of deleted handler > cannot be instantiated because there is no corresponding enabled module defining message-handler of such class"
looking at the plugins modules list, confirmed that the deleted handler has no more module listed here.
where else would JIRA be referencing this phantom handler?
Lance,
Is this your personal plugin or is it a plugin from Marketplace? If so, can you let us know which one?
Have you tried clearing the plugin cache?
JIRA_HOME/plugins/.bundled-plugins JIRA_HOME/plugins/.osgi-plugins
Regards,
Shannon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
i renamed the dir, restarted, JIRA created a new dir. Still get the phantom-handler error msg. :(
ERROR [] JIRA-Bootstrap null[null]: Cannot instantiate message handler 'com.jira.plugins.mail.handlers.XLSMailHandler. This service will not work until this problem is fixed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Lance,
Can you confirm if clearing the plugin cache was attempted as well? This doesn't require that you rename any directories. You must delete them.
Regards,
Shannon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
it seems to me that renaming that dir would effectively do the same thing, and it seemed like it did since the .osgi-plugins dir was recreated by JIRA
i deleted the .osgi-plugins dir and everything happened the same way. After JIRA restarted, the .osgi-plugins dir was recreated and then that same error message got spit out to the log file (cannot instantiate message handler). Thanks for your help btw
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Lance,
Can you show us the full startup sequence surrounding the error you're encountering? This will give us more information.
In addition, can you let me know which add-on this is that is causing you trouble?
Shannon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.