Axis Webservice 调用有时会失败，access.log 显示内容！
我们的应用程序是第三方 Web 服务（也是轴 1）的 Web 服务客户端（轴 1）。我们已经使用它好几年了。
几周以来，我们（作为客户端）在调用 Web 服务时有时会收到 HTTP 状态 400（错误请求）或读取超时。
奇怪的是，服务的 access.log 显示的是请求或响应的一部分，而不是 URL。它看起来像这样（看起来像请求字符串的结尾）
x.x.x.x -> y.y.y.y:8080 - - [timestamp] "POST /webservice HTTP/1.0" 200 16127 0
x.x.x.x -> y.y.y.y:8080 - - [timestamp] "POST /webservice HTTP/1.0" 200 22511 1
x.x.x.x -> y.y.y.y:8080 - - [timestamp] "il=\"true\"/><nsl:text xsi:type=\"xsd:string\" xsi:nil=\"true\"/></SOAPSomeOperation></soapenv:Body></soapenv:Envelope> Axis/1.4" 400 299 0
或（看起来像请求的字符串）
x.x.x.x -> y.y.y.y:8080 - - [timestamp] ":string\">some text</sometag><othertag>moretext" 400 299 0
或者在其他一些情况下它看起来像两个请求放在一起（...意味着 xml 字符串被遗漏）：
x.x.x.x -> y.y.y.y:8080 - - [timestamp] "...</someop></soapenv:Body></soapenv:Envelope>:xsd=\"http://www.w3.org/2001/XMLSchema\"...</soapenv:Body></soapenv:Envelope>" 400 299 0
应用程序日志没有给出任何提示。此类调用的频率为对该服务的所有调用的 1%。到目前为止，我所知道的唯一区别是，由于操作通知我们服务 URL 由于“服务器迁移”而发生了更改，因此发生了这种情况。
有人经历过这种现象吗？有人知道出了什么问题以及如何解决吗？
谢谢，
our app is a webservice client (axis 1) to a third party webservice (also axis 1). We use it for some years now.
Since a few weeks, we (as a client) get sometimes HTTP status 400 (bad request) or read timeouts when calling the webservice.
Strangely, the access.log of the service shows part of the request or the response instead of the URL. It looks like this (looks like the end of the request string)
x.x.x.x -> y.y.y.y:8080 - - [timestamp] "POST /webservice HTTP/1.0" 200 16127 0
x.x.x.x -> y.y.y.y:8080 - - [timestamp] "POST /webservice HTTP/1.0" 200 22511 1
x.x.x.x -> y.y.y.y:8080 - - [timestamp] "il=\"true\"/><nsl:text xsi:type=\"xsd:string\" xsi:nil=\"true\"/></SOAPSomeOperation></soapenv:Body></soapenv:Envelope> Axis/1.4" 400 299 0
or (some string out of the what looks like the request)
x.x.x.x -> y.y.y.y:8080 - - [timestamp] ":string\">some text</sometag><othertag>moretext" 400 299 0
or in some other cases it looks like two requests thrown together (... means xml string left out):
x.x.x.x -> y.y.y.y:8080 - - [timestamp] "...</someop></soapenv:Body></soapenv:Envelope>:xsd=\"http://www.w3.org/2001/XMLSchema\"...</soapenv:Body></soapenv:Envelope>" 400 299 0
Application log does not give any hints. Frequency of such call is 1% of all calls to that service. The only discriminator I know of so far is that it happens since operations informed us that the service url changed because of "server migration".
Has anyone experienced such phenomenon yet? Has somebody got an idea whats wrong and how to fix?
Thanks,
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我们没有这种确切的行为，但我们遇到了 Axis 1 的几个缺陷，这让我们遭受了很多痛苦。有问题的类之一是 Axis 的 HttpSender，它似乎不是线程安全的，并且还具有许多 错误。
访问日志错误的不规则性可能意味着它实际上与线程安全相关。无论如何，如果你有机会摆脱轴 1，那就立即去做。它已经有将近 5 年历史了，实际上已经是死产品了，有很多缺陷没有修复。
We didn't have this exact behavior, but we faced several defects of Axis 1 that made us suffer a lot. One of the faulty classes was Axis' HttpSender, which appeared to be not thread-safe and also had a number of bugs.
Irregularity of your access log errors may mean that it's actually thread-safeness related. In any case if you have a chance to get rid of Axis 1, then do it immediatly. It is almost 5 years old and actually dead product with a lot of defects unfixed.