WebSphere应用出现java.lang.NoClassDefFoundError: DestBeanCreator错误求助

问题描述 #

在WebSphere Application Server（WAS）上运行应用流程时，抛出如下错误：

Caused by: org.apache.cxf.binding.soap.SoapFault: java.lang.NoClassDefFoundError: org.dozer.factory.DestBeanCreator (initialization failure)
        at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.unmarshalFault(Soap11FaultInInterceptor.java:86) ~[cxf-rt-bindings-soap-3.1.1.jar:3.1.1]
        at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:52) ~[cxf-rt-bindings-soap-3.1.1.jar:3.1.1]
        at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:41) ~[cxf-rt-bindings-soap-3.1.1.jar:3.1.1]
        at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) ~[cxf-core-3.1.1.jar:3.1.1]
        at org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:112) ~[cxf-core-3.1.1.jar:3.1.1]
        at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:69) ~[cxf-rt-bindings-soap-3.1.1.jar:3.1.1]
        at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:34) ~[cxf-rt-bindings-soap-3.1.1.jar:3.1.1]
        at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) ~[cxf-core-3.1.1.jar:3.1.1]
        at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:798) ~[cxf-core-3.1.1.jar:3.1.1]
        at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1641) ~[cxf-rt-transports-http-3.1.1.jar:3.1.1]
        at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1532) ~[cxf-rt-transports-http-3.1.1.jar:3.1.1]
        at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1330) ~[cxf-rt-transports-http-3.1.1.jar:3.1.1]
        at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) ~[cxf-core-3.1.1.jar:3.1.1]
        at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:652) ~[cxf-rt-transports-http-3.1.1.jar:3.1.1]
        at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) ~[cxf-core-3.1.1.jar:3.1.1]
        at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) ~[cxf-core-3.1.1.jar:3.1.1]
        at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514) ~[cxf-core-3.1.1.jar:3.1.1]
        at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423) ~[cxf-core-3.1.1.jar:3.1.1]
        at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324) ~[cxf-core-3.1.1.jar:3.1.1]
        at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277) ~[cxf-core-3.1.1.jar:3.1.1]
        at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96) ~[cxf-rt-frontend-simple-3.1.1.jar:3.1.1]
        at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139) ~[cxf-rt-frontend-jaxws-3.1.1.jar:3.1.1]

已知WEB-INF/lib目录下已存在版本为5.3.2的dozer jar包，以下是具体排查思路：

排查思路 #

• 检查类加载顺序：WAS默认类加载策略为PARENT_FIRST，可能优先加载服务器全局类库中旧版本或不兼容的dozer类。进入WAS控制台修改应用类加载器配置为PARENT_LAST，确保应用优先加载自身WEB-INF/lib中的类。
• 验证Dozer依赖完整性：Dozer 5.3.2依赖commons-beanutils、commons-lang、commons-logging等基础类库，检查WEB-INF/lib是否缺少这些依赖，或依赖版本与Dozer不兼容。
• 定位初始化失败根源：错误标注initialization failure，说明DestBeanCreator类能被找到，但初始化时抛出异常（如静态代码块执行失败、依赖类加载失败）。查看WAS的SystemOut.log等系统日志，寻找更底层的异常栈定位具体原因。
• 检查Jar包完整性：确认dozer-5.3.2.jar是否损坏，可重新下载官方版本替换，解压后检查是否存在org/dozer/factory/DestBeanCreator.class文件。
• 排查类加载器隔离问题：若应用部署在集群环境或与其他应用共享类加载器，可能存在类隔离冲突。检查应用类加载器配置，确保使用独立类加载器加载自身lib目录下的类。
• 检查权限配置：WAS的安全策略可能限制应用对dozer类的访问，导致无法加载或初始化。查看服务器Java安全策略文件，确认允许应用访问dozer相关类路径。

内容的提问来源于stack exchange，提问作者CaveBatman