This was indeed the problems... Thanks for the tip !

-----Original Message-----
From: Hiranya Jayathilaka [mailto:[email protected]] 
Sent: donderdag 28 juli 2011 10:06
To: [email protected]
Subject: Re: Proxy service call fails although mediators are executed
successfully

This is because the proxy service does not send a response back to the
client. Client expects a HTTP 202 response. You should either configure
your
proxy to send a response back to client. Or you can try setting the
following property in the in-sequence:

<property name="FORCE_SC_ACCEPTED" value="true" scope="axis2"/>

Thanks,
Hiranya

On Thu, Jul 28, 2011 at 1:00 PM, De Vleeschauwer Nele <
[email protected]> wrote:

> Hi,
>
> On my Apache Synapse installation, I've configured a proxy services
> which does nothing more than writing a log message, storing the
message
> in a message store and delivering it to a fileshare endpoint.
> My proxy service looks like this:
> <?xml version="1.0" encoding="UTF-8"?>
> <proxy xmlns="http://ws.apache.org/ns/synapse"; name="testSequence"
> transports="http" startOnLoad="true" trace="disable">
>    <target endpoint="fileshareEndpointNDV">
>        <inSequence>
>            <sequence
> key="conf:/repository/synapse/default/sequences/store"/>
>            <property name="OUT_ONLY" value="true" scope="default"/>
>        </inSequence>
>    </target>
> </proxy>
>
> and the sequence:
> <?xml version="1.0" encoding="UTF-8"?>
> <sequence xmlns="http://ws.apache.org/ns/synapse"; name="store"
> trace="enable" statistics="enable">
>    <in>
>        <log level="full"/>
>        <store messageStore="MemoryMessageStore"/>
>    </in>
>    <description/>
> </sequence>
>
> and the endpoint:
> <?xml version="1.0" encoding="UTF-8"?>
> <endpoint xmlns="http://ws.apache.org/ns/synapse";
> name="fileshareEndpointNDV">
>    <address statistics="disable" trace="disable"
> uri="vfs:file:///D:/DATA/filedropping">
>        <timeout>
>            <duration>0</duration>
>            <action>discard</action>
>        </timeout>
>        <markForSuspension>
>            <retriesBeforeSuspension>0</retriesBeforeSuspension>
>            <retryDelay>0</retryDelay>
>        </markForSuspension>
>        <suspendOnFailure>
>            <initialDuration>0</initialDuration>
>            <maximumDuration>0</maximumDuration>
>            <progressionFactor>1.0</progressionFactor>
>        </suspendOnFailure>
>    </address>
> </endpoint>
>
> Each time when we call our proxy service e.g. via a soap ui client,
the
> client executes the request, the message is correctly logged, stored
and
> written to disk, but our client always gets an exception back:
> Thu Jul 28 09:23:41 CEST 2011:INFO:Error getting response for [HTTP
Test
> Request]; java.net.SocketTimeoutException: Read timed out
>
> What do we need to do to avoid this ?
>
>
>
>
> -----------------------------------------
> Visit our website! http://www.nbb.be
>
> "DISCLAIMER: The content of this e-mail message should not be
> construed as binding on the part of the National Bank of Belgium
> (NBB) unless otherwise and previously stated. The opinions
> expressed in this message are solely those of the author and do not
> necessarily reflect NBB viewpoints, particularly when the content
> of this message, or part thereof, is private by nature or does not
> fall within the professional scope of its author."




-- 
Hiranya Jayathilaka
Associate Technical Lead;
WSO2 Inc.;  http://wso2.org
E-mail: [email protected];  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com

Reply via email to