[SYNAPSE-542] Sample 254 fails with "Could not rename ..."

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 2.0
• Component/s: Transports
• Assignee: Unassigned
• Reporter: Andreas Veithen
• Created: 08/May/09 23:51
• Updated: 10/May/09 12:09
• Resolved: 10/May/09 12:09

Description

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.

Issue Links

• is blocked by: WSCOMMONS-466 AbstractTransportListener.GenericObserver may start listening for services when the transport is stopped