WebLogic下Argument(s) "type" can't be null.

Start item appears Argument (s) "type" can not be null. Anomalies. Abnormal follows:

 

java.lang.IllegalArgumentException: Argument(s) "type" can't be null.
at com.sun.xml.bind.api.TypeReference.<init>(TypeReference.java:93)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:758)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:678)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:428)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:277)
Truncated. see log file for complete stacktrace
> 
<11.02.2014 22:28 Uhr FET> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1392146884362' for task '17'. Error is: 'weblogic.application.ModuleException: [HTTP:101216]Servlet: "ItvasDAS" failed to preload on startup in Web application: "itvas-das-0.0.1.war".
java.lang.IllegalArgumentException: Argument(s) "type" can't be null.
at com.sun.xml.bind.api.TypeReference.<init>(TypeReference.java:93)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:758)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:678)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:428)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:277)
at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:363)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:202)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:496)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:539)
at weblogic.wsee.jaxws.JAXWSDeployedServlet.getEndpoint(JAXWSDeployedServlet.java:183)
at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:139)
at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:68)
at weblogic.wsee.jaxws.JAXWSDeployedServlet.init(JAXWSDeployedServlet.java:54)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
...
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

 

 

Search for a long time, and finally on to the outside of the article (http://www.intropro.com/resources/blog/66-argument-s-type-can-t-be-null)

To find a solution : Remove jaxb-api-2.2.3-2.5.2.jar, jaxb- impl-2.2.4-1-2.5.2.jar, jaxb-xjc-2.2.4-1 under WEB-INF / lib -2.5.2.jar three jar package. problem solved.

Finally, the entire project was finally up and running successfully.

Summary: Tomcat project run under normal, abnormal WebLogic release to the next, mostly jar package incompatibility. Found an error class, find jar, you can delete the conflict.

Guess you like

Origin www.cnblogs.com/weixupeng/p/11140132.html