SOAP web service throws a stacktrace when raising a user exception

[kiwipetedev]

I have a SOAP web service deployed on GF 7.0.15. I have recently upgraded the web service from Java 8 to Java 17. In the web service, I raise exceptions caused by user errors. With Java 8, these errors are sent back to the client, and the user sees an appropriate error message. However, with Java 17, a stacktrace is produced in the web service itself, and this is reported back to the client as a 500 error.

This is the stacktrace from the GF logs:

[2025-07-02T10:48:15.647104+12:00] [GF 7.0.15] [SEVERE] [] [com.sun.xml.ws.transport.http.HttpAdapter] [tid: _ThreadID=94 _ThreadName=http-l
istener-1(1)] [levelValue: 1000] [[
  class org.glassfish.jaxb.runtime.v2.runtime.JAXBContextImpl cannot be cast to class org.glassfish.jaxb.runtime.api.JAXBRIContext (org.glas
sfish.jaxb.runtime.v2.runtime.JAXBContextImpl is in unnamed module of loader org.glassfish.web.loader.WebappClassLoader @a83f89; org.glassfi
sh.jaxb.runtime.api.JAXBRIContext is in unnamed module of loader org.apache.felix.framework.BundleWiringImpl$BundleClassLoader @5a52b)
java.lang.ClassCastException: class org.glassfish.jaxb.runtime.v2.runtime.JAXBContextImpl cannot be cast to class org.glassfish.jaxb.runtime
.api.JAXBRIContext (org.glassfish.jaxb.runtime.v2.runtime.JAXBContextImpl is in unnamed module of loader org.glassfish.web.loader.WebappClas
sLoader @a83f89; org.glassfish.jaxb.runtime.api.JAXBRIContext is in unnamed module of loader org.apache.felix.framework.BundleWiringImpl$Bun
dleClassLoader @5a52b)
        at com.sun.xml.ws.db.glassfish.JAXBRIContextFactory.newContext(JAXBRIContextFactory.java:45)
        at com.sun.xml.ws.spi.db.BindingContextFactory.create(BindingContextFactory.java:122)
        at com.sun.xml.ws.message.jaxb.JAXBMessage.create(JAXBMessage.java:136)
        at com.sun.xml.ws.fault.SOAPFaultBuilder.createSOAP11Fault(SOAPFaultBuilder.java:414)
        at com.sun.xml.ws.fault.SOAPFaultBuilder.createSOAPFaultMessage(SOAPFaultBuilder.java:189)
        at com.sun.xml.ws.fault.SOAPFaultBuilder.createSOAPFaultMessage(SOAPFaultBuilder.java:177)
        at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:406)
        at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:832)
        at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:386)
        at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:139)
        at org.glassfish.webservices.JAXWSServlet.doPost(JAXWSServlet.java:140)
        at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:547)
        at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:614)
        at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1368)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:200)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:118)
        at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:563)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:504)
        at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:71)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:121)
        at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:293)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:186)
        at com.sun.enterprise.v3.services.impl.ContainerMapper$HttpHandlerCallable.call(ContainerMapper.java:425)
        at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:144)
        at org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:174)
        at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:153)
        at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:196)
        at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:88)
        at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:246)
        at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:178)
        at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:118)
        at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:96)

I'm not sure where to start to determine the cause of this. Does anyone know what is causing this?

[dmatej]

Would you have time to create some small reproducer ie. adding a test as a PR to the application-tests maven module?

We put sources of the application to the src/main/... directories, test to the src/test/... directories, then we use ShrinkWrap to create an archive or a set of archives and deploy it just as user would do that, and finally run the test.

See HttpSoapEmbeddedAuthTest as an example with WSDL and SOAP, which is quite complicated test but still not much hard to understand.

My first guess - can you check the war file or ear file if there are no Java EE or Jakarta EE API jars from an older version? In your project they should be all declared as a <scope>provided</scope>, because they could be in conflict with server's modules.

I would also recommend to try the latest version, 7.0.25.

[OndroMih]

Hi @kiwipetedev, this looks like a complex issue and would require deeper investigation. Feel free to contact our engineering team at omnifish.ee/contact-us or even book a free consultation call with us.

[kiwipetedev]

Hi Ondro, thanks for your reply. I tried booking a free consultation call twice, but both times I got an error. The last error code was this - tid-ced952c2-624a-4270-8916-4f979b96e890.

[OndroMih]

Thanks for the info.

Feel free to send us a message via the contact form and just write “I’d like to request a free consultancy call” and write which time and timezone. We’ll schedule a call with you.

i tested the link to schedule the call and it worked for me. Maybe try again and it will work for you. Or just write us via the form.