Kimbro Staken wrote:
I'm going to guess it can't bind to the port because it's already in use. You should have gotten a more descriptive error in that case though. I'm not sure why the NullPointerException propagated.
As best as I can tell from my system tools, the port is NOT in use.
Tried that already, things then proceed to fail while initializing the HTTP server...... same way.
Buried in the FAQ is a reference to 1.3.1 as having problems, but the details of that are not explicit.
Meanwhile, I've attempted to dig into the source code to figure out the problem and found that the
org.dbxml.server.* section of the tree doesn't seem to have source anywhere.... I assume that
the GopherServer is then extending a class file buried in one of the jars as it compiles...
You don't actually need the gopher server for anything, it was just a debugging tool from the early days. You can comment it out in system.xml to debug the problem. Also the source you're looking for is only available from CVS. In the Xindice tree it was rolled back into the main tree, but in dbXML it was a separate project.
Ok, I'll try to grab the source, and see where I can go from there...
