Custom SOAP plugin fails after upgrade from 7.13.6 to 8.5.5 - ProviderImpl could not be instantiated

[Morten Johnsen]

Our custom SOAP Integration app, which works fine in 7.13.6, no longer works on Jira 8.5.5. It's an add-on that leverages the scheduler, which fails with the following message:

javax.xml.ws.spi.Provider: Provider com.sun.xml.ws.spi.ProviderImpl could not be instantiated

runJob : Error,
java.util.ServiceConfigurationError: javax.xml.ws.spi.Provider: Provider com.sun.xml.ws.spi.ProviderImpl could not be instantiated
at java.util.ServiceLoader.fail(ServiceLoader.java:232)
at java.util.ServiceLoader.access$100(ServiceLoader.java:185)
at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:384)
at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404)
at java.util.ServiceLoader$1.next(ServiceLoader.java:480)
at javax.xml.ws.spi.Provider.getProviderUsingServiceLoader(Provider.java:180)
at javax.xml.ws.spi.Provider.provider(Provider.java:140)
at javax.xml.ws.Service.<init>(Service.java:92)
at javax.xml.ws.Service.create(Service.java:722)
at [package_name].m2jintegration.soapclient.M2MUtboundSoapClient.callGetRecords(M2MUtboundSoapClient.java:43)
at [package_name].m2jintegration.m2mqueuetask.M2MQueueTask.getM2MQueueRecords(M2MQueueTask.java:66)
at [package_name].m2jintegration.scheduler.impl.M2JSchedulerJobRunnerImpl.runJob(M2JSchedulerJobRunnerImpl.java:55)
at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:134)
at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:106)
at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:90)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:435)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeLocalJob(CaesiumSchedulerService.java:402)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:380)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:66)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:60)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:35)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.sun.xml.ws.spi.ProviderImpl
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at java.lang.Class.newInstance(Class.java:442)
... 19 more 

 Both versions (7.13.6 and 8.5.5) run on AdoptOpenJDK 1.8.

From what I've been able to gather, there's been some changes to what's being bundled in Jira 8.x compared to Jira 7 - does anyone have any idea what I need to do to get this working again? I'm not too familiar with SOAP, as this was an add-on that I had to take over when the developer quit, but our (new) rest implementation is nowhere near ready to take over for this add-on, and it's blocking our production upgrade.

If anyone has any idea I'd love some feedback :)