On Thursday, December 13, 2001, at 03:21 PM, 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
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.
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
If this is indeed on windows you can change the size of the scroll back buffer to capture the stack trace.
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
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.
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?
There are not any known, serious stability problems like you're seeing. That certainly doesn't mean there aren't any, just that we haven't been hearing a lot about it. The only way we can really judge this is based on user feedback. So to anyone, if your having stability problems like this then please let us know about it. That being said there are definitely problem areas and you're right it would be good to have better visibility on this.
This is what I know of.
- Namespace functionality is not perfect or entirely consistent across XPath/XUpdate and the API. It seems not a lot of people have been using this so it is rather lightly tested.
- Remote connections are broken in beta 4
- DTDs are not supported
- Some encodings cause problems for people. We only claim to support UTF-8 and UTF-16 though
- People constantly have problems setting up the addressbook
Alteratively an open bug database would be nice.
And until this week we did have one. Since we're in the process of moving to the ASF we still need to convert over to what is used there.
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.
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.
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]
Kimbro Staken XML Database Software, Consulting and Writing http://www.xmldatabases.org/
