Redeploy issues with CXF and Glassfish

[Nick Stuart <ni...@portlandwebworks.com>]

We are having problems doing redeploys in our development instances. The
redeploys work and everything starts, but some CXF services stop working
(not all of them, which makes this even weirder). The affected services all
produce the following stacktrace:

Interceptor for {
http://my.company.com/}AuthenticationEndpoint#{http://my.company.com/}authenticate
has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault: Unmarshalling Error: This web container
has not yet been started
        at
org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(JAXBEncoderDecoder.java:881)
~[cxf-rt-databinding-jaxb-2.7.13.jar:2.7.13]
        at
org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(JAXBEncoderDecoder.java:702)
~[cxf-rt-databinding-jaxb-2.7.13.jar:2.7.13]
        at
org.apache.cxf.jaxb.io.DataReaderImpl.read(DataReaderImpl.java:160)
~[cxf-rt-databinding-jaxb-2.7.13.jar:2.7.13]
        at
org.apache.cxf.interceptor.DocLiteralInInterceptor.getPara(DocLiteralInInterceptor.java:324)
~[cxf-api-2.7.13.jar:2.7.13]
        at
org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:125)
~[cxf-api-2.7.13.jar:2.7.13]
        at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
~[cxf-api-2.7.13.jar:2.7.13]
        at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
[cxf-api-2.7.13.jar:2.7.13]
        at
org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:241)
[cxf-rt-transports-http-2.7.13.jar:2.7.13]
        at
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:248)
[cxf-rt-transports-http-2.7.13.jar:2.7.13]
        at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:222)
[cxf-rt-transports-http-2.7.13.jar:2.7.13]
        at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:153)
[cxf-rt-transports-http-2.7.13.jar:2.7.13]
        at
org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:171)
[cxf-rt-transports-http-2.7.13.jar:2.7.13]
        at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
[cxf-rt-transports-http-2.7.13.jar:2.7.13]
        at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
[cxf-rt-transports-http-2.7.13.jar:2.7.13]
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
[javax.servlet-api.jar:3.1.0]
        at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:262)
[cxf-rt-transports-http-2.7.13.jar:2.7.13]
        at
org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1682)
[web-core.jar:na]

All our services have the same interceptor (and only 1 interceptor on
them), and all are configured the same way:

       <jaxws:client id="authenticationEndpoint"
  serviceClass="my.AuthenticationEndpointPortType"
  address="#{endpointBase}authentication">
<jaxws:outInterceptors>
<ref bean="messageSecurityInterceptor"/>
</jaxws:outInterceptors>
</jaxws:client>

This happens on GF 4.0 and 4.1 with both JDK 1.7 and 1.8. Any ideas? Should
I open a bug or is the purely a GF issue?

Thanks for the help!