In general, FileLister is tested very well with the default
directory structure. If you changed this structure somehow and run into
problems not described below, we absolutely recommend to delete your installation
and extract the downloaded installation archive again!
- I don't know how to configure a virtual root
for my servlet runner...
For Tomcat/Catalina, see Tip 1.
For any other servlet runner, please consult the corresponding documentation.
- I can't configure a web or a FTP server because
my host doesn't run any.
Try to use your servlet runner then! If this doesn't work, leave
the "link.prefix" setting empty. This means you can't download
listed files at all which we think is quite sad. We suggest to consider
running FileLister on another host then...
- The log file of my servlet runner becomes that
big running the InitialIndexer regularly!
See Tip 6.
- I simply want to configure a new installation
for another server but I'm seeing lots of exceptions in the setup
See Tip 9.
- I'm seeing a strange exception and don't know
what to do!
Read the first line of the stack trace! If somewhere further below,
a "root cause" is listed, this is the exception to look
for. Here is a list of some exceptions that might occur:
Especially on Linux platforms, the OutOfMemoryError occurs quite
easily, because the JVM's default settings are rather conservative.
Building very large zip files, you run into troubles anyway if
the JVM can't be swapped onto the hard disk. Anyway, modify the
JVM setting by adding "-Xms128m -Xmx156m" (or even more,
see help by executing "java -X" on the command prompt)
before the "-classpath" argument of your servlet runner's
java command line. To do this, open the servlet runner's execution
file in an editor and look for the line "java -classpath
- java.lang.ClassNotFoundException or java.lang.NoClassDefFoundError:
FileLister requires the following jar files: A MySQL JDBC driver
jar, a Servlet API jar, the kunststoff.jar, the xercesImpl.jar,
the xmlParserAPIs.jar and FileLister's own jar files named filelister-0.5.jar
and util-1.0.jar. If one of those jar files isn't accessible for
FileLister, a ClassNotFoundException or a NoClassDefFoundError
FileLister requires a database on the SQL server specified in
the JDBC parameters of the config file. If this database isn't
accessible or the specified user account is not allowed to create,
modify and drop tables or the amount of simultaneous connections
raise to high for the JDBC driver (about 30 - 40 for mm.mysql)
or you didn't define a table name where FileLister should store
the index in, a SQLException describing the problem will occur.
FileLister's indexing service (started by the InitialIndexer or
a click on the "Directory search" option in the web
GUI) needs to be allowed to access the whole directory structure
one below the virtual root. If the JVM realizes that it's not
allowed to access a file or directory within this tree, a SecurityException
is thrown. In this case, you should extend the list of no go areas
with the directory/-ies that FileLister isn't allow to access
or change the file system's access rights.
FileLister needs at least the version 2.0.11 of the mm.mysql JDBC
driver. Please upgrade your version of the driver with the one
of the distribution if you see some exception text containing
- java.lang.VerifyError: (class: org/alltimeflashdreamer/util/xml/XMLDataHandler,
method: cloneDocument signature: (Lorg/w3c/dom/Document;)Lorg/w3c/dom/Document;)
Incompatible object argument for function call:
Your servlet runner runs a too old version of the org.w3c.dom
package, e.g. like Tomcat 3.2.3. In this case, you need to upgrade
your servlet runner to a newer version.
Back to Index / License