(didn't appear to get through, again, resending)
OK, many thanks Kimbro, you've answered many of my questions.
> This is not normal and I've never seen it do this on UNIX. I have > however heard of something like this on windows, I think it's usually > windows 98 but to this point I haven't been convinced that it is > anything but a rare occurrence due to misconfiguration. If that is not > the case I'd like to hear more detail on it.
Yes, you're right, this is on Windows 98 with the Sun JDK 1.3.1_01 release. I'm pretty sure I've configured it correctly, as in setup the environment variables and run the server according to instructions. I appreciate that most of you will work on Linux, but I haven't currently got it set up. Soon hopefully.
> The shutdown command needs the collection context because that is how > it locates the server. In a default installation /db would be the > proper context to use.
Ah, ok. Would using / as the collection context instead cause problems?
> There is exception handling built in but like many things in the > server it isn't perfect and you seem to actually be encountering > things that are true exceptions.
Hmm, OK. I'll see if I can improve it on windows.
Oh yes, one thing - it's not possible to pipe STDERR in DOS (grr) but you can use a little program called stderr.exe to join stderr and stdout together so they can be captured. Just for future reference you know, if you get someone else on windows with a long exception.
thanks -mike
