堆栈内存溢出
  简体   繁体   English

WSO2 REST API to capture invalid/valid xml request in WSO2 EI 6.1.1

[英]WSO2 REST API to capture invalid/valid xml request in WSO2 EI 6.1.1

 原文  2021-03-05 12:07:42  6   2    xml/ wso2/ wso2esb/ restapi/ wso2ei

问题描述

I am using WSO2 EI 6.1.1.I have designed Rest API which received xml payload as request.In this if request is valid i can able to print incoming request payload by using log mediator, often if request is wrong, unfortunately can't able to get exact request that sent into my system. I am using WSO2 EI 6.1.1.I have designed Rest API which received xml payload as request.In this if request is valid i can able to print incoming request payload by using log mediator, often if request is wrong, unfortunately can't能够获得发送到我的系统的确切请求。

Getting below exception when receives invalid xml request.收到无效的 xml 请求时出现以下异常。

Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character ' ' (code 32) (missing name?)

I need to capture the input request that sent by client whether it is valid or not.我需要捕获客户端发送的输入请求是否有效。 Kindly help me to resolve this issue.请帮我解决这个问题。

API Code: API 代码：

<?xml version="1.0" encoding="UTF-8"?>
<api context="/WSO2API" name="WSO2API" xmlns="http://ws.apache.org/ns/synapse">
    <resource methods="POST">
        <inSequence>
            <log level="custom">
                <property name="API Logger"
                    value="====Inside QRSag_NAC Lead Creation API Process Started====" />
                <property name="===Input Request Logger===" expression="$body" />
            </log>
            <log level="full" />
            <payloadFactory media-type="json" description="Form Response Payload">
                <format>{"StatusCode":"$1","Message":"$2"}</format>
                <args>
                    <arg value="200" />
                    <arg value="Success" />
                </args>
            </payloadFactory>
            <log level="custom">
            <property name="==Response==" expression="json-eval($.)"></property>
            </log>
            <property name="HTTP_SC" value="400" scope="axis2" type="STRING"
                description="HTTPStatusCode" />
            <property name="messageType" value="application/json" scope="axis2"
                type="STRING" description="HttpMessageType" />
            <respond />
        </inSequence>
        <outSequence />
        <faultSequence>
            <log level="custom" separator=",**, " description="FaultSequence">
                <property name="=====Faulty Response=====" value="Inside default Fault Sequence" />
                <property name="=====message=====" expression="get-property('ERROR_MESSAGE')" />

            </log>

            <payloadFactory media-type="json" description="Form Response Payload">
                <format>{"StatusCode":"$1","Message":"$2"}</format>
                <args>
                    <arg value="400" />
                    <arg value="Failure" />
                </args>
            </payloadFactory>
            <property name="HTTP_SC" value="400" scope="axis2" type="STRING"
                description="HTTPStatusCode" />
            <property name="messageType" value="application/json" scope="axis2"
                type="STRING" description="HttpMessageType" />
                <log level="custom">
            <property name="==Response==" expression="json-eval($.)"></property>
            </log>
            <respond />
        </faultSequence>
    </resource>
</api>

Valid Request:有效请求：

<leaddetails>
    <customer>
        <extdburn>0</extdburn>
        <title/>
        <forename>Jared</forename>
        <surname>Parker</surname>
        <mobile>0406008974</mobile>
        <email>Jwparke888@hotmail.com</email>
    </customer>
    
</leaddetails>

Invalid request:无效的请求：

<leaddetails>
    <customer>
        <extdburn>0</extdburn>
        <title/>
        <forename>**Jared & Justin**</forename>
        <surname>Parker</surname>
        <mobile>0406008000</mobile>
        <email>Jwparke888@hotmail.com</email>
    </customer>
    
</leaddetails>

Logs:日志：

[2021-03-05 17:27:54,003] []  INFO - LogMediator API Logger = ====Inside QRSag_NAC Lead Creation API Process Started====, ===Input Request Logger=== = <soapenv:Body xmlns:soapenv="h
ttp://schemas.xmlsoap.org/soap/envelope/"/>
[2021-03-05 17:27:54,004] [] ERROR - LogMediator Could not build full log message: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character ' ' (code 32) (missing name?)
 at [row,col {unknown-source}]: [6,26]
org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character ' ' (code 32) (missing name?)
 at [row,col {unknown-source}]: [6,26]
        at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)
        at org.apache.axiom.om.impl.llom.OMElementImpl.buildNext(OMElementImpl.java:653)
        at org.apache.axiom.om.impl.llom.OMNodeImpl.getNextOMSibling(OMNodeImpl.java:122)
        at org.apache.axiom.om.impl.traverse.OMChildrenIterator.getNextNode(OMChildrenIterator.java:36)
        at org.apache.axiom.om.impl.traverse.OMAbstractIterator.hasNext(OMAbstractIterator.java:58)
        at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeChildren(OMSerializerUtil.java:554)
        at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:875)
        at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeChildren(OMSerializerUtil.java:555)
        at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:875)
        at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeChildren(OMSerializerUtil.java:555)
        at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:875)
        at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeChildren(OMSerializerUtil.java:555)
        at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:875)
        at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:230)
        at org.apache.axiom.om.impl.llom.OMSerializableImpl.serialize(OMSerializableImpl.java:125)
        at org.apache.axiom.om.impl.llom.OMSerializableImpl.serialize(OMSerializableImpl.java:113)
        at org.apache.axiom.om.impl.llom.OMElementImpl.toString(OMElementImpl.java:988)
        at java.lang.String.valueOf(String.java:2994)
        at java.lang.StringBuffer.append(StringBuffer.java:265)
        at org.apache.synapse.mediators.builtin.LogMediator.getFullLogMessage(LogMediator.java:203)
        at org.apache.synapse.mediators.builtin.LogMediator.getLogMessage(LogMediator.java:138)
        at org.apache.synapse.mediators.builtin.LogMediator.mediate(LogMediator.java:101)
        at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:97)
        at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:59)
        at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158)
        at org.apache.synapse.rest.Resource.process(Resource.java:343)
        at org.apache.synapse.rest.API.process(API.java:399)
        at org.apache.synapse.rest.RESTRequestHandler.apiProcess(RESTRequestHandler.java:123)
        at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:101)
        at org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:69)
        at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:304)
        at org.apache.synapse.core.axis2.SynapseMessageReceiver.receive(SynapseMessageReceiver.java:78)
        at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
        at org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:326)
        at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:372)
        at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:151)
        at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character ' ' (code 32) (missing name?)
 at [row,col {unknown-source}]: [6,26]
        at com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:639)
        at com.ctc.wstx.sr.StreamScanner.parseFullName(StreamScanner.java:1924)
        at com.ctc.wstx.sr.StreamScanner.parseEntityName(StreamScanner.java:2050)
        at com.ctc.wstx.sr.StreamScanner.resolveNonCharEntity(StreamScanner.java:1479)
        at com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:2788)
        at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1072)
        at org.apache.axiom.util.stax.wrapper.XMLStreamReaderWrapper.next(XMLStreamReaderWrapper.java:225)
        at org.apache.axiom.util.stax.dialect.DisallowDoctypeDeclStreamReaderWrapper.next(DisallowDoctypeDeclStreamReaderWrapper.java:34)
        at org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
        at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
        ... 39 more
[2021-03-05 17:27:54,015] [] ERROR - WSO2API Could not build full log message: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character ' ' (code 32) (missing name?)
 at [row,col {unknown-source}]: [6,26]
org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character ' ' (code 32) (missing name?)
 at [row,col {unknown-source}]: [6,26]
        at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)
        at org.apache.axiom.om.impl.llom.OMElementImpl.buildNext(OMElementImpl.java:653)
        at org.apache.axiom.om.impl.llom.OMNodeImpl.getNextOMSibling(OMNodeImpl.java:122)
        at org.apache.axiom.om.impl.traverse.OMChildrenIterator.getNextNode(OMChildrenIterator.java:36)
        at org.apache.axiom.om.impl.traverse.OMAbstractIterator.hasNext(OMAbstractIterator.java:58)
        at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeChildren(OMSerializerUtil.java:554)
        at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:875)
        at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeChildren(OMSerializerUtil.java:555)
        at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:875)
        at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeChildren(OMSerializerUtil.java:555)
        at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:875)
        at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeChildren(OMSerializerUtil.java:555)
        at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:875)
        at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:230)
        at org.apache.axiom.om.impl.llom.OMSerializableImpl.serialize(OMSerializableImpl.java:125)
        at org.apache.axiom.om.impl.llom.OMSerializableImpl.serialize(OMSerializableImpl.java:113)
        at org.apache.axiom.om.impl.llom.OMElementImpl.toString(OMElementImpl.java:988)
        at java.lang.String.valueOf(String.java:2994)
        at java.lang.StringBuffer.append(StringBuffer.java:265)
        at org.apache.synapse.mediators.builtin.LogMediator.getFullLogMessage(LogMediator.java:203)
        at org.apache.synapse.mediators.builtin.LogMediator.getLogMessage(LogMediator.java:138)
        at org.apache.synapse.mediators.builtin.LogMediator.mediate(LogMediator.java:101)
        at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:97)
        at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:59)
        at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158)
        at org.apache.synapse.rest.Resource.process(Resource.java:343)
        at org.apache.synapse.rest.API.process(API.java:399)
        at org.apache.synapse.rest.RESTRequestHandler.apiProcess(RESTRequestHandler.java:123)
        at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:101)
        at org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:69)
        at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:304)
        at org.apache.synapse.core.axis2.SynapseMessageReceiver.receive(SynapseMessageReceiver.java:78)
        at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
        at org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:326)
        at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:372)
        at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:151)
        at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character ' ' (code 32) (missing name?)
 at [row,col {unknown-source}]: [6,26]
        at com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:639)
        at com.ctc.wstx.sr.StreamScanner.parseFullName(StreamScanner.java:1924)
        at com.ctc.wstx.sr.StreamScanner.parseEntityName(StreamScanner.java:2050)
        at com.ctc.wstx.sr.StreamScanner.resolveNonCharEntity(StreamScanner.java:1479)
        at com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:2788)
        at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1072)
        at org.apache.axiom.util.stax.wrapper.XMLStreamReaderWrapper.next(XMLStreamReaderWrapper.java:225)
        at org.apache.axiom.util.stax.dialect.DisallowDoctypeDeclStreamReaderWrapper.next(DisallowDoctypeDeclStreamReaderWrapper.java:34)
        at org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
        at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
        ... 39 more
[2021-03-05 17:27:54,036] []  INFO - LogMediator =====Faulty Response===== = Inside default Fault Sequence,**, =====message===== = Could not build full log message: com.ctc.wstx.exc
.WstxUnexpectedCharException: Unexpected character ' ' (code 32) (missing name?)
[2021-03-05 17:27:54,037] []  INFO - LogMediator ==Response== = {"StatusCode":"400","Message":"Failure"}

2 个解决方案

解决方案1
 0  2021-03-05 13:22:15

Salute, I had a similar problem.致敬，我也有类似的问题。 perhaps replacing the symbols '**' with Unicode one will help you: You can find codes you need for example [1]: https://unicode-table.com/也许用 Unicode 替换符号 '**' 会对您有所帮助：您可以找到所需的代码，例如 [1]： https://unicode-table.com/

解决方案2
 0  2021-03-06 10:09:06

With the above API configurations and with the invalid request payload, this issue can be easily reproducible with WSO2 EI 6.1.1.使用上述 API 配置和无效的请求负载，可以使用 WSO2 EI 6.1.1 轻松重现此问题。

[2021-03-05 17:27:54,004] [] ERROR - LogMediator Could not build full log message: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character ' ' (code 32) (missing name?) 
    at [row,col {unknown-source}]: [6,26]
org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character ' ' (code 32) (missing name?)
    at [row,col {unknown-source}]: [6,26]

The above error has been thrown when WSO2 EI is trying to build the message payload inside a full log mediator.当 WSO2 EI 尝试在完整日志中介内构建消息有效负载时，会引发上述错误。 The issue is happening because of the '&' character in your invalid request payload.由于无效请求有效负载中的“&”字符，问题正在发生。 This is a special character and WSO2 EI cannot handle special characters like these and hence it will throw an exception.这是一个特殊字符，WSO2 EI 不能处理这些特殊字符，因此会抛出异常。

If you really want to use the '&' character in your request payload you need to use escape characters (&amp;) to avoid breaking the flow.如果您真的想在请求负载中使用“&”字符，则需要使用转义字符 (&amp;) 以避免中断流程。

暂无
暂无

声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 WSO2 EI分析 - WSO2 EI analytics WSO2 EI JSONBuilder 配置 - WSO2 EI JSONBuilder configuration WSO2 ESB：未解析WSO2 REST API调用中的XML响应 - WSO2 ESB: XML response in WSO2 REST API call not parsed wso2 esb 5.0中的DOCTYPE Xml请求 - DOCTYPE Xml Request in wso2 esb 5.0 在 WSO2 APIM 3.2.0 中修改/删除 wso2 类中介或 xml 序列中的请求有效负载内容 - Modify/Remove request payload content in wso2 class mediator or xml sequence in WSO2 APIM 3.2.0 在Wso2中将XML转换为JSON - Transforming XML to JSON in Wso2 wso2中xml到json的转换 - xml to json conversion in wso2 从 WSO2 EI 中具有 2 个命名空间的 XML 转换 JSON 消息 - Transform JSON message from XML which has 2 namespaces in WSO2 EI 在WSO2中，ESB在进入api之前验证XML - In WSO2 ESB is validate XML before coming to the api JSON至SOAP WSO2 Api管理器xml序列 - JSON to SOAP WSO2 Api manager xml sequence
相关标签
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM