Exception in Thread "http-bio-8081-exec-3" Java.lang.OutOfMemoryError:PermGen space

Preface:

In the http://www.cnblogs.com/wql025/p/4865673.html article I have described this anomaly also provides a solution, but the effect is not ideal, now in the way of this article, the effect is significant.

Currently this project can only log on, and then open the other function modules that the following exception occurs:

Exception in Thread "http-bio-8081-exec-3" Java.lang.OutOfMemoryError:PermGen space
At Java.lang.ClassLoader.defineClass1 (Native Method)
At Java.lang.ClassLoader.defineClass (classloader.java:800)
At Java.security.SecureClassLoader.defineClass (secureclassloader.java:142)
At Java.net.URLClassLoader.defineClass (urlclassloader.java:449)
At java.net.urlclassloader.access$100 (urlclassloader.java:71)
At Java.net.urlclassloader$1.run (urlclassloader.java:361)
At Java.net.urlclassloader$1.run (urlclassloader.java:355)
At java.security.AccessController.doPrivileged (Native Method)
At Java.net.URLClassLoader.findClass (urlclassloader.java:354)
At Java.lang.ClassLoader.loadClass (classloader.java:425)
At Java.lang.ClassLoader.loadClass (classloader.java:358)
At Org.eclipse.jdt.internal.compiler.classfmt.MethodInfo.decodeLocalVariableAttribute (methodinfo.java:529)
At Org.eclipse.jdt.internal.compiler.classfmt.MethodInfo.decodeCodeAttribute (methodinfo.java:511)
At Org.eclipse.jdt.internal.compiler.classfmt.MethodInfo.readCodeAttribute (methodinfo.java:482)
At Org.eclipse.jdt.internal.compiler.classfmt.MethodInfo.getArgumentNames (methodinfo.java:251)
At Org.eclipse.jdt.internal.compiler.classfmt.MethodInfo.initialize (methodinfo.java:349)
At Org.eclipse.jdt.internal.compiler.classfmt.ClassFileReader.initialize (classfilereader.java:1153)
At Org.eclipse.jdt.internal.compiler.classfmt.classfilereader.<init> (classfilereader.java:388)
At Org.apache.jasper.compiler.jdtcompiler$1.findtype (jdtcompiler.java:231)
At Org.apache.jasper.compiler.jdtcompiler$1.findtype (jdtcompiler.java:203)
At Org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.askForType (lookupenvironment.java:157)
At Org.eclipse.jdt.internal.compiler.lookup.PackageBinding.getTypeOrPackage (packagebinding.java:201)
At Org.eclipse.jdt.internal.compiler.lookup.Scope.getPackage (scope.java:2982)
At Org.eclipse.jdt.internal.compiler.ast.QualifiedTypeReference.getTypeBinding (qualifiedtypereference.java:97)
At Org.eclipse.jdt.internal.compiler.ast.TypeReference.internalResolveType (typereference.java:472)
At Org.eclipse.jdt.internal.compiler.ast.TypeReference.resolveType (typereference.java:571)
At Org.eclipse.jdt.internal.compiler.ast.TypeReference.resolveType (typereference.java:567)
At Org.eclipse.jdt.internal.compiler.ast.TypeReference.resolveSuperType (typereference.java:541)
At Org.eclipse.jdt.internal.compiler.lookup.ClassScope.findSupertype (classscope.java:1287)
At Org.eclipse.jdt.internal.compiler.lookup.ClassScope.connectSuperclass (classscope.java:938)
At Org.eclipse.jdt.internal.compiler.lookup.ClassScope.connectTypeHierarchy (classscope.java:1095)
At Org.eclipse.jdt.internal.compiler.lookup.CompilationUnitScope.connectTypeHierarchy (Compilationunitscope.java : 323)

As you can see from the name, this exception is a memory overflow. Encountered many times before, the solution is mostly to increase the Tomcat memory, but the effect is almost not ideal, today did not move Tomcat, just increased the memory of Eclipse, this program from http://bbs.csdn.net/topics/390961799 magi1201 Netizen's message.

Here are my steps to resolve:

1, first in the Eclipse installation directory to increase the startup parameters of Eclipse-- in the Eclipse installation directory INI file, I use the STS, so is the Sts.ini file .

Original file Parameters:

-startupplugins/org.eclipse.equinox.launcher_1. 3.100.v20150511-1540. jar--launcher.libraryplugins/org.eclipse.equinox.launcher.win32.win32.x86 _64_1. 1.300.v20150602-1417-productorg.springsource.sts.ide--launcher.defaultactionopenfile--  Launcher. xxmaxpermsize256m-vmargs-dosgi.requiredjavaversion=1.7-xms40m-xx:maxpermsize=256m-  xverify:none-dorg.eclipse.swt.browser.ieversion=10001-xmx1200m       

Adjusted file parameters:

-startupplugins/org.eclipse.equinox.launcher_1. 3.100.v20150511-1540. jar--launcher.libraryplugins/org.eclipse.equinox.launcher.win32.win32.x86 _64_1. 1.300.v20150602-1417-productorg.springsource.sts.ide--launcher.defaultactionopenfile--  Launcher. Xxmaxpermsize512m-vmargs-dosgi.requiredjavaversion=1.7-xms40m-xx:maxpermsize=512M- xverify:none-dorg.eclipse.swt.browser.ieversion=10001-xmx1200m        

Note: The red font is the modified parameter

2. Then in the Eclipse's server bar, find the Tomcat option to open the Tomcat configuration

2.1

2.2

2.3

The VM Arguments box below the Arguments label box is followed by your own Tomcat to start the virtual machine parameters. Note: The red line is labeled as new. Remember to click Apply and OK OH

PostScript: This method a try on the spirit, the original memory of this project only enough to log in, and then click on other features are the exception, the installation of the above method immediately after the restoration of normal. But the most important test is to modify the project in a running situation--to be tested ...

Exception in Thread "http-bio-8081-exec-3" Java.lang.OutOfMemoryError:PermGen space