I think we must keep the streaming behavior of VFS transport. I have seen use cases where people use VFS transport to manage legacy content delivery/routing which involves large file transfers.
Do you see any down side of forcing to remove ClientAPINonBlockingProperty at the transport level in the VFS transport. I think its acceptable for most of the use cases. regards, Charith On Thu, Jul 18, 2013 at 4:07 PM, Hiranya Jayathilaka <[email protected]>wrote: > Hi Folks, > > I'm in the process of fixing SYNAPSE-851. There is a problem in the VFS > transport if you try to mediate a non-XML message through Synapse without > touching its payload (i.e. pass through). When Synapse tries to send the > message out, Axis2 will spawn a new thread to handle the send operation. At > this point, the VFS listener thread that received the message gets released > and it closes the file input stream. Since the message hasn't been built > yet, Synapse will end up writing an empty message to the output stream. > > There are 2 workarounds to the problem: > 1. Force Synapse to build the message in the in-sequence by engaging some > mediator (e.g. log mediator). > 2. Remove the ClientAPINonBlocking property (successor to the old > transportNonBlocking property) from the message which forces Axis2 to send > the message out on the same VFS listener thread. > > My question is, should we try to do better here? This problem must have > always been there, but usually we do some processing on the incoming > message (e.g. XSLT), which circumvents the issue. So we can treat pass > through scenario as a special case and make it a requirement to remove the > ClientAPINonBlockingProperty. Or we can make it the default behavior of the > VFS transport listener. We can even try to build all VFS requests before > they are sent out to any endpoint. > > WDYT? > > Thanks, > Hiranya > -- > Hiranya Jayathilaka > Mayhem Lab/RACE Lab; > Dept. of Computer Science, UCSB; http://cs.ucsb.edu > E-mail: [email protected] <[email protected]>; Mobile: +1 (805) 895-7443 > Blog: > http://techfeast-hiranya.**blogspot.com<http://techfeast-hiranya.blogspot.com/> > > -- Charith Dhanushka Wickramaarachchi Tel +1 213 447 4253 Web http://apache.org/~charith <http://www-scf.usc.edu/~cwickram/><http://charith.wickramaarachchi.org/> Blog http://charith.wickramaarachchi.org/<http://charithwiki.blogspot.com/> Twitter @charithwiki <https://twitter.com/charithwiki>
