重新部署后JAX-WS客户端无法连接(SymbolTable中的NullPointerException) [英] JAX-WS Client can't connect after redeployment (NullPointerException in SymbolTable)

查看:139
本文介绍了重新部署后JAX-WS客户端无法连接(SymbolTable中的NullPointerException)的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

当我们使用jax-ws客户端重新部署Web应用程序时,客户端无法连接到Web服务。连接到服务器时,它会抛出此异常:

When we redeploy our webapplication with an jax-ws client, the client can not connect to the webservice. While connecting to the server it throws this exception:

java.lang.NullPointerException: null
at com.ctc.wstx.util.SymbolTable.findSymbol(SymbolTable.java:385) ~[woodstox-core-asl-4.0.8.jar:4.0.8]
at com.ctc.wstx.sr.StreamScanner.parseLocalName(StreamScanner.java:1833) ~[woodstox-core-asl-4.0.8.jar:4.0.8]
at com.ctc.wstx.sr.BasicStreamReader.handleNsAttrs(BasicStreamReader.java:2963) ~[woodstox-core-asl-4.0.8.jar:4.0.8]
at com.ctc.wstx.sr.BasicStreamReader.handleStartElem(BasicStreamReader.java:2907) ~[woodstox-core-asl-4.0.8.jar:4.0.8]
at com.ctc.wstx.sr.BasicStreamReader.handleRootElem(BasicStreamReader.java:2049) ~[woodstox-core-asl-4.0.8.jar:4.0.8]
at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2029) ~[woodstox-core-asl-4.0.8.jar:4.0.8]
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1100) ~[woodstox-core-asl-4.0.8.jar:4.0.8]
at com.sun.xml.internal.ws.util.xml.XMLStreamReaderFilter.next(XMLStreamReaderFilter.java:81) ~[na:1.7.0-ea]
at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.next(XMLStreamReaderUtil.java:78) ~[na:1.7.0-ea]
at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.nextContent(XMLStreamReaderUtil.java:99) ~[na:1.7.0-ea]
at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.nextElementContent(XMLStreamReaderUtil.java:89) ~[na:1.7.0-ea]
at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.hasWSDLDefinitions(RuntimeWSDLParser.java:231) ~[na:1.7.0-ea]
at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:141) ~[na:1.7.0-ea]
at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:120) ~[na:1.7.0-ea]
at com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(WSServiceDelegate.java:256) ~[na:1.7.0-ea]
at com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:219) ~[na:1.7.0-ea]
at com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:167) ~[na:1.7.0-ea]
at com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:95) ~[na:1.7.0-ea]
at javax.xml.ws.Service.<init>(Service.java:77) ~[na:1.7.0-ea]

重启TomCat后,客户端可以再次成功连接到服务器。
(使用JDK 6和JDK 7测试)

After restarting TomCat the client could successfully connect to the sever again. (Tested with JDK 6 and JDK 7)

推荐答案

我们将使用spring-ws,通过重新部署进行测试没问题。

We'll use spring-ws instead, tested with redeploying without a problem.

这篇关于重新部署后JAX-WS客户端无法连接(SymbolTable中的NullPointerException)的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆