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.

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"?

Kind Regards,
Stefan

Reply via email to