Hi ESB team, I observed the $subject while examining another issue in VFS transport.
I have done timeout handling on SMB file system with VFS file endpoint following [1] My SMB authentication has intermittent issue not authorizing file creation for random calls. When it hits "acquireLock", the endpoint goes to VFS default timeout, not my synapse timeout(which is no timeout). [2016-08-15 12:01:23,469] WARN - VFSTransportSender Couldn't get the lock for the file : smb://xx":***@"yyy/zzz/file-out/Resp-1066.txt, retry : 1 scheduled after : 30000 I do not think this is expected behaviour. Close examination point to [2], which I think needs to be corrected. I do not think we need the "wait till we get the lock" segment. I suggest to let it fail fast when it can not acquire the lock. WDYT? [1] http://miyurudw.blogspot.com/2012/02/disable-suspension-of-wso2-esb-synapse.html [2] https://github.com/wso2/wso2-synapse/blob/3a6b25a195bbeb95c638730d7678d7a7a8ffb831/modules/transports/core/vfs/src/main/java/org/apache/synapse/transport/vfs/VFSTransportSender.java#L429 Cheers, Ruwan
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
