Hi,
if you want to play with it the ftp community
module has been checked in.
I also added to the community release section
so it should show up on the nightly build community
modules starting tomorrow.
As it stands now it works on port 8021 and allows the
default admin user to login. It exposes only part of
the data directory, in particular $DATA_DIR/data,
to prevent silly issues with people messing with
the configuration (you're not supposed to hand edit
it, remember? 
)
I hope to make both configurable once I figure out a
good way to store the configuration itself
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
On 02/06/10 02:23, Andrea Aime wrote:
It exposes only part of
the data directory, in particular $DATA_DIR/data,
to prevent silly issues with people messing with
the configuration (you're not supposed to hand edit
it, remember? )
Riiight. 
[The app-schema community smiles and nods slowly.]
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
That's great. I tested it and was able to upload some data (both with FileZilla and command line, FireFtp seems to work but fails to provide proper UI feedback, so a FireFtp problem, not a server one).
Yet, I found that if I mvn jetty:run -Pftp:
- I can connect to ftp if I don't access the web UI
- Accessing the web UI always produces the following exception, regardless of having previously connected to ftp or not:
org.apache.ftpserver.FtpServerConfigurationException: Failed to bind to address 0.0.0.0/0.0.0.0:8021, check configuration
at org.apache.ftpserver.listener.nio.NioListener.start(NioListener.java:183)
at org.apache.ftpserver.impl.DefaultFtpServer.start(DefaultFtpServer.java:80)
at org.geoserver.ftp.FTPServerManager.startServer(FTPServerManager.java:55)
at org.geoserver.ftp.FTPServerManager.onApplicationEvent(FTPServerManager.java:65)
- After having tried to access the UI, connecting to ftp is no longer possible, client stalling on "Status: Connection established, waiting for welcome message..." and then timing out.
Cheers,
Gabriel
On 6/1/10 3:23 PM, Andrea Aime wrote:
Hi,
if you want to play with it the ftp community
module has been checked in.
I also added to the community release section
so it should show up on the nightly build community
modules starting tomorrow.
As it stands now it works on port 8021 and allows the
default admin user to login. It exposes only part of
the data directory, in particular $DATA_DIR/data,
to prevent silly issues with people messing with
the configuration (you're not supposed to hand edit
it, remember? )
I hope to make both configurable once I figure out a
good way to store the configuration itself
Cheers
Andrea
--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Gabriel Roldan ha scritto:
That's great. I tested it and was able to upload some data (both with FileZilla and command line, FireFtp seems to work but fails to provide proper UI feedback, so a FireFtp problem, not a server one).
Yet, I found that if I mvn jetty:run -Pftp:
- I can connect to ftp if I don't access the web UI
- Accessing the web UI always produces the following exception, regardless of having previously connected to ftp or not:
org.apache.ftpserver.FtpServerConfigurationException: Failed to bind to address 0.0.0.0/0.0.0.0:8021, check configuration
at org.apache.ftpserver.listener.nio.NioListener.start(NioListener.java:183)
at org.apache.ftpserver.impl.DefaultFtpServer.start(DefaultFtpServer.java:80)
at org.geoserver.ftp.FTPServerManager.startServer(FTPServerManager.java:55)
at org.geoserver.ftp.FTPServerManager.onApplicationEvent(FTPServerManager.java:65)
- After having tried to access the UI, connecting to ftp is no longer possible, client stalling on "Status: Connection established, waiting for welcome message..." and then timing out.
Oh, interesting, I never use that, tested with Tomcat and could
not find issues. A theory (which might be faulty): how many threads is
jetty:run using to serve requests? A firefox connection will suck up 6
and since it uses persistent connections, those 6 will be gone.
This might or might not have anything to do with the problem, but I've
seen a similar problem trying to run requests from the command line (using curl) when I forcefully limited tomcat to, say, 6-8 connections
tops
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Gabriel Roldan ha scritto:
That's great. I tested it and was able to upload some data (both with FileZilla and command line, FireFtp seems to work but fails to provide proper UI feedback, so a FireFtp problem, not a server one).
Yet, I found that if I mvn jetty:run -Pftp:
- I can connect to ftp if I don't access the web UI
- Accessing the web UI always produces the following exception, regardless of having previously connected to ftp or not:
Ah ha, reproduced it. And hopefully fixed it as well as of r14472
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.