synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiranya Jayathilaka (JIRA)" <>
Subject [jira] [Commented] (SYNAPSE-851) VFS proxy generates the response.xml with empty content (Synapse-2.2.0-Snapshot trunk)
Date Thu, 18 Jul 2013 19:04:50 GMT


Hiranya Jayathilaka commented on SYNAPSE-851:

I think Ratha has uncovered a serious bug here. This is what happens:

1. VFS listener receives a plain text message. The plain text builder creates an OMSourcedElement
to represent the message payload.
2. When the ESB hits send, a new thread is spawned to handle the send operation. At this point
the VFS listener thread returns and it closes the input stream to the input file.
3. Now when the VFS sender attempts to format the message, the OMSourcedElement no longer
have access to the original file input stream. So an empty payload is written out.
> VFS proxy generates the response.xml with empty content (Synapse-2.2.0-Snapshot trunk)
> --------------------------------------------------------------------------------------
>                 Key: SYNAPSE-851
>                 URL:
>             Project: Synapse
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: NIGHTLY
>            Reporter: Vijayaratha Vijayasingam
>            Assignee: Hiranya Jayathilaka
>            Priority: Blocker
>             Fix For: FUTURE
> Used following configuration;
> I see the output(response.xml) at "out" folder is empty..
> <proxy name="StockQuoteProxy" transports="vfs" startOnLoad="true" trace="disable">
>         <target faultSequence="fault">
>             <inSequence>
>                 <property name="OUT_ONLY" value="true"/>
>                 <send>
>                     <endpoint>
>                         <address uri="vfs:file:C:\Users\TOSHIBA\Desktop\out"/>
>                     </endpoint>
>                 </send>
>             </inSequence>
>         </target>
>         <parameter name="transport.PollInterval">15</parameter>
>         <parameter name="transport.vfs.ActionAfterProcess">MOVE</parameter>
>         <!--<parameter name="transport.vfs.FileURI">vfs:ftp://anonymous@localhost/in?vfs.passive=true</parameter>-->
> 		<parameter name="transport.vfs.FileURI">file:C:\Users\TOSHIBA\Desktop\in</parameter>
>         <parameter name="transport.vfs.MoveAfterProcess">file:C:\Users\TOSHIBA\Desktop\original</parameter>
>         <parameter name="transport.vfs.MoveAfterFailure">file:C:\Users\TOSHIBA\Desktop\error</parameter>
>         <parameter name="transport.vfs.FileNamePattern">.*</parameter>
>         <parameter name="transport.vfs.ContentType">text/plain</parameter>
>         <parameter name="transport.vfs.ActionAfterFailure">MOVE</parameter>
>         <parameter name="serviceType">proxy</parameter>
>     </proxy>

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message