Le 26/03/2017 à 13:25, Stefan Seelmann a écrit : > Hi, > > another test that is failing in Studio is related to ApacheDS repair mode. > > I found out that when executing the "repair" command from commandline > (using apacheds.sh from tar.gz) we (1) start the server with boolean > flag startServers=false and then (2) run the repair, so far so good. But > when repair is finished the JVM doesn't terminate. It also not possible > to stop it via "stop" command because shutdown listener is not started.
Ah, that is clearly wrong. The idea was to repair the database, then to start the server properly, including the shutdown listener. That part is missing, I think. > > I think we need to change > (1) the UberJarMain.repair() method to stop the service again so the JVM > can terminate > (2) all the init scripts to run repair in interactive mode and await > termination > > Or, should we change the repair back to behaviour in 2.0.0-M23 where it > was more a "start and repair"? Yes, I think it would be better. We could also add a flag that does not restart the server once teh database has been repaired, but it might be superfluous. My take is that we should just fix the current behavior, and leave it as is, until Mavibot get ready (I'll give a status in a mail later today). Thanks Stefan ! (I wish week-ends last 3 or 4 days ;-) -- Emmanuel Lecharny Symas.com directory.apache.org
