[Bug 66507] Catalina version command not honoring JAVA_OPTS variable

2023-04-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66507 --- Comment #5 from Thomas Starlinger --- (In reply to Eric Hamilton from comment #4) > Thomas, > Can you try moving the agent configuration to the CATALINA_OPTS variable? > > The CATALINA_OPTS variable is only used by the commands that start

[Bug 66507] Catalina version command not honoring JAVA_OPTS variable

2023-04-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66507 --- Comment #4 from Eric Hamilton --- Thomas, Can you try moving the agent configuration to the CATALINA_OPTS variable? The CATALINA_OPTS variable is only used by the commands that start the Tomcat server, while the JAVA_OPTS variable is used

[Bug 66507] Catalina version command not honoring JAVA_OPTS variable

2023-04-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66507 --- Comment #3 from Thomas Starlinger --- Hi. We're using an RMI agent to let JConsole connect to the Tomcat JVM. The agent is configured via JAVA_OPTS. Now, if I try to start version.sh resp. catalina.sh the system tries to start the agent wh

[Bug 66507] Catalina version command not honoring JAVA_OPTS variable

2023-03-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66507 Han Li changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug 66507] Catalina version command not honoring JAVA_OPTS variable

2023-03-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66507 --- Comment #1 from Eric Hamilton --- Updated suggested catalina.sh fix to conform with execution style of other commands: elif [ "$1" = "version" ] ; then eval "\"$_RUNJAVA\"" "$JAVA_OPTS" \ -classpath "\"$CATALINA_HOME/lib/catalina