本文介绍了Web 服务在 WSO2 ESB 上返回空的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们使用 WSO2 ESB 来访问我们的服务.我们在 Application Server 上开发了服务,我们可以通过使用 ESB 代理服务来访问它们.然而,有时 ESB 会向我们的客户返回空值.如果我直接调用 AS,我可以看到响应.当 ESB 开始变为空值时,它会影响我们在 ESB 上的所有服务.我们找不到如何解决这个问题.当我们重新启动 ESB 服务器时,一切又开始工作了.

We are using WSO2 ESB to access our services. We have developed services on Application Server and we could access them via using ESB Proxy services. However sometimes ESB returns empty values to our clients. If i call AS directly i could see the response. When ESB starts to turn empty value it is effecting all of our servises on ESB. We could not find how could we fix the problem. When we restart the ESB server everything starting to work again.

我们使用的是 WSO2 ESB 4.6.0 和 WSO2 AS 5.0.2

We are using WSO2 ESB 4.6.0 and WSO2 AS 5.0.2

谢谢,

Ps:我正在执行此脚本以查看 Web 服务响应.但是 Web 服务响应为空.curl -d @request.xml -H "Content-Type: application/soap+xml;charset=UTF-8" "http://esbhostname.com:8280/services/Report"> response.xml

Ps: I am executing this script to look at web service response. But web service response is empty.curl -d @request.xml -H "Content-Type: application/soap+xml;charset=UTF-8" "http://esbhostname.com:8280/services/Report" > response.xml

推荐答案

我们在 passthrough 传输中发现了这样的问题..但是真的很难重现..我们注意到的是,wso2esb 4.6.0 丢弃了 POST 消息体有时..不确定根本原因是什么或在哪种情况下发生..一旦我们能够重现它,我们将尽快解决该问题..这个问题发生在直通传输上.如果你真的不需要直通传输,你可以切换到 nio tarnsport.为 nio 传输编辑axis2.xml 传输发送器/接收器.

we have noticed such an issue in passthrough transport..but it is really hard to reproduce..What we noticed is, wso2esb 4.6.0 drops POST message body sometimes..not sure what is the root cause or in which situation it happened..we will try to fix that issue soon once we are able to reproduce it..This issuse happens with passthrough transport..If you dont really need passthrough transport, you can switch to nio tarnsport. Edit the axis2.xml transport sender/receiver for nio transport.

这篇关于Web 服务在 WSO2 ESB 上返回空的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

09-06 04:07