Why doesn't VisualVm show all threads in running tomcat?

My tomcat (version: 5.5.25) launches an application that I am trying to run using VisualVM (version: 1.3.2). Everything looks good, but not all classes and methods are shown in visualVM. They are not in the line [main]. I know this because it is the name of the thread that I get if I get a breakpoint. Classes that go beyond the core, for example. [worker1], [worker2], ... are displayed correctly.

Any ideas what could be the reason? Or what could I try?

Since the application that I run (it is called Assentis Docbase ), it can be configured by default for the tomcat configuration. But they allowed me to expand the scope of my own classes and those that I want to profile.

VisualVM I run the default configuration at boot.

+5
source share
4 answers

You probably need to set up profiling root methods. See Profiling with VisualVM, part 1 and Profiling with VisualVM, part 2 . You can also use the "Sampler" tab to get a high-level image of what your Tomcat is doing.

+8

, "" :

  • .

  • , Thread.setName().

, , , Tomcat.


, . Google - .

+2

, VisualVM thread [main], , VisualVM 32 simoultanously. . " VisualVM" , 2, " NetBeans" :

" - 32".

: - (

+2

, " " .

, org.acme.competition.* (A) :

VisualVM Startup Configuration Dialog Box

org.acme.reference.ReferenceImpl (B), :

$ cat source.txt | java -Xverify:none \
    -agentpath:/usr/share/visualvm/profiler/lib/deployed/jdk16/linux-amd64/libprofilerinterface.so=/usr/share/visualvm/profiler/lib,5140 \
    -cp bin/ org.acme.reference.ReferenceImpl

:

Invalid result

VisualVM Startup " " org.acme.reference.*, :

Correct result

. > .

0

All Articles