[NIFI-5556] Expose JVM debugging via command-line argument

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.7.1
• Component/s: Configuration, Tools and Build
• Labels: debug jvm toolkit
• Assignee: Troy Melhase
• Reporter: Andy LoPresto
• Created: 27/Aug/18 15:54
• Updated: 17/Apr/20 04:15

Description

Recently I have been performing remote JVM debugging on a number of NiFi components – core instances, TLS toolkit, etc. Currently, to enable/disable JVM debugging requires manually modifying the bootstrap.conf file or the *.sh file and (un)commenting/adding the following line(s):

bootstrap.conf

java.arg.debug=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8000

tls-toolkit.sh

# exec "${JAVA}" -cp "${CLASSPATH}" ${JAVA_OPTS:--Xms12m -Xmx24m} org.apache.nifi.toolkit.tls.TlsToolkitMain "$@"
   exec "${JAVA}" -cp "${CLASSPATH}" ${JAVA_OPTS:--Xms12m -Xmx24m} -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8000 org.apache.nifi.toolkit.tls.TlsToolkitMain "$@"

I propose we decide on a standard command-line flag or environment variable which can be set to enable/disable JVM debugging (and optional flag/variable to enable/disable suspend) in order to make this easier for developers.

My suggestion is to follow a pattern like Kafka uses, as proposed in this StackOverflow answer.

This can be copied to NiFi Registry, MiNiFi Java, etc.

Issue Links

• links to: GitHub Pull Request #3441