Re: [Dev] WSO2 Oxygen Tank > Manage endpoint text responses from proxy (Unexpected character 'some_character' code 45 in prolog expected '<')

Hello Finally I found this solution that applies to the general operation ESB You have to add in axis2.xml file at least With more time I will perform more checks Marcos ___ Dev mailing list Dev@wso2.org

Re: [Dev] WSO2 Oxygen Tank > Manage endpoint text responses from proxy (Unexpected character 'some_character' code 45 in prolog expected '<')

Apologies for the insistence ... Would this solution be enough? http://ws.apache.org/ns/synapse; name="%%_Based_Proxy" startOnLoad="true" statistics="disable" trace="enable" transports="http,https">

Re: [Dev] WSO2 Oxygen Tank > Manage endpoint text responses from proxy (Unexpected character 'some_character' code 45 in prolog expected '<')

For facilitating a simple solution. I suggest only to send to client the SOAP part of response: http://schemas.xmlsoap.org/soap/envelope/; xmlns: ns1 = "https://.es//ws/ws_/1.0/infoEnvi;> xa3x2x8xx7 And remove file’s information: --urn: uuid:

Re: [Dev] WSO2 Oxygen Tank > Manage endpoint text responses from proxy (Unexpected character 'some_character' code 45 in prolog expected '<')

Hi Nadeeshaan Regarding the need to create a custom message formatter / builder. I do not have enough knowledge to implement it. And I would like to make a solution as simple as possible. As a solution I propose the following (if you could help me). Just take the complete response received from

Re: [Dev] WSO2 Oxygen Tank > Manage endpoint text responses from proxy (Unexpected character 'some_character' code 45 in prolog expected '<')

Hi Nadeeshaan Very grateful for your help The error I reported was obtained from the log file. It is the only one found. TID: [-1234] [] [2017-12-21 17:15:38,305] ERROR {org.apache.synapse.transport.passthru.util.RelayUtils} - Error while building Passthrough stream

Re: [Dev] WSO2 Oxygen Tank > Manage endpoint text responses from proxy (Unexpected character 'some_character' code 45 in prolog expected '<')

Hello Nadeeshaan I have this simple proxy: http://ws.apache.org/ns/synapse; name="WsV2_Based_Proxy" startOnLoad="true" statistics="disable" trace="enable" transports="http,https">

[Dev] WSO2 Oxygen Tank > Manage endpoint text responses from proxy (Unexpected character 'some_character' code 45 in prolog expected '<')

Hi ... I'm making a soap call to an endpoint service through ESB6.1.1 from SOAPUI PROXY CONFIGURATION ((( I bloted out some information with ))) http://ws.apache.org/ns/synapse; name="WsV2_Based_Proxy" startOnLoad="true" statistics="disable" trace="enable" transports="http,https">

[Dev] WSO2 Oxygen Tank > Message Forwarding Processor > Use of propeties tag inside a Scheduled Message Forwarding Processor

Hello How can i add tags (or similar functionality) to a Scheduled Message Forwarding Processor? I explain the case: I'm sending a message from a proxy service to an endpoint adding last mentioned properties without problem. In case of endpoint is fallen, I save the message in

[Dev] WSO2 Oxygen Tank > WSO2 Development> ESB > Parameter for sending messages to a sequence when is_Enabled

Hello I would like to save messages before they are dropped by the Scheduled Message Forwarding Processor when it’s configured to be always active. With this configuration it drops messages in processor’s queue then max delivery attemtps is reached (It works like this when is_Enabled) My

Re: [Dev] WSO2 Oxygen Tank > WSO2 Development> ESB > Message Processor > Continuous operation Message Processor

Sorry I wanted to warn that I just found a bug in the max.delivery.attempts parameter. I can’t change its value: http://wso2-oxygen-tank.10903.n7.nabble.com/WSO2-Oxygen-Tank-gt-WSO2-Development-gt-ESB-gt-Message-Processor-gt-max-delivery-attempts-bug-

Re: [Dev] WSO2 Oxygen Tank > WSO2 Development> ESB > Message Processor > Continuous operation Message Processor

Hi I think that using Cron Expression parameter I would keep Message Processor always active. Do you know any cron expression for my purpose? Best regards ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Oxygen Tank > WSO2 Development> ESB > Message Processor > Continuous operation Message Processor

Hello When the backend is down, I would like to keep the Message Processor active always without having to drop any pending message and without having the necessity of reactivate the Message Processor manually. I don't care how to achieve this configuration ¿Can you send an example? Thanks in

[Dev] WSO2 Oxygen Tank > WSO2 Development> ESB > Message Processor > max.delivery.attempts bug

Hello When I change the value of max.delivery.attempts parameter in the message processor and save changes. It always return to its default value of 4. Ubuntu 16.04 - mysql 5 - wso2 6.1.1 configuration Thanks Marcos Marcos ___ Dev mailing list