Home/ Questions/Q 36835
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T14:27:21+00:00

I am calling a vendor’s Java API, and on some servers it appears that

  • 0

I am calling a vendor’s Java API, and on some servers it appears that the JVM goes into a low priority polling loop after logging into the API (CPU at 100% usage). The same app on other servers does not exhibit this behavior. This happens on WebSphere and Tomcat. The environment is tricky to set up so it is difficult to try to do something like profiling within Eclipse.

Is there a way to profile (or some other method of inspecting) an existing Java app running in Tomcat to find out what methods are being executed while it’s in this spinwait kind of state? The app is only executing one method when it gets in this state (vendor’s method). Vendor can’t replicate the behavior (of course).

Update:

Using JConsole I was able to determine who was running and what they were doing. It took me a few hours to then figure out why it was doing it. The problem ended up being that the vendor’s API jar that was being used did not match exactly to the the database configuration that it was using. It was defaulting to having tracing and performance monitoring enabled on the servers that had the slight mis-match in configuration. I used a different jar and all is well.

So thanks, Joshua, for your answer. JConsole was extremely easy to setup and use to monitor an existing application.

@Cringe – I did some experimenting with some of the options you suggested. I had some problems with getting JProfiler set up, it looks good (but pricey). Going forward I went ahead and added the Eclipse Profiler plugin and I’ll be looking over the different open source profilers to compare functionality.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. If you are using Java 5 or later, you can connect to your application using jconsole to view all running threads. jstack also will do a stack dump. I think this should still work even inside a container like Tomcat.

    Both of these tools are included with JDK5 and later (I assume the process needs to be at least Java 5, though I could be wrong)

    Update: It’s also worth noting that starting with JDK 1.6 update 7 there is now a bundled profiler called VisualVM which can be launched with ‘jvisualvm’. It looks like it is a java.net project, so additional info may be available at that page. I haven’t used this yet but it looks useful for more serious analysis.

    Hope that helps

    • 0