wso2 - Using VFS to Write a File -

i've started working wso2 , encountering problem using vfs write file.

<?xml version="1.0" encoding="utf-8"?><proxy xmlns="http://ws.apache.org/ns/synapse" name="px_writetofile" transports="https,http,vfs" statistics="disable" trace="disable" startonload="true">     <target>         <insequence>             <loopback/>         </insequence>         <outsequence>             <payloadfactory media-type="xml">                 <format>                     <fungus xmlns="">                         <info>$1 fungus $2 cap. has $3 stem $4 gills. may dangerous having $5</info>                     </fungus>                 </format>                 <args>                     <arg evaluator="xml" expression="//name"/>                     <arg evaluator="xml" expression="//cap"/>                     <arg evaluator="xml" expression="//stem"/>                     <arg evaluator="xml" expression="//gill"/>                     <arg evaluator="xml" expression="//toxin"/>                 </args>             </payloadfactory>             <property name="transport.vfs.replyfilename" value="reply.txt" scope="transport" type="string"/>             <property name="out_only" value="true" scope="default" type="boolean"/>             <send>                 <endpoint>                     <address uri="vfs:file://c:/vfs/reply"/>                 </endpoint>             </send>         </outsequence>     </target>     <parameter name="transport.vfs.actionafterprocess">move</parameter>     <parameter name="transport.pollinterval">5</parameter>     <parameter name="transport.vfs.moveafterprocess">file://c:/vfs/map</parameter>     <parameter name="transport.vfs.fileuri">file://c:/vfs/reply</parameter>     <parameter name="transport.vfs.moveafterfailure">file://c:/vfs/maf</parameter>     <parameter name="transport.vfs.contenttype">text/xml</parameter>     <parameter name="transport.vfs.actionafterfailure">move</parameter>     <description/> </proxy> 

when executing proxy service get

[2015-06-03 16:57:24,377]  warn {service_logger.px_writetofile} -  executing fault handler due exception encountered [2015-06-03 16:57:24,378]  warn {service_logger.px_writetofile} -  error_code : 0 error_message : unexpected error during sending message ou t [2015-06-03 16:57:24,379]  info {service_logger.px_writetofile} -  faulthandler executing impl: org.apache.synapse.mediators.mediatorfaultha ndler [2015-06-03 16:57:24,380]  warn {service_logger.px_writetofile} -  executing fault sequence mediator : fault [2015-06-03 16:57:24,380]  info {service_logger.px_writetofile} -  to: , from: 136.227.134.115, wsaction: urn:mediate, soapaction: urn:media te, replyto: http://www.w3.org/2005/08/addressing/anonymous, messageid: http://identifiers.wso2.com/messageid/1433365044366/4616446479, dire ction: response, message = executing default 'fault' sequence, error_code = 0, error_message = unexpected error during sending message out, envelope: <?xml version="1.0" encoding="utf-8"?><s:envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://www.w3.org/2 005/08/addressing"><s:header>    </s:header><s:body><fungus><info>silvercap fungus blue, white , pearlescent cap. has no stem smooth gills. may d angerous having mercury comparable tuna/lb</info></fungus></s:body></s:envelope> 

vfs enabled (both receiver , sender) , have tried using

writing on text file using vfs in wso2 esb 4.8.1

as reference without luck.

is there have overlooked?

thank you,

additional logging tracing enabled. [2015-06-04 08:09:39,784]  info {trace_logger} -  end : property mediator [2015-06-04 08:09:39,784]  info {trace_logger} -  start : send mediator [2015-06-04 08:09:39,785]  info {trace_logger} -  sending message through endpoint : null resolving address = vfs:file:.=///c:/vfs/reply [2015-06-04 08:09:39,785]  info {trace_logger} -  soapaction: urn:mediate [2015-06-04 08:09:39,785]  info {trace_logger} -  wsa-action: urn:mediate [2015-06-04 08:09:39,811]  warn {trace_logger} -  executing fault handler due exception encountered [2015-06-04 08:09:39,811]  warn {service_logger.px_writetofile} -  executing fault handler due exception encountered [2015-06-04 08:09:39,811]  warn {trace_logger} -  error_code : 0 [2015-06-04 08:09:39,811]  warn {trace_logger} -  error_message : unexpected error during sending message out [2015-06-04 08:09:39,811]  warn {trace_logger} -  error_detail : org.apache.synapse.synapseexception: unexpected error during sending message out     @ org.apache.synapse.core.axis2.axis2sender.handleexception(axis2sender.java:172)     @ org.apache.synapse.core.axis2.axis2sender.sendon(axis2sender.java:71)     @ org.apache.synapse.core.axis2.axis2synapseenvironment.send(axis2synapseenvironment.java:309)     @ org.apache.synapse.endpoints.abstractendpoint.send(abstractendpoint.java:333)     @ org.apache.synapse.endpoints.addressendpoint.send(addressendpoint.java:59)     @ org.apache.synapse.mediators.builtin.sendmediator.mediate(sendmediator.java:97)     @ org.apache.synapse.mediators.abstractlistmediator.mediate(abstractlistmediator.java:77)     @ org.apache.synapse.mediators.abstractlistmediator.mediate(abstractlistmediator.java:47)     @ org.apache.synapse.mediators.base.sequencemediator.mediate(sequencemediator.java:131)     @ org.apache.synapse.core.axis2.axis2synapseenvironment.injectmessage(axis2synapseenvironment.java:268)     @ org.apache.synapse.mediators.builtin.loopbackmediator.mediate(loopbackmediator.java:42)     @ org.apache.synapse.mediators.abstractlistmediator.mediate(abstractlistmediator.java:77)     @ org.apache.synapse.mediators.abstractlistmediator.mediate(abstractlistmediator.java:47)     @ org.apache.synapse.mediators.base.sequencemediator.mediate(sequencemediator.java:131)     @ org.apache.synapse.core.axis2.proxyservicemessagereceiver.receive(proxyservicemessagereceiver.java:166)     @ org.apache.axis2.engine.axisengine.receive(axisengine.java:180)     @ org.apache.axis2.transport.http.httptransportutils.processhttppostrequest(httptransportutils.java:172)     @ org.apache.axis2.transport.http.axisservlet.dopost(axisservlet.java:146)     @ org.wso2.carbon.core.transports.carbonservlet.dopost(carbonservlet.java:231)     @ javax.servlet.http.httpservlet.service(httpservlet.java:755)     @ javax.servlet.http.httpservlet.service(httpservlet.java:848)     @ org.eclipse.equinox.http.servlet.internal.servletregistration.service(servletregistration.java:61)     @ org.eclipse.equinox.http.servlet.internal.proxyservlet.processalias(proxyservlet.java:128)     @ org.eclipse.equinox.http.servlet.internal.proxyservlet.service(proxyservlet.java:68)     @ javax.servlet.http.httpservlet.service(httpservlet.java:848)     @ org.wso2.carbon.tomcat.ext.servlet.delegationservlet.service(delegationservlet.java:68)     @ org.apache.catalina.core.applicationfilterchain.internaldofilter(applicationfilterchain.java:305)     @ org.apache.catalina.core.applicationfilterchain.dofilter(applicationfilterchain.java:210)     @ org.wso2.carbon.tomcat.ext.filter.charactersetfilter.dofilter(charactersetfilter.java:61)     @ org.apache.catalina.core.applicationfilterchain.internaldofilter(applicationfilterchain.java:243)     @ org.apache.catalina.core.applicationfilterchain.dofilter(applicationfilterchain.java:210)     @ org.apache.catalina.core.standardwrappervalve.invoke(standardwrappervalve.java:222)     @ org.apache.catalina.core.standardcontextvalve.invoke(standardcontextvalve.java:123)     @ org.apache.catalina.authenticator.authenticatorbase.invoke(authenticatorbase.java:472)     @ org.apache.catalina.core.standardhostvalve.invoke(standardhostvalve.java:171)     @ org.apache.catalina.valves.errorreportvalve.invoke(errorreportvalve.java:99)     @ org.wso2.carbon.tomcat.ext.valves.compositevalve.continueinvocation(compositevalve.java:178)     @ org.wso2.carbon.tomcat.ext.valves.tomcatvalvecontainer.invokevalves(tomcatvalvecontainer.java:49)     @ org.wso2.carbon.tomcat.ext.valves.compositevalve.invoke(compositevalve.java:141)     @ org.wso2.carbon.tomcat.ext.valves.carbonstuckthreaddetectionvalve.invoke(carbonstuckthreaddetectionvalve.java:156)     @ org.apache.catalina.valves.accesslogvalve.invoke(accesslogvalve.java:936)     @ org.wso2.carbon.tomcat.ext.valves.carboncontextcreatorvalve.invoke(carboncontextcreatorvalve.java:52)     @ org.apache.catalina.core.standardenginevalve.invoke(standardenginevalve.java:118)     @ org.apache.catalina.connector.coyoteadapter.service(coyoteadapter.java:407)     @ org.apache.coyote.http11.abstracthttp11processor.process(abstracthttp11processor.java:1004)     @ org.apache.coyote.abstractprotocol$abstractconnectionhandler.process(abstractprotocol.java:589)     @ org.apache.tomcat.util.net.nioendpoint$socketprocessor.run(nioendpoint.java:1653)     @ java.util.concurrent.threadpoolexecutor.runworker(threadpoolexecutor.java:1145)     @ java.util.concurrent.threadpoolexecutor$worker.run(threadpoolexecutor.java:615)     @ java.lang.thread.run(thread.java:745) caused by: org.apache.axis2.axisfault: vfs transport doesn't support synchronous responses. please use appropriate (out only) message exchange pattern.     @ org.apache.synapse.transport.vfs.vfstransportsender.sendmessage(vfstransportsender.java:110)     @ org.apache.axis2.transport.base.abstracttransportsender.invoke(abstracttransportsender.java:112)     @ org.apache.axis2.engine.axisengine.send(axisengine.java:442)     @ org.apache.synapse.core.axis2.dynamicaxisoperation$dynamicoperationclient.send(dynamicaxisoperation.java:185)     @ org.apache.synapse.core.axis2.dynamicaxisoperation$dynamicoperationclient.executeimpl(dynamicaxisoperation.java:167)     @ org.apache.axis2.client.operationclient.execute(operationclient.java:149)     @ org.apache.synapse.core.axis2.axis2flexiblemepclient.send(axis2flexiblemepclient.java:482)     @ org.apache.synapse.core.axis2.axis2sender.sendon(axis2sender.java:59)     ... 48 more  [2015-06-04 08:09:39,811]  warn {trace_logger} -  error_exception : org.apache.synapse.synapseexception: unexpected error during sending message out [2015-06-04 08:09:39,811]  warn {service_logger.px_writetofile} -  error_code : 0 error_message : unexpected error during sending message out 

in endpoint address, vfs:file:// protocol , rest directory must start /

the directory c:\vfs\reply must exist

<send>   <endpoint>     <address uri="vfs:file:///c:/vfs/reply"/>   </endpoint> </send>