[
https://jira.jboss.org/jira/browse/JBESB-1995?page=com.atlassian.jira.plu...
]
Mark Little commented on JBESB-1995:
------------------------------------
Which FTP server are you using? There are known issues with some FTP servers (e.g., MSFT)
that create the file and don't release it immediately, thus preventing us to rename
it. The effect would be that we are conflicting with ourselves and not some other process
having grabbed the file in between the write and the rename attempt.
FTP notification - Failed to rename file: 550
---------------------------------------------
Key: JBESB-1995
URL:
https://jira.jboss.org/jira/browse/JBESB-1995
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.4
Environment: JBoss 4.2.3.GA, JBossESB-4.4.GA
Reporter: Willem Labuschagne
When using the file notification, and using the option to specify own filename, I get a
the follow error. It seems that the other side has already moved the file when the rename
tries to happen. The filename must not tried be renamed but saved with the correct
filename.
12:00:28,734 ERROR [NotificationList] Can't instantiate target <target
class="NotifyFTP">
<ftp URL="ftp://formscape:1234**@10.5.102.127/0580"
filename="{itc-_MessageID}.xml"/>
</target>
org.jboss.soa.esb.notification.NotificationException: Could not complete FTP
notification
at org.jboss.soa.esb.notification.NotifyFTP.sendNotification(NotifyFTP.java:162)
at org.jboss.soa.esb.notification.NotificationList.notifyAll(NotificationList.java:164)
at org.jboss.soa.esb.actions.Notifier.notifyOK(Notifier.java:93)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processSuccess(ActionProcessorMethodInfo.java:165)
at
org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.processSuccess(OverriddenActionLifecycleProcessor.java:108)
at
org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.notifySuccess(ActionProcessingPipeline.java:610)
at
org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:384)
at
org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.jboss.soa.esb.util.RemoteFileSystemException: Failed to rename file: 550
e93864db-cea6-4ab5-bb16-3ab96ba4e9e9.xml: The process cannot access the file because it is
being used by another process.
at org.jboss.internal.soa.esb.util.FtpImpl.uploadFile(FtpImpl.java:591)
at org.jboss.soa.esb.notification.NotifyFTP.sendNotification(NotifyFTP.java:160)
... 14 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira