wood burning stoves*
The moose likes Performance and the fly likes JVM Hot Spot issue (in 1.6) Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Performance
Bookmark "JVM Hot Spot issue (in 1.6)" Watch "JVM Hot Spot issue (in 1.6)" New topic
Author

JVM Hot Spot issue (in 1.6)

Karthick Dharani Vidhya
Ranch Hand

Joined: Feb 23, 2008
Posts: 88
Hi,

If i run my java application using 1.5, it works fine.
The same application if I run using 1.6.0_13, after some time the java application closes by genarting the below mentioned file in my desktop.





What I see is, in LineNo.155 the PermSize is used 99%.
I have not specified any PermSize. Can some one tell me, what will be the default PremSize?
If someone has already faced it, could you please suggest some solutions.

Karthick D V
Karthick Dharani Vidhya
Ranch Hand

Joined: Feb 23, 2008
Posts: 88
Hi All,

Sorry for the late reply.

The day I posted the above question, I came to know that this happens when both JVM code and native code tries to access same native resource. See below.

NATIVE
---------

Stack: [0x02fa0000,0x02ff0000], sp=0x02fef2a4, free space=316k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [awt.dll+0x3920c]

JVM
----

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j sun.awt.windows.WToolkit.eventLoop()V+0
j sun.awt.windows.WToolkit.run()V+69
j java.lang.Thread.run()V+11
v ~StubRoutines::call_stub

This happens many time in 1.6, as Sun has enhanced the use of D3D feature. To avoid this error, I was suggested to set the below parameter to FALSE. (If your application is not using any high level 3D rendering)

-Dsun.java2d.d3d=false.

After setting this, it looks ok.
tom wangrui
Greenhorn

Joined: Aug 16, 2009
Posts: 3
i think your Perm Space that you allocated in JVM is not large enough
Karthick Dharani Vidhya
Ranch Hand

Joined: Feb 23, 2008
Posts: 88
Hi,

Thanks for the reply.

At first, even I thought it could be Perm Size issue. But after finding the above solution in SUN's site, i just set that property to false. I did not change the Perm size of the application, but with this property it looks OK till today.
tom wangrui
Greenhorn

Joined: Aug 16, 2009
Posts: 3
OK,that's perfect
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: JVM Hot Spot issue (in 1.6)