Im not using dry-run but the JVM does get forked. im just starting jetty through shell atm like this:
java -jar /opt/jetty/start.jar Mit freundlichen Grüßen/Best Regards *Timo Brunn* Website: timo-brunn.de <https://timo-brunn.de> /Um ihre Echtheit zu bestätigen, wurde diese E-Mail digital signiert. To prove its authenticity, this E-Mail has been digitally signed./ On 28/06/2023 19:22, Cantor, Scott wrote:
It's pretty likely that your startup approach is mucking with the password. From my own experience, using --dry-run for example botched the "escaping" of the settings that get extracted and passed to the new process command as of a recent 10.x patch, something I raised in github. I don't know that you're using --dry-run, but given that you may be, that's a possible cause. I had to run the command line through sed to strip the escaping back out. -- Scott _______________________________________________ jetty-users mailing list jetty-users@eclipse.org To unsubscribe from this list, visithttps://www.eclipse.org/mailman/listinfo/jetty-users
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ jetty-users mailing list jetty-users@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users
