Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
Showing results for 
Search instead for 
Did you mean: 

Java 1.4.2_02/Red Hat Enterprise WS 3.0 question

pierre gauthier
Occasional Contributor

Java 1.4.2_02/Red Hat Enterprise WS 3.0 question

I have written a Java application
using JDK 1.4.2_02 on my HP XW4100 workstation
running Red Hat Enterprise WS 3.0. The
application uses pure swing components with
no external third-party classes.

For some reasons, the application freezes
randomly when resizing the window or performing
other operations on the GUI I wrote.
When the application freezes, the CPU usage
gets around 95%. There's no computation loop
in my application I know of that could get into
in endless loop. I used JBuilder to create the
application. JBuilder itself is a Java application and runs fine. I see the problem
when running from JBuilder or outside JBuilder.

Any suggestions how to track down this problem
would be appreciated.
Honored Contributor

Re: Java 1.4.2_02/Red Hat Enterprise WS 3.0 question

Hi ,

What is the memory utilization at the time ?.

If the CPU utilization is only affected then upgrade to JDK version 1.4.2_04.



Innovations are made when conventions are broken
pierre gauthier
Occasional Contributor

Re: Java 1.4.2_02/Red Hat Enterprise WS 3.0 question

Thanks for your help.

The memory usage is not a problem.
Only CPU utilization.

I will try 1.4.2_04.
Rick Beldin
Esteemed Contributor

Re: Java 1.4.2_02/Red Hat Enterprise WS 3.0 question

Either the JVM is going through some internal computations, or Swing is likely to be doing some X-related things necessary to re-layout the interface. Depending on the interface, this could be really inefficient.

As for isolation:

- xscope / xmon would tell you whether the app is generating lots of X-protocol during the times of high CPU

- simplyfing the Java app until the problem appears disappears.
Necessary questions: Why? What? How? When?