Issue Details (XML | Word | Printable)

Key: MULE-3770
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Blocker Blocker
Assignee: Dan Diephouse
Reporter: Ross Mason
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Mule

File Transport seems to be reading the same file Multiple times. See the FileToTcpStreamingTestCase

Created: 06/Oct/08 03:08 AM   Updated: 10/Oct/08 11:41 AM
Component/s: Transport: File
Affects Version/s: 2.0.2
Fix Version/s: 2.1.1

Time Tracking:
Not Specified

Issue Links:
Related
 

Labels:
User impact: High


 Description  « Hide
This looks like a serious issue and a regression from previous behaviour. I think it only happens when streaming is set to true, but that is the default for the FileConnector

 All   Comments   Work Log   Change History   Transitions   FishEye      Sort Order: Ascending order - Click to sort in descending order
Ross Mason added a comment - 06/Oct/08 06:29 AM
See new test coverage added: http://fisheye.codehaus.org/changelog/mule/?cs=12909
could not reproduce the issue

Daniel Feist added a comment - 09/Oct/08 09:37 PM
This still occurs. It happens in the following case:
  • File -> tcp bridging
  • You rely on input file being moved/delete so as not to be picked up again.

I believe this happens because TcpMessageDispatcher/StreamingProtocol do not close the FileInputStream ever and so the move/delete operations that are done in ReceiverFileInputStream never happen.


Dan Diephouse added a comment - 10/Oct/08 11:41 AM
Fixed in : http://fisheye.codehaus.org/changelog/mule/?cs=13043

The Tcp stream wasn't being closed, so the file resources weren't being released/deleted.