Tomcat - Versionsgeschichte

Jochen: /* Remote Monitoring */

2021-07-27T09:24:32Z

Remote Monitoring

← Nächstältere Version		Version vom 27. Juli 2021, 11:24 Uhr
Zeile 19:		Zeile 19:
	=== Remote Monitoring ===		=== Remote Monitoring ===

	Werden die Monitoring Tools Remote oder lokal und einem anderen Benutzer ausgeführt, so müssen folgende Einstellungen am Tomcat vorgenommen werden.		Werden die Monitoring Tools Remote oder lokal und unter einem anderen Benutzer ausgeführt, so müssen folgende Einstellungen am Tomcat vorgenommen werden.

	==== Command Line Interface (CLI) ====		==== Command Line Interface (CLI) ====

Jochen: /* JMX Monitoring */

2021-01-27T08:05:52Z

JMX Monitoring

← Nächstältere Version		Version vom 27. Januar 2021, 10:05 Uhr
Zeile 9:		Zeile 9:
	== JMX Monitoring ==		== JMX Monitoring ==

	Das Monitoring und Management via JMX in Java wird [https://docs.oracle.com/en/java/javase/11/management/monitoring-and-management-using-jmx-technology.html hier] beschrieben. Die Einstellungen für den Tomcat 9 [https://tomcat.apache.org/tomcat-9.0-doc/monitoring.html hier]. Als Tools zum JMX Monitoring dienen [https://openjdk.java.net/tools/svc/jconsole/ JConsole] oder [https://visualvm.github.io/ VisualVM].		Das Monitoring und Management via JMX in Java wird [https://docs.oracle.com/en/java/javase/11/management/monitoring-and-management-using-jmx-technology.html hier] beschrieben. Die Einstellungen für den Tomcat 9 [https://tomcat.apache.org/tomcat-9.0-doc/monitoring.html hier]. Als Tools zum JMX Monitoring dienen [https://openjdk.java.net/tools/svc/jconsole/ JConsole] oder [https://visualvm.github.io/ VisualVM].

			Bei der Verwendung von [https://visualvm.github.io/ VisualVM] sollte das Plugin ''VisualVM-MBeans'' installiert sein.

	=== Lokales Monitoring ===		=== Lokales Monitoring ===

Jochen: /* JMX Monitoring via Java VisualVM */

2021-01-27T07:50:15Z

JMX Monitoring via Java VisualVM

@@ Zeile 7: / Zeile 7: @@
-== JMX Monitoring via Java VisualVM ==
+== JMX Monitoring ==
-Zum (Remote) JMX Monitoring eines Tomcat müssen die folgenden JVM Parameter spezifiziert werden.
+Das Monitoring und Management via JMX in Java wird [https://docs.oracle.com/en/java/javase/11/management/monitoring-and-management-using-jmx-technology.html hier] beschrieben. Die Einstellungen für den Tomcat 9 [https://tomcat.apache.org/tomcat-9.0-doc/monitoring.html hier]. Als Tools zum JMX Monitoring dienen [https://openjdk.java.net/tools/svc/jconsole/ JConsole] oder [https://visualvm.github.io/ VisualVM].
 <syntaxhighlight lang="text">

Jochen: /* JMX Monitoring via Java VisualVM */

2019-10-04T14:06:52Z

JMX Monitoring via Java VisualVM

← Nächstältere Version		Version vom 4. Oktober 2019, 16:06 Uhr
Zeile 12:		Zeile 12:

	<syntaxhighlight lang="text">		<syntaxhighlight lang="text">
	Dcom.sun.management.jmxremote.port=8090		-Dcom.sun.management.jmxremote.port=8090
	Dcom.sun.management.jmxremote.ssl=false		-Dcom.sun.management.jmxremote.ssl=false
	Dcom.sun.management.jmxremote.authenticate=false		-Dcom.sun.management.jmxremote.authenticate=false
	</syntaxhighlight>		</syntaxhighlight>


	== Namensgebung der WAR Datei ==		== Namensgebung der WAR Datei ==

Jochen am 23. November 2018 um 07:43 Uhr

2018-11-23T07:43:20Z

← Nächstältere Version		Version vom 23. November 2018, 09:43 Uhr
Zeile 5:		Zeile 5:

	Eine sehr gute Beschreibung zum Thema Tomcat Remote Debugging kann [https://blog.trifork.com/2014/07/14/how-to-remotely-debug-application-running-on-tomcat-from-within-intellij-idea/ hier] gefunden werden.		Eine sehr gute Beschreibung zum Thema Tomcat Remote Debugging kann [https://blog.trifork.com/2014/07/14/how-to-remotely-debug-application-running-on-tomcat-from-within-intellij-idea/ hier] gefunden werden.


	== JMX Monitoring via Java VisualVM ==		== JMX Monitoring via Java VisualVM ==

Jochen: /* Remote Debugging */

2018-11-23T07:43:10Z

Remote Debugging

← Nächstältere Version		Version vom 23. November 2018, 09:43 Uhr
Zeile 4:		Zeile 4:
	== Remote Debugging ==		== Remote Debugging ==

	~~=== How do I configure~~ Tomcat ~~to support remote debugging? ===~~		Eine sehr gute Beschreibung zum Thema Tomcat Remote Debugging kann [https://blog.trifork.com/2014/07/14/how-to-remotely-debug-application-running-on-tomcat-from-within-intellij-idea/ hier] gefunden werden.

	~~A very good explanation to remote debugging can be found~~ [https://blog.trifork.com/2014/07/14/how-to-remotely-debug-application-running-on-tomcat-from-within-intellij-idea/ ~~here~~].


	== JMX Monitoring via Java VisualVM ==		== JMX Monitoring via Java VisualVM ==

Jochen am 23. November 2018 um 07:42 Uhr

2018-11-23T07:42:10Z

← Nächstältere Version		Version vom 23. November 2018, 09:42 Uhr
Zeile 8:		Zeile 8:
	A very good explanation to remote debugging can be found [https://blog.trifork.com/2014/07/14/how-to-remotely-debug-application-running-on-tomcat-from-within-intellij-idea/ here].		A very good explanation to remote debugging can be found [https://blog.trifork.com/2014/07/14/how-to-remotely-debug-application-running-on-tomcat-from-within-intellij-idea/ here].


	~~=== How do I remotely debug Tomcat using Eclipse? ===~~

	This answer assumes that you have a project set up and have some idea of what you are doing in this respect. If not then that is really outside the scope of this topic and you need to go to [http://eclipse.org/ eclipse.org] and read up on how to use your IDE, and maybe practice a little bit before you come back to this. We are also going to assume that you have some idea of what a debugger is and how to use one.

	* Make sure that Tomcat is started in remote debugging mode as described above and that your app is deployed.
	* Make sure that you have the sources for the code that you are trying to debug in your IDE. For the libraries and for Tomcat itself you can "attach" the sources to the jar files: open a class file and then click "Attach Source..." button.
	* If you have a servlet or something, set a breakpoint where it is sure to hit on the next request.
	* Go to "Run->Debug Configurations...". Click on "Remote Java Applications", then click "New". Type in the title. Note that port 8000 from the Tomcat instructions. Save and run.
	* Eclipse will connect to the JVM that Tomcat is running under. Wow, that was easy!

	~~Now go type the url to submit to your servlet or whatever in your browser. Boom you hit the breakpoint right? Have fun!~~


	~~=== How do I remotely debug Tomcat using NetBeans? ===~~

	This answer assumes that you know how to work with a NetBeans Project, and also how to use the NetBeans debugger. If not, please go to [http://www.netbeans.org/kb/using-netbeans/40/debug.html http://www.netbeans.org/kb/using-netbeans/40/debug.html] and read up on how to use NetBeans and its debugger.

	Starting with Tomcat trunk revision 1484409, the Tomcat source includes Ant tasks to configure your source directory as a NetBeans Free-Form Project. After you have successfully run Ant with the default build target (deploy), you can then run the ide-netbeans target. This task will configure your sandbox copy of Tomcat so the source can be inspected, maintained and debugged under the NetBeans IDE. You should follow the detailed instructions in the README.txt file that will have been installed in your new nbproject directory.

	Make sure that Tomcat is started in debug mode as described above, that your application is deployed, and that the sources are all defined as resources in your application. If you have a servlet or JSP file, set a breakpoint where you think a problem might be occurring. Go to "Run->Attach Debugger". A dialog pops up to let you specify the following options:

	* Debugger: JPDA Debugger
	* Connector: SocketAttach
	* Host: The IP address of the host your Tomcat installation is running on (127.0.0.1 if it is your local machine).
	* Port: The port of your Tomcat debugging interface, which should be 8000 if you've followed the instructions above.

	~~When you press OK, you have a debugging connection very similar to local debugging.~~

	Note that NetBeans has a second option -- you can debug JSP files and servlets locally using a Tomcat server that is bundled with the IDE. When you debug a JSP file or servlet in the IDE, the bundled Tomcat server automatically starts in debug mode, and the debugger connects to it.

	The Tomcat NetBeans targets have not yet been back-ported to Tomcat 7. You can copy the files from your copy of the trunk and they should only require minimal editing of paths to work with older versions of Tomcat.


	~~=== How do I remotely debug Tomcat using IntelliJ Ultimate? ===~~

	~~The following screenshots show the cinfiguration to remotely debug a Tomcat Web Server.~~

	~~[[File:Run-Debug Configurations_024.png]]~~

	~~[[File:Run-Debug Configurations_025.png]]~~

	~~[[File:Run-Debug Configurations_026.png]]~~

	~~[[File:Run-Debug Configurations_027.png]]~~

	== JMX Monitoring via Java VisualVM ==		== JMX Monitoring via Java VisualVM ==

Jochen: /* Remote Debugging */

2018-11-23T07:32:47Z

Remote Debugging

← Nächstältere Version		Version vom 23. November 2018, 09:32 Uhr
Zeile 5:		Zeile 5:

	=== How do I configure Tomcat to support remote debugging? ===		=== How do I configure Tomcat to support remote debugging? ===

	~~The short answer is to add the following options when the JVM is started:~~

	~~<syntaxhighlight lang="text">~~
	~~-Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n~~
	~~</syntaxhighlight>~~

	~~There are a number of ways you can do this depending on how you normally start Tomcat:~~

	* If you are using shell scripts to start Tomcat, start it with the following command:
	*: <syntaxhighlight lang="text">catalina jpda start</syntaxhighlight>
	*: It will start Tomcat so that a remote debugger can be connected to port 8000.
	*: The above mentioned options can be provided by setting certain environment variables. See the comments at the top of catalina.sh or .bat file for details.
	*: For example, the port number and JPDA transport implementation can be set with JPDA_ADDRESS=8000 and JPDA_TRANSPORT=dt_socket.
	* If you run Tomcat using service wrapper, add the above JVM options before any other JVM options. Check the documentation for the service wrapper to determine how to set JVM options.
	* If you start Tomcat from within an IDE, check the documentation for the IDE to determine how to set the required JVM options.

	~~The port does not need to be set to 8000, it may be any value appropriate for your system.~~

	~~Whilst this is very useful in development it should not be used in production because of both security and performance implications.~~


	~~=== How do I configure Tomcat to support remote debugging? Another way ===~~

	A very good explanation to remote debugging can be found [https://blog.trifork.com/2014/07/14/how-to-remotely-debug-application-running-on-tomcat-from-within-intellij-idea/ here].		A very good explanation to remote debugging can be found [https://blog.trifork.com/2014/07/14/how-to-remotely-debug-application-running-on-tomcat-from-within-intellij-idea/ here].

Jochen: /* Remote Debugging */

2018-11-22T09:32:35Z

Remote Debugging

← Nächstältere Version		Version vom 22. November 2018, 11:32 Uhr
Zeile 25:		Zeile 25:

	Whilst this is very useful in development it should not be used in production because of both security and performance implications.		Whilst this is very useful in development it should not be used in production because of both security and performance implications.


			=== How do I configure Tomcat to support remote debugging? Another way ===

			A very good explanation to remote debugging can be found [https://blog.trifork.com/2014/07/14/how-to-remotely-debug-application-running-on-tomcat-from-within-intellij-idea/ here].


Zeile 71:		Zeile 76:

	[[File:Run-Debug Configurations_027.png]]		[[File:Run-Debug Configurations_027.png]]


	== JMX Monitoring via Java VisualVM ==		== JMX Monitoring via Java VisualVM ==

Jochen am 22. Juni 2018 um 06:53 Uhr

2018-06-22T06:53:40Z

@@ Zeile 180: / Zeile 180: @@
 -Dhttp.proxyUser=<user name>
 -Dhttp.proxyPassword=<password>
 </syntaxhighlight>