Phlogiston,
Just curious if you saw Niklas's note earlier, from your response here,
it looks like you missed it.
--- Niklas Note ---
Over at [EMAIL PROTECTED] Jeanfrancois Arcand from the Glassfish
team quickly figured out that it is this bug in Glassfish:
https://glassfish.dev.java.net/issues/show_bug.cgi?id=5321
This bug affects all uses of NIO in Glassfish, thereby also MINA. It
is resolved by adding the following to domain.xml:
<jvm-options>-Dcom.sun.enterprise.server.ss.ASQuickStartup=false</jvm-options>
--- End of Note ---
Glassfish
---------
On Linux the Glassfish default domain is called "domain1", and it's
located here:
glassfish/domains/domain1/config/domain.xml
Inside the domain.xml file is a commented-out section that addresses the
option. The section is located at about line 201.
<!--
Use the following jvm-options element to disable the quick startup
com.sun.enterprise.server.ss.ASQuickStartup=false
-->
Domain Configuration
--------------------
The quick start for Glassfish should be set to false like this:
<jvm-options>-Dcom.sun.enterprise.server.ss.ASQuickStartup=false</jvm-options>
This should be inserted right above the comment:
...
<jvm-options>-Dcom.sun.enterprise.taglisteners=jsf-impl.jar</jvm-options>
<jvm-options>-XX:NewRatio=2</jvm-options>
<jvm-options>-Dcom.sun.enterprise.server.ss.ASQuickStartup=false</jvm-options>
<!--
Use the following jvm-options element to disable the quick startup
com.sun.enterprise.server.ss.ASQuickStartup=false
-->
...
---------
Understand this is not an Apache FTPServer issue, it is the NIO section
of the Container Server. Older FTP engines that do not use NIO will not
likely be affected by this issue, however newer high performance ones
that use NIO will likely be affected. So if you intend to write your
own code and use NIO with Glassfish, you will experience the same
problem you are seeing with the Apache Ftp Server. The simple solution
is to follow the instructions of the people that wrote Glassfish, which
is the detailed above.
Good luck.
Andy
Phlogiston Eight wrote:
Thank you, David, for the link to a third example of a <server>-<server>
defined FtpServer bean, which works in Spring, and accepts client connections.
I copied it over, subbed-in my values where necessary, built, and ran it. It builds and runs with no errors reported.
However-- it cannot be connected to by a client. There is no way to connect to it. So it is not possible to FTP with it. I tried 4 different FTP client applications. So looks like Apache's FTP Server is not right for my project. I'll scrap all our work and start over from scratch.
I believe you that it worked for you, I don't dispute that. But you did mention Glassfish has a known bug when running FTPServer. And Glassfish is our existing App Server. So that is probably why FTPServer doesn't work at all for us. This is especially clear now, since a known, working example, coded by others, also fails to work.
But thanks for trying, I appreciate it.
_________________________________________________________________
You live life beyond your PC. So now Windows goes beyond your PC.
http://clk.atdmt.com/MRT/go/115298556/direct/01/
