Sample 254 fails with "Could not rename ..."
--------------------------------------------
Key: SYNAPSE-542
URL: https://issues.apache.org/jira/browse/SYNAPSE-542
Project: Synapse
Issue Type: Bug
Components: Transports
Reporter: Andreas Veithen
Priority: Critical
Fix For: 1.3
Executing sample 254 fails with the following error:
Could not rename "file:///Users/veithen/test/in/test.xml" to
"file:///Users/veithen/test/original/test.xml".
The reason for the failure can be seen in the logs:
2009-05-09 01:18:21,626 [-] [vfs-Worker-1] DEBUG VFSTransportListener Scanning
directory or file : file:///Users/veithen/test/in
2009-05-09 01:18:21,645 [-] [vfs-Worker-1] DEBUG VFSTransportListener File name
pattern :.*\.xml
2009-05-09 01:18:21,645 [-] [vfs-Worker-1] DEBUG VFSTransportListener Matching
file :test.xml
2009-05-09 01:18:21,646 [-] [vfs-Worker-1] DEBUG VFSTransportListener
Processing file :file:///Users/veithen/test/in/test.xml
2009-05-09 01:18:21,674 [-] [vfs-Worker-2] DEBUG VFSTransportListener Scanning
directory or file : file:///Users/veithen/test/in
2009-05-09 01:18:21,674 [-] [vfs-Worker-2] DEBUG VFSTransportListener File name
pattern :.*\.xml
2009-05-09 01:18:21,674 [-] [vfs-Worker-2] DEBUG VFSTransportListener Matching
file :test.xml
2009-05-09 01:18:21,674 [-] [vfs-Worker-2] DEBUG VFSTransportListener
Processing file :file:///Users/veithen/test/in/test.xml
The VFS transport schedules two polls on the same directory!
The root cause for this issue is WSCOMMONS-466. It only shows up now because of
the recent changes in startup order.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
