This doesn't answer your bug database or stability needs, but if you want to "log" the exceptions you only have to redirect stdout and stderr (I believe the exceptions go to stderr) with syntax on the command line. Assuming you're starting it by running a script (e.g. startup.bat on Windows) you'll want to edit the script and add the output redirection to the line that executes the actual java command. In startup.bat, it should be something like (excuse the line breaks):
%JAVACMD% -Xms16m -Xmx128m - Ddbxml.home=%DBXML_HOME% -classpath "%LOCALCLASSPATH%" -noverify org.dbxml.core.server.dbXML %DBXML_HOME%\config\system.xml >out.log 2>err.log To send std to the file "out.log" and stderr to the file "err.log" If you're running on Unix, you can similarly modify the shell script "start" (unless I'm mistaken, the stdout and stderr redirection syntax is the same). On 13 Dec 2001, at 22:21, Michael Hearn wrote: > Hiya again, > > Unfortunately although I'd very much like to use Xindice in my > software, I've been plagued by constant instabilities in the software > which have rendered it virtually unusable to me. For instance, even on > a clean install the software will sometimes throw exceptions for me on > startup (this is before even creating a new collection), and then > proceed to start as normal. If I shutdown the server using the > command, and restart it, there will be some different exceptions. > Unfortunately it doesn't log exceptions and as I can't scroll back to > see what the exceptions are (the stack trace is so long it fills the > screen) I can't figure out how to try and fix it. Running the shutdown > command (which for some reason asks for a collection context, so i > give it /) sometimes works fine, and other times will make the server > shut down but also throw a load of exceptions itself - usually it says > that the shutdown succeeded "maybe". Adding a collection throws an > exception for some reason, but appears to succeed. Then I try it again > after deleting it, and it works without an exception! > > I don't mean to complain as I know that everyone on the project is a > volunteer, but if there are any known stability problems could they be > documented with workarounds? Alteratively an open bug database would > be nice. At the very least it'd be nice to have some kind of exception > handling built in, rather than just dumping a stack trace to the > output. > > When I figure out how to get Forte to build it, I might have some time > to help out and do something about all this stuff i've just been > moaning about. Otherwise could somebody please advise what i could do > to increase it's stability? > > thanks -mike > > -- > ______________________________ > Michael Hearn > [EMAIL PROTECTED] > Jabber (jabber.org) [EMAIL PROTECTED] > >
