[ http://jira.jboss.com/jira/browse/JBESB-1609?page=comments#action_12403512 ] Mark Little commented on JBESB-1609: ------------------------------------ Can you try a different FTP server, or check your configuration? I've tried PureFTPd on Mac OS X and the examples work in passive and active modes. I'm double checking I got my configuration right though. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1609?page=comments#action_12403524 ] Len DiMaggio commented on JBESB-1609: ------------------------------------- At first glance - this syntax seems to work: /usr/local/sbin/pure-ftpd -p30000:50000 I'd like to make sure that this is really running in passive mode though. Will look at it with Wireshark on Wednesday. What config did you use for PureFTPd? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1609?page=comments#action_12403543 ] Kevin Conner commented on JBESB-1609: ------------------------------------- The FTP gateway should work in passive mode but I don't believe the notifier does. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1609?page=all ] Len DiMaggio closed JBESB-1609. ------------------------------- Resolution: Rejected I've been looking at the FTP action/notifier tests with passive-only FTP and have some updates. 1) I'm closing SOA-467 and JBESB-1609 as rejected. The test configuration was incorrect. The problem listed in the JIRAs only occurs when the FTP server is running on local host. 2) The helloworld_ftp_action Quickstart runs cleanly with either vsftpd or PureFTPd - with the FTP daemon running on a remote server. I'm taking the firewall out of the equation by turning it off on both the client and server. 3) The notifications Quickstart's FTP notifier runs cleanly with PureFTPd configured with Passive mode (/usr/local/sbin/pure-ftpd -A -c50 -B -C8 -D -fftp -H -I15 -L2000:8 -m4 -p30000:50000 -s -U133:022 -u100 -k99 -Z). With vsftpd set to Passive mode (port_enable=NO), I'm seeing the exception listed below. This looks logical for a passive mode failure (FTPControlSocket, etc.). So - I'm currently looking at verifying that passive mode is actually being used by vsftpd or PureFTPd - based on their configurations. I'll log a new JIRA for passive mode + FTP notifiers when I can verify this. Notifier test vsftpd # Set passive only mode port_enable=NO 11:14:31,007 INFO [STDOUT] ConsoleNotifier 2008/03/19 11:14:31.007<Hello from ESB-unaware JMS Client> 11:20:41,007 WARN [ActionProcessingPipeline] No reply to address defined for reply message! To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/quickstart_notifications_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: ID:JBM-8228 RelatesTo: jms:correlationID#ID:JBM-11264 11:20:41,210 INFO [STDOUT] ConsoleNotifier 2008/03/19 11:20:41.210<Hello from ESB-unaware JMS Client> 11:20:41,481 ERROR [NotificationList] Can't instantiate target <target class="NotifyFTP"> <ftp URL="ftp://jboss:jboss@atlantis.boston.redhat.com/remote/dir" filename="notification.txt"/> </target> org.jboss.soa.esb.notification.NotificationException: Could not complete FTP notification at org.jboss.soa.esb.notification.NotifyFTP.sendNotification(NotifyFTP.java:207) 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:566) 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: com.enterprisedt.net.ftp.FTPException: Permission denied. at org.jboss.internal.soa.esb.util.EdtFtpImpl.uploadFile(EdtFtpImpl.java:629) at org.jboss.soa.esb.notification.NotifyFTP.sendNotification(NotifyFTP.java:203) ... 14 more Caused by: com.enterprisedt.net.ftp.FTPException: Permission denied. at com.enterprisedt.net.ftp.FTPControlSocket.validateReply(FTPControlSocket.java:923) at com.enterprisedt.net.ftp.FTPControlSocket.setDataPort(FTPControlSocket.java:602) at com.enterprisedt.net.ftp.FTPControlSocket.sendPORTCommand(FTPControlSocket.java:480) at com.enterprisedt.net.ftp.FTPControlSocket.createDataSocketActive(FTPControlSocket.java:461) at com.enterprisedt.net.ftp.FTPControlSocket.createDataSocket(FTPControlSocket.java:432) at com.enterprisedt.net.ftp.FTPClient.setupDataSocket(FTPClient.java:1597) at com.enterprisedt.net.ftp.FTPClient.initPut(FTPClient.java:1632) at com.enterprisedt.net.ftp.FTPClient.putData(FTPClient.java:1704) at com.enterprisedt.net.ftp.FTPClient.put(FTPClient.java:1479) at com.enterprisedt.net.ftp.FTPClient.put(FTPClient.java:1465) at com.enterprisedt.net.ftp.FTPClient.put(FTPClient.java:1443) at org.jboss.internal.soa.esb.util.EdtFtpImpl.uploadFile(EdtFtpImpl.java:620) ... 15 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira