Open mkubaty opened 4 years ago
Hello there, we recently used the java version java version "11.0.6" 2020-01-14 LTS for evaluation purposes. It turned out, this particular version does not bind the specified debug port for AEM to 0.0.0.0:$port but to 127.0.0.1:$port until you explicitely define it by setting interface and port . Please see https://stackoverflow.com/questions/138511/what-are-java-command-line-options-to-set-to-allow-jvm-to-be-remotely-debugged and https://www.oracle.com/technetwork/java/javase/9-notes-3745703.html#JDK-8041435
java version "11.0.6" 2020-01-14 LTS
0.0.0.0:$port
127.0.0.1:$port
Unfortunately the type-checker in instance.pp, line 36 validate_integer($debug_port) does not allow to set IP and port.
validate_integer($debug_port)
We are about to fix that internally, and think it may bee of interest for you too. Our fix will be provided to you, after we merged into our fork.
Kind regards
@mkubaty any update on the contribution?
@bdhoine No updates, sorry. Internal discussion ongoing on how to proceed
Hello there, we recently used the java version
java version "11.0.6" 2020-01-14 LTS
for evaluation purposes. It turned out, this particular version does not bind the specified debug port for AEM to0.0.0.0:$port
but to127.0.0.1:$port
until you explicitely define it by setting interface and port . Please see https://stackoverflow.com/questions/138511/what-are-java-command-line-options-to-set-to-allow-jvm-to-be-remotely-debugged and https://www.oracle.com/technetwork/java/javase/9-notes-3745703.html#JDK-8041435Unfortunately the type-checker in instance.pp, line 36
validate_integer($debug_port)
does not allow to set IP and port.We are about to fix that internally, and think it may bee of interest for you too. Our fix will be provided to you, after we merged into our fork.
Kind regards