Note that there are some explanatory texts on larger screens.

plurals
  1. POjava.lang.OutOfMemoryError: PermGen space with tomcat7 windows service
    primarykey
    data
    text
    <p>i am running <strong>tomcat 7.0.33</strong> on <strong>windows server 2008 R2</strong> (i installed tomcat as windows service)</p> <ul> <li><strong>JDK version:</strong> <code>jdk1.6.0_25 64-bit</code></li> <li><p><strong>Tomcat options:</strong></p> <ol> <li><strong>Java Virtual Machine:</strong> <code>C:\Program Files\Java\jre6\bin\server\jvm.dll</code> (BTW, i don't have client folder inside jre)</li> <li><strong>Initial memory pool:</strong> 1000 MB</li> <li><p><strong>Maximum memory pool:</strong> 2000 MB</p> <p>when i check the server status, i can see that the server is using the memory i configured.</p></li> <li><p><strong>Environment Variables (SYSTEM VARIABLES) Configuration:</strong></p> <ul> <li><strong>JAVA_HOME:</strong> <code>C:\Program Files\Java\jdk1.6.0_25</code></li> <li><strong>Path:</strong> <code>...;%JAVA_HOME%\bin;....</code></li> </ul></li> </ol></li> </ul> <p>do i need to add <strong>CATALINA_HOME</strong> and <strong>JAVA_OPTS</strong> system variables too ?</p> <p><strong>ISSUE:</strong> i have two web applications <strong>APP1</strong>,*<em>APP2</em>* when i deploy each one separately, i can find that memory use for</p> <p><strong>APP1</strong>= 198 MB <strong>APP2</strong>= 104 MB</p> <p>Information about the applications:</p> <p><strong>APP1,APP2</strong>: Spring Maven applications that includes in the libraries other small maven spring applications.</p> <p>APP1: contains webservices, that APP2 uses them.</p> <p>if i tried to deploy both of them on same tomcat instance, i always get</p> <pre><code>java.lang.OutOfMemoryError: PermGen space </code></pre> <p>please advise what might be causing this issue.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload