org.apache.axis.ConfigurationException: No service named ldapOperate is available解决方法

最新推荐文章于 2018-11-15 19:09:14 发布

原创最新推荐文章于 2018-11-15 19:09:14 发布 · 1.1w 阅读

2 ·

CC 4.0 BY-SA版权

文章标签：

#log4j #web service

疑难杂症专栏收录该内容

5 篇文章

订阅专栏

本文解决在使用Axis1.4生成的webService时遇到的异常日志问题，通过调整log4j日志级别来避免误导性的日志记录。提供了详细步骤和链接以获取更深入的理解。

在调用使用axis1.4生成的webService时，老是报题目中的那个异常，但调用还是能通过，但看着还是让人不爽，也不知道会不会有什么隐患，在网上搜了大概是axis中自己的问题，解决的方法就是把log4j中日志的级别打高一点，由于E文水平有限，下面是问题解释的原文

Hi,

Not sure if you got you answer as yet but anyhow, I thought below details would help all folks who are having same problem.

This is logged because this code in AxisEngine (line 308 in Axis 1.x): 

depends on an exception being thrown on the first attempt (line 311) to then try a different method of finding the service (which succeeds if you see no log of the AxisFault on line 316). The log entry is created because a ConfigurationException logs itself (at DEBUG level) on creation (questionable practice, imho). To avoid this misleading log entry you'll want to add this to your log4j.properties file:

log4j.logger.org.apache.axis.ConfigurationException = INFO

Details can be found at the following link :
http://wiki.apache.org/ws/FrontPage/Axis/DealingWithCommonExceptions

Thanks,
Josh

参考：

https://forums.oracle.com/forums/thread.jspa?messageID=7009127