[BUG] Mirth Versions 4.4.1 and 4.4.2 custom-lib folder needs to be empty for web service listener channel to start about connect HOT 7 OPEN

I had the same issue starting a web service listener with custom-libs loaded when we upgraded to 4.4.1. I added the following to the mirth vmoptions files and it resolved the issue:
-Djavax.xml.ws.spi.Provider=com.sun.xml.ws.spi.ProviderImpl
I found this resolution in jakartaee/jax-ws-api#161

from connect.

ERROR when trying to start the Channel:

[2023-11-22 10:01:28.898] ERROR (com.mirth.connect.server.channel.ErrorTaskHandler:26): com.mirth.connect.donkey.server.StartException: Failed to start channel test web service (b125f74f-fd94-4b46-b277-16bf7077bb43).

at com.mirth.connect.donkey.server.channel.Channel.start(Channel.java:792)

at com.mirth.connect.server.controllers.DonkeyEngineController$DeployTask.doDeploy(DonkeyEngineController.java:2031)

at com.mirth.connect.server.controllers.DonkeyEngineController$DeployTask.execute(DonkeyEngineController.java:1835)

at com.mirth.connect.server.channel.ChannelTask.call(ChannelTask.java:67)

at com.mirth.connect.server.channel.ChannelTask.call(ChannelTask.java:16)

at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)

at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)

at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

at java.base/java.lang.Thread.run(Thread.java:834)

Caused by: java.lang.NullPointerException

at javax.xml.ws.Endpoint.create(Endpoint.java:161)

at com.mirth.connect.connectors.ws.WebServiceReceiver.onStart(WebServiceReceiver.java:209)

at com.mirth.connect.donkey.server.channel.SourceConnector.start(SourceConnector.java:106)

at com.mirth.connect.donkey.server.channel.Channel.start(Channel.java:768)

... 8 more

from connect.

@clarksss did @narupley 's suggestion on your forum post not work?

Forum link for reference for others: https://forums.mirthproject.io/forum/mirth-connect/support/184120-web-service-listener-not-starting-since-upgrade-from-mirth-connect-3-9-1-to-4-4-1

Most likely that is a bug in JAX-WS. Something like this: jakartaee/jax-ws-api#161

We're still including the old javax.xml.ws module, so perhaps at some point we should upgrade to the newer jakarta.xml.ws (and probably break a lot of Web Service channels in the process...)

Anyway you can either uncheck that Default resource in your channel's Summary -> Set Dependencies -> Library Resources

Or, go to Settings -> Resources and check "Load Parent-First" on the Default resource, which seems to workaround the jax-ws bug too (because it's a classloader issue).

from connect.

from connect.

I experienced the same issue moving from Mirth 4.1.1 on Java 8 to Mirth 4.4.2 on Java 11 (Amazon Coretto). I have changed the "Default Resource" (aka custom-lib) to parent-first behavior and my channels will deploy and start, now.

from connect.

After testing, my SOAP-based services are working exactly as expected after enabling parent-first load-order.

from connect.

Looks like my forum response was already copied above, but yeah, it sounds like this is a defect in the JAX-WS implementation library itself. At some point we should upgrade to the newer jakarta implementation (just a fork/continuation of the javax library I think), where it looks like that has already been fixed.

from connect.