Skip to main content

Java Virtual Machine - The Method Area

Inside a Java Virtual Machine instance, information about loaded types is stored in a logical area of memory area  called the method area. When the Jave Virtual Machine loads a type, it uses a class loader to locate the appropriate class file. The  class loader reads in the class file -- a linear stream to binary data  and passes it to the virtual machine. Memory for class(static) variables declared in the class is also taken from the method area.

The method area can also be garbage collected. Because Java programs can  be dynamically extended via class loader objects, classes can become "unreferenced" by the application. If a class becomes unreferenced, a Java Virtual Machine can unload the class(garbage collect it) to keep the memory occupied by the method area at a minimum.

Type Information: for each type it loads, a Java Virtual Machine must store the following kinds of information in the method area:
. the fully qualified name of the type
. the fully qualified name of the type's direct superclass
.whether or not the type is a class or an interface
. the type's modifiers(some sumbset of ' public , abstract, final)
.an ordered list of the fully qualified names of any direct superinterfaces.

In addition to basic type information listed above, it must also store for each loaded type:
. the constant pool for the type
. field information
. method information
.all class(static) variables declared in the type, except constants
.a reference to class ClassLoader
. a reference to Class Class

Comments

Post a Comment

Popular posts from this blog

JasperReports - Configuration Reference

Data Source / Query Executer net.sf.jasperreports.csv.column.names.{arbitrary_name} net.sf.jasperreports.csv.date.pattern net.sf.jasperreports.csv.encoding net.sf.jasperreports.csv.field.delimiter net.sf.jasperreports.csv.locale.code net.sf.jasperreports.csv.number.pattern net.sf.jasperreports.csv.record.delimiter net.sf.jasperreports.csv.source net.sf.jasperreports.csv.timezone.id net.sf.jasperreports.ejbql.query.hint.{hint} net.sf.jasperreports.ejbql.query.page.size net.sf.jasperreports.hql.clear.cache net.sf.jasperreports.hql.field.mapping.descriptions net.sf.jasperreports.hql.query.list.page.size net.sf.jasperreports.hql.query.run.type net.sf.jasperreports.jdbc.concurrency net.sf.jasperreports.jdbc.fetch.size net.sf.jasperreports.jdbc.holdability net.sf.jasperreports.jdbc.max.field.size net.sf.jasperreports.jdbc.result.set.type net.sf.jasperreports.query.chunk.token.separators net.sf.jasperreports.query.executer.factory.{language} net.sf.jasperreports.xpath....
Post a Comment
Read more

Stretch a row if data overflows in jasper reports

It is very common that some columns of the report need to stretch to show all the content in that column. But  if you just specify the property " stretch with overflow' to that column(we called text field in jasper report world) , it will just stretch that column and won't change other columns, so the row could be ridiculous. Haven't find the solution from internet yet. So I just review the properties in iReport one by one and find two useful properties(the bold  highlighted in example below) which resolve the problems.   example: <band height="20" splitType="Stretch" > <textField isStretchWithOverflow="true" pa...
4 comments
Read more

Live - solving the jasper report out of memory and high cpu usage problems

I still can not find the solution. So I summary all the things and tell my boss about it. If any one knows the solution, please let me know. Symptom: 1.        The JVM became Out of memory when creating big consumption report 2.        Those JRTemplateElement-instances is still there occupied even if I logged out the system Reason:         1. There is a large number of JRTemplateElement-instances cached in the memory 2.     The clearobjects() method in ReportThread class has not been triggered when logging out Action I tried:      About the Virtualizer: 1.     Replacing the JRSwapFileVirtualizer with JRFileVirtualizer 2.     Not use any FileVirtualizer for c...
1 comment
Read more