【WebService异常分析】
1. Axis1.x框架的WebService
1.1 在生成server-config.wsdd时报错
命令:
java -cp %AXISCLASSPATH% org.apache.axis.client.AdminClient deploy.wsdd
报错内容:
D:\Tomcat\apache-tomcat-6.0.43\webapps\DemoWebService\WEB-INF>java -cp %AXISCLASSPATH% org.apache.axis.client.AdminClien
t deploy.wsdd
Processing file deploy.wsdd
Exception: AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.net.ConnectException: Connection refused: connect
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:529)
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.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:153)
at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:120)
at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:191)
at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:404)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:1792)
at org.apache.axis.client.AdminClient.process(AdminClient.java:439)
at org.apache.axis.client.AdminClient.process(AdminClient.java:404)
at org.apache.axis.client.AdminClient.process(AdminClient.java:410)
at org.apache.axis.client.AdminClient.process(AdminClient.java:320)
at org.apache.axis.client.AdminClient.main(AdminClient.java:463)
{http://xml.apache.org/axis/}hostname:1MLVINUF6M8NOUS
}}}如我的deploy.wsdd文件如下:
<?xml version="1.0" encoding="UTF-8"?> <deployment xmlns="http://xml.apache.org/axis/wsdd/"xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"><service name="HelloWorldWSDD" provider="java:RPC"><parameter name="className" value="cn.hw.ws.HelloWorldWSDD" /><!-- 代表所有的方法都暴露 --><parameter name="allowedMethods" value="*" /><parameter name="scope" value="request" /></service> </deployment>
解决办法
dos命令到WEB-INF下,命令改为:java -cp %AXISCLASSPATH% org.apache.axis.client.AdminClient -l http://localhost:8181/axis/services/HelloWorldWSDD deploy.wsdd参考文档: webservice Axis发布deploy.wsdd出错, {http://xml.apache.org/axis/}stackTrace:java.net.ConnectException: Coction refused: connect
1.2 将不带报名的类HelloWorldService放到tomcat的axis工程中,在浏览器中访问,点击Click to see the WSDL 报错
- 报错内容
AXIS error
Sorry, something seems to have gone wrong… here are the details:Fault - Failed to determine deployed service names.; nested exception is:
org.apache.axis.ConfigurationException: Could not find class for the service named: cn.hw.ws.HelloWorldWSDD
Hint: you may need to copy your class files/tree into the right location (which depends on the servlet system you are using).; nested exception is:
java.lang.ClassNotFoundException: cn.hw.ws.HelloWorldWSDD
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode:
faultString: Could not find class for the service named: cn.hw.ws.HelloWorldWSDD
Hint: you may need to copy your class files/tree into the right location (which depends on the servlet system you are using).; nested exception is:
java.lang.ClassNotFoundException: cn.hw.ws.HelloWorldWSDD
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:1MLVINUF6M8NOUSCould not find class for the service named: cn.hw.ws.HelloWorldWSDD
Hint: you may need to copy your class files/tree into the right location (which depends on the servlet system you are using).; nested exception is:
java.lang.ClassNotFoundException: cn.hw.ws.HelloWorldWSDD
at org.apache.axis.providers.java.JavaProvider.getServiceClass(JavaProvider.java:432)
at org.apache.axis.providers.java.JavaProvider.initServiceDesc(JavaProvider.java:461)
……
- 原因分析
在tomcat中的axis工程原来部署过HelloWorldWSDD类,虽然该类在tomcat中删除了,但是其发布用的配置文件“server-config.wsdd”还在tomcat中。删除该文件,然后重启tomcat,在tomcat重启的过程中会报出”Unable to find config file. Creating new servlet engine config file: /WEB-INF/server-config.wsdd“,应该是tomcat的某个文件中有记录,所以重启时会显示该记录,但是并不影响其他类HelloWorldService的发布。
1.3 Dos进行webService发布时报错
- 报错内容
D:\Tomcat\apache-tomcat-6.0.43\webapps\DemoWebService\WEB-INF>java -cp %AXISCLASSPATH% org.apache.axis.client.AdminClien
t -l http://localhost:8181/DemoWebService/services/AdminService deployComplex.wsdd
Processing file deployComplex.wsdd
- Exception:
org.xml.sax.SAXException: Fatal Error: URI=null Line=2: Element type “deployment” must be followed by either attribute s
pecifications, “>” or “/>”.
at org.apache.axis.utils.XMLUtils ParserErrorHandler.fatalError(XMLUtils.java:723)atcom.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177)atcom.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)atcom.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414)atcom.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.seekCloseOfStartTag(XMLDocumentFragmentScannerImpl.java:1395)atcom.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:285)atcom.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl ParserErrorHandler.fatalError(XMLUtils.java:723) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388) at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.seekCloseOfStartTag(XMLDocumentFragmen tScannerImpl.java:1395) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.ja va:285) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImplNSContentDriver.scanRootElementHook(XMLNSDoc
umentScannerImpl.java:626)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3104)atcom.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl FragmentContentDriver.next(XMLDocument FragmentScannerImpl.java:3104) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImplPrologDriver.next(XMLDocumentScannerImpl.java:
922)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScanne
rImpl.java:511)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:235)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:284)
at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:369)
at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:388)
at org.apache.axis.message.SOAPBodyElement.getDocumentElement(SOAPBodyElement.java:90)
at org.apache.axis.message.SOAPBodyElement.(SOAPBodyElement.java:79)
at org.apache.axis.client.AdminClient.process(AdminClient.java:438)
at org.apache.axis.client.AdminClient.process(AdminClient.java:404)
at org.apache.axis.client.AdminClient.process(AdminClient.java:410)
at org.apache.axis.client.AdminClient.process(AdminClient.java:320)
at org.apache.axis.client.AdminClient.main(AdminClient.java:463)
Exception: org.xml.sax.SAXException: Fatal Error: URI=null Line=2: Element type “deployment” must be followed by either
attribute specifications, “>” or “/>。.
错误原因分析
我在编写deployComplex.wsdd时,里面含有中文注释。将该中文注释删除,然后重新发布即可。可以将deployComplex.wsdd中的encoding=”UTF-8”改为encoding=”gbk”。参考文档:Invalid byte 2 of 2-byte UTF-8 sequence解决方案
1.3 WebService发布成功,客户端执行报Connection refused异常
报错内容
Exception in thread “main” AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.net.ConnectException: Connection refused: connect
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:529)
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.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:153)
at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:120)
at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:191)
at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:404)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at cn.hw.ws.client.UploadFileClient.main(UploadFileClient.java:51)
{http://xml.apache.org/axis/}hostname:1MLVINUF6M8NOUS原因分析
客户端代码中url地址错误,如下面代码中的url与发布的服务地址不符合String url = "http://localhost:8080/AxisWebService/services/UploadFile"; Service service = new Service(); Call call = (Call) service.createCall(); call.setTargetEndpointAddress(url);
【WebService异常分析】相关推荐
- [解决问题]selenium.remote.UnreachableBrowserException 异常分析并解决问题
[解决问题]selenium.remote.UnreachableBrowserException 异常分析并解决问题 参考文章: (1)[解决问题]selenium.remote.Unreachab ...
- java.lang.ArrayIndexOutOfBoundsException异常分析及解决
2019独角兽企业重金招聘Python工程师标准>>> java.lang.ArrayIndexOutOfBoundsException异常分析及解决 这是一个非常常见的异常,从名字 ...
- LCD显示异常分析——开机闪现花屏【转】
转自LCD显示异常分析--开机闪现花屏 最近在工作中,有同事遇到LCD开机瞬间会闪现雪花屏的问题,而这类问题都有个共同点,那就是都发生在带GRAM的屏上,同样的问题,在休眠唤醒时也会出现. 其实这类问 ...
- java异常——分析堆栈跟踪元素+使用异常机制的技巧
[0]README 0.1) 本文描述+源代码均 转自 core java volume 1, 旨在理解 java异常--分析堆栈跟踪元素+使用异常机制的技巧 的相关知识: [1]分析堆栈跟踪元素相关 ...
- Linux Kernel Oops异常分析
0.linux内核异常常用分析方法 异常地址是否在0附近,确认是否是空指针解引用问题 异常地址是否在iomem映射区,确认是否是设备访问总线异常问题,如PCI异常导致的地址访问异常 异常地址是否在st ...
- createsemaphore 异常_浅析SPC之异常分析
未来能源的短缺及资源匮乏,导致各国都在寻求替代能源以避免发生无资源可用的情况.汽油替代能源-生质酒精由此得到了广泛的应用. 生质酒精属于生质燃料(Biofuel)的一种,是由生物或化学转换成生物质(b ...
- Spring Boot————BeanCreationNotAllowedException异常分析
引言 在对数据库进行新增记录的JUnit测试时,抛出一个BeanCreationNotAllowedException异常: 异常分析与解决 异常信息太长,图片截不下,粘贴来看: Exception ...
- Enterprise Services (COM+)服务组件开发异常分析
Enterprise Services (COM+)服务组件开发异常分析<?xml:namespace prefix = o ns = "urn:schemas-microsoft-c ...
- 经验:Library Cache Lock之异常分析-云和恩墨技术通讯精选
亲爱的读者朋友: 为了及时共享行业案例,通知共性问题,达成共享和提前预防,我们整理和编辑了<云和恩墨技术通讯>,通过对过去一段时间的知识回顾,故障归纳,以期提供有价值的信息供大家参考.同时 ...
- FPGA系统时间戳偶尔异常分析及定位
1.1 FPGA系统时间戳偶尔异常分析及定位 1.1.1 本节目录 1)本节目录: 2)本节引言: 3)FPGA简介: 4)FPGA系统时间戳偶尔异常分析及定位: 5)结束语. 1.1.2 本节引言 ...
最新文章
- 用 Python 实现隐身,我可以 | 文末福利
- Spring4.1新特性——Spring MVC增强
- ITK:计算两个图像之间的均方度量值
- 为什么物联网没有杀手级应用
- 马化腾联手10余位科学家发起科学探索奖,腾讯基金投入10亿元启动资金
- pcb只开窗不镀锡_案例图解射频PCB设计要点
- jsp项目放入宝塔windows环境_商业裂变,之项目技术实战(第八节:宝塔面板介绍)...
- 递归和尾递归的区别和原理
- wget命令详解_嵌入式学习之 Wget 命令详解
- PECL PEAR php扩展模块的简便安装方式
- python 决策树回归参数_python决策树之CART分类回归树详解
- 返回路径平面上的间隙_PCB EMC问题:最常见的返回路径不连续
- 计算机考研数据库题库
- 从excel文件xlsx中特定单元格中提取图片
- 视频录制软件有哪些?4款录制视频软件,免费下载
- 免费下载有声读物获取您自己!
- 华为设备:清除配置详解
- linux怎么添加用户并赋予root权限
- ResNet :( residual 、residual bottleneck)
- 6 Processes 下
热门文章
- 三国争霸 Linux三款音乐播放器全方位PK
- PAT (Basic Level) Practice 1~7
- 谈谈创业这点事(7)
- 【贝叶斯算法分类】基于朴素贝叶斯算法(bayesian)的数据分类预测附matlab代码
- 已解决FileNotFoundError: [Errno 2] No such file or directory: ‘D:\\1. PDF‘
- 【亲测】七合一支付收款码 40+模板
- 1.Yolov5学习率调整策略
- 4 查询网站是否收录和利用百度做网站推广
- trust(fiduciary) words
- k8s部署springboot应用