https://issues.apache.org/bugzilla/show_bug.cgi?id=46218
--- Comment #3 from Michael Gratton <[EMAIL PROTECTED]> 2008-11-16 04:52:19 PST --- I can't test it out right now since I had to put that machine back into production for use tomorrow (Monday AEST). To reproduce, on a reasonably fast dual-core machine, just continually start and stop Xindice. I was effectively doing: while true; do xindiced start sleep 5 xindice ld -c /db/some/10k+collection xindice stop sleep 5 done If this is still a problem, you'll see instances of xindice slowly piling up. New ones can start even though the old ones are hanging around since the Jetty handler will have stopped it listening on whatever port is is configured to do so. Note this might also indicate the "db.lock" database lock mechanism isn't actually functioning. What are the odds of this getting applied to 1.1 and having a 1.1.1 release? I don't want to move to 1.2 on this machine yet. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
