java.lang.NoClassDefFoundError:无法初始化类 weblogic.wsee.jaxws.spi.WLSProvider

声明:本页面是StackOverFlow热门问题的中英对照翻译,遵循CC BY-SA 4.0协议,如果您需要使用它,必须同样遵循CC BY-SA许可,注明原文地址和作者信息,同时你必须将它归于原作者(不是我):StackOverFlow 原文地址: http://stackoverflow.com/questions/20204632/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me): StackOverFlow

提示:将鼠标放在中文语句上可以显示对应的英文。显示中英文
时间:2020-08-13 00:16:09  来源:igfitidea点击:

java.lang.NoClassDefFoundError: Could not initialize class weblogic.wsee.jaxws.spi.WLSProvider

javaweb-servicestomcat7weblogic-10.x

提问by sbala_20

I am trying to make a webservice call in a program and deployed that in tomcat server. But I am getting the error "java.lang.NoClassDefFoundError: Could not initialize class weblogic.wsee.jaxws.spi.WLSProvider". But this class is available in weblogic.jar and the same is there in tomcat/lib folder. Any suggestion on how to solve this exception?

我正在尝试在程序中进行网络服务调用并将其部署在 tomcat 服务器中。但我收到错误“java.lang.NoClassDefFoundError:无法初始化类 weblogic.wsee.jaxws.spi.WLSProvider”。但是这个类在 weblogic.jar 中可用,在 tomcat/lib 文件夹中也是如此。有关如何解决此异常的任何建议?

EVERE: Servlet.service() for servlet [test] in context with path [/VTM-Engg-UI] threw exception [Handler processing failed; nested exception is

EVERE: Servlet.service() for servlet [test] in context with path [/VTM-Engg-UI] threw exception [Handler processing failed; nested exception is

**java.lang.NoClassDefFoundError: Could not initialize class weblogic.wsee.jaxws.spi.WLSProvider] with root causejava.lang.NoClassDefFoundError: Could not initialize class weblogic.wsee.jaxws.spi.WLSProvider**

**java.lang.NoClassDefFoundError: Could not initialize class weblogic.wsee.jaxws.spi.WLSProvider] with root causejava.lang.NoClassDefFoundError: Could not initialize class weblogic.wsee.jaxws.spi.WLSProvider**

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:357)
at java.lang.Class.newInstance(Class.java:310)
at javax.xml.ws.spi.FactoryFinder.newInstance(FactoryFinder.java:31)
at javax.xml.ws.spi.FactoryFinder.find(FactoryFinder.java:90)
at javax.xml.ws.spi.Provider.provider(Provider.java:83)
at javax.xml.ws.Service.<init>(Service.java:56)
at com.onstar.vcs.services.ws.ProcessVehicleTask.<init>(ProcessVehicleTask.java:42)
at com.onstar.vtm.manager.GetTaskWs.getTask(GetTaskWs.java:99)
at com.onstar.vtm.vehType.controller.VehTypeController.getGetTaskAttribute(VehTypeController.java:584)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.web.method.support.InvocableHandlerMethod.invoke(InvocableHandlerMethod.java:219)
at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:132)
at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:100)
at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:604)
at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:565)
at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:80)
at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:923)
at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:852)
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882)
at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:778)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:621)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1041)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:603)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)`

回答by Indu Devanath

There could be some possibilities.

可能有一些可能性。

The application can't access tomcat/lib/weblogic.jar file. May be it's not in application class path.

应用程序无法访问 tomcat/lib/weblogic.jar 文件。可能它不在应用程序类路径中。

There might be more than one jar file that contains weblogic.wsee.jaxws.spi.WLSProvider and this could be posing a problem.

可能有多个 jar 文件包含 weblogic.wsee.jaxws.spi.WLSProvider,这可能会造成问题。

Check to see the complete class name with package name. Sometimes the version of the jar file might be an issue as well.

检查以查看完整的类名和包名。有时 jar 文件的版本也可能是一个问题。

May be WLSProvider is not initialized properly. If you look at complete stack trace in your logs and see all the errors, there might be an error pointing to it's initialisation. Similar issue was posted long time back on JavaRanch - http://www.coderanch.com/t/582814/BEA-Weblogic/initialize-class-weblogic-wsee-jaxws

可能是 WLSProvider 未正确初始化。如果您查看日志中的完整堆栈跟踪并查看所有错误,则可能存在指向其初始化的错误。类似的问题在 JavaRanch 上发布了很长时间 - http://www.coderanch.com/t/582814/BEA-Weblogic/initialize-class-weblogic-wsee-jaxws

Dig deeper in your logs file and see if there are more errors. May be there is something else that needs to load before this class loads, and that might have not loaded properly.

深入挖掘您的日志文件,看看是否有更多错误。可能在加载此类之前需要加载其他内容,并且可能未正确加载。

Try paired programming. If you can get a peer looking at your problem, they might see something you might have missed. Many times two heads are better than one!

尝试结对编程。如果您可以让同行查看您的问题,他们可能会看到您可能遗漏的内容。很多时候两个头比一个好!

Good luck.

祝你好运。