-
Bug
-
Resolution: Fixed
-
High
-
None
Symptom: Webhooks does not work from one week to another.
On the logs:
@40000000557e8c9d11e30484 ___ FAILED PLUGIN REPORT _____________________ @40000000557e8c9d11e30484 @40000000557e8c9d11e3086c 1 plugin failed to load during JIRA startup. @40000000557e8c9d11eee394 @40000000557e8c9d11eee77c 'com.atlassian.jira.plugins.webhooks.jira-webhooks-plugin' - 'JIRA WebHooks Plugin' failed to load. @40000000557e8c9d11eeeb64 Application context initialization for 'com.atlassian.jira.plugins.webhooks.jira-webhooks-plugin' has timed out @40000000557e8c9d11eeef4c @40000000557e8c9d11eeef4c It has the following missing service dependencies : @40000000557e8c9d11eef334 &beanBuilderFactory of type (objectClass=com.atlassian.jira.rest.v2.issue.builder.BeanBuilderFactory) @40000000557e8c9d11fb10c4 @40000000557e8c9d11fb14ac It was loaded from /sw/ondemand/plugins/jira-webhooks-plugin/jira-webhooks-plugin-1.7.4.jar
Fix:
The fix requires a JIRA restart so it will be deployed to instances depending on the region they are located to minimise impact.
EMEA is scheduled for: June 24, 12:00AM UTC
Workaround:
We can apply the fix manually that requires ~10 minutes of downtime. Contact Support with details on when would this be most suitable for your team.
- is duplicated by
-
JRACLOUD-65722 Transition issue throws "Could not load FunctionProvider class" error
- Closed
-
JRACLOUD-65890 WebHooks don't work
- Closed
-
JRASERVER-43956 JIRA OnDemand now presents workflow error: Could not load FunctionProvider class
- Closed
- is related to
-
JRASERVER-43981 How to verify JIRACloud webhook functionality is working
- Closed