Re: [jetty-users] Jetty 10 SSL Problem

[Joakim Erdfelt <joakim@xxxxxxxxxxx>]

The forked JVM gets its arguments directly handed to it by using java.lang.ProcessBuilder(List<String> args).

The properties are passed in as a properties file to the forked JVM as well. 

It would be highly unlikely to be a forked JVM command line argument issue.

But let's investigate that anyway.

You can enable start.jar debug with `java -jar /path/to/start.jar --debug` when you execute.

Look for the lines with the patterns

DEBUG: Command Line: <num> entries

That tells you how many arguments.

DEBUG: [<num>] "<value>"

That dumps each command line argument separately, with added quotes around it in the DEBUG output (quotes not sent to forked JVM).

You can also use `java -jar /path/to/start.jar --list-config` and check the output.

If there are any entries in the "System Properties:" section, you will have a forked JVM.

The entries in the "Properties:" section list all of the configured properties for your instance.

Joakim Erdfelt / joakim@xxxxxxxxxxx

On Wed, Jun 28, 2023 at 2:35 PM Cantor, Scott <cantor.2@xxxxxxx> wrote:

> Im not using dry-run but the JVM does get forked.

I'd suggest verifying that it's not showing up in some manipulated form as a property on the command line of the child process. Just to be sure.

-- Scott


_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users