| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| File Input - Read only issue using FTP |
« View previous topic :: View next topic » |
| Author |
Message
|
| AKARTHIK |
 Posted: Tue Feb 05, 2008 4:24 am Post subject: File Input - Read only issue using FTP |
 |
|
Newbie
Joined: 29 Jan 2008
Posts: 3
|
Hi
The FileInput node is configured with FTP option for polling a file from a remote desktop.
I find that the File is moved from remote desktop to local path specified in the Input directory of FileInput node. Then the FileInput polls the file from local path.
The FileInput node behaves in a such a way that it will not process a readonly File in the local path.
But when I put a Read Only file in the remote desktop, after FTP the property Read only is removed from the file in the local path and the file remains there in the remote desktop as well.
So this process runs infinitely affecting the performance of my Broker.
Since I dont have control on the file in remote desktop, if someone puts a readonly file by mistake, I should not process the file or while FTP I should preserve the Readonly property of the file in the local path.
Is there anyway to achieve this using FileInput?
Is there any other solution for this?
Regards
arunkarthik b |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Feb 05, 2008 4:43 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Open a PMR.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mqpaul |
| Posted: Wed Feb 06, 2008 4:12 am Post subject: FTP has a problem with undeletable files |
|
|
Acolyte
Joined: 14 Jan 2008
Posts: 66
Location: Hursley, UK
|
Unfortunately, the FTP RFC 959 provides no way to determine if a remote file can be deleted short of trying to delete it. (Read-only may or may not allow deletion, depending on the operating system. For example, you need write access to the containing directory to delete a file on a Linux server).
The FTP LIST command returns the server's directory list, but its result varies according to the FTP server; there's no standard. The proposed extensions in RF 3659 would provide more information in a standard form. However, the File nodes can neither assume the FTP server supports RFC3659, nor that LIST provides any specific format response.
Net of this is that the FileInput node might fail the flow if it was unable to delete the file on the FTP server. However, as the file would remain there, it would try to transfer it every time it polled the FTP directory, so you would get failing flows until either the file was made deletable, or it was removed from the directory.
_________________
Paul |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Feb 06, 2008 4:59 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
While it may not be possible to delete a remote file, it may be possible to a) rename it, b) cache the fact that you've already processed it.
Otherwise, yes, this is a much harder problem than it looks like.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
