• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
Sheriffs:
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
Bartenders:
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

JVM Hot Spot issue (in 1.6)

 
Ranch Hand
Posts: 91
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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 Dharani Vidhya
Ranch Hand
Posts: 91
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
i think your Perm Space that you allocated in JVM is not large enough
 
Karthick Dharani Vidhya
Ranch Hand
Posts: 91
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
OK,that's perfect
 
This is my favorite tiny ad:
Free, earth friendly heat - from the CodeRanch trailboss
https://www.kickstarter.com/projects/paulwheaton/free-heat
reply
    Bookmark Topic Watch Topic
  • New Topic