Hello..
I have developed an swing application using "netBeans with JDK 1.6".
I am facing a problem very commonly.....
During execution of the programme it gets stuck for more than 1 minute.....
Its a very big problem and my Client is not happy with that.
any body have any solution...
Is there any path to remove this problem....?
THx
Can you corrolate the pauses with anything particular in the game, or anything particular in the execution of the JRE itself. Does it only happen on your client's machine, or does it happen on all machines? (E.g., your development machine?)
On the chance that the problem is an overly long garbage collection, try running with -XX:+PrintGCTimeStamps -XX:+PrintGCDetails. That will tell you how long the garbage collections take, and let you know when they are happening, so you can decide if those are the problem. If garbage collection is taking more than 1 minute on a modest heap (<1GB?), then you should check what else is running on the machine and if you have physical memory enough for the Java object heap. Running the Java object heap out of the paging file is not a good idea.
I am developing SWING application. The problem actually occurs when I scroll in the list of items which have the ListActionLIstener registered with them.
It not only ossurs on client side but on development side as well.
One of my colleague advice me to remove all the other JDKs and JREs from the system and run your application only having JDK and JRE 6.0.
Previously I had JDK 5.0 and JRE 5.0.
Acting on his advice, when I ran my application have JRE6.0 the problem remains still the same. Now it takes just few seconds less than before.
When I run my application on JRE 5.0 it runs perfect.
It there any patch available to remove this kind of problem...
Removing the JRE's that you aren't using shouldn't affect the JRE that you are using.
It might be diagnostic to profile your application under JRE-5.0 (where it runs well) and under JRE 6.0 (where it doesn't).
You might want to look for resource usage (heap size, garbage collection, paging, etc.) that is different between your application on JRE 5.0 and JRE 6.0.
