Tim Space qwertypoi75 at hotmail.com writes:
Here is the result of ps -aef | grep java
...
Hi,
I see it has been some time since the last message is posted but I had a similar
problem that took quite an amount of my time. I want to share my experience
here.
Most probably, tomcat is not
I see these errors(tomcat 6) :
Exception in thread http-bio-8080-exec-21
java.lang.OutOfMemoryError: PermGen space
Exception in thread com.mchange.v2.async.ThreadPoolAsynchronousRunner
$PoolThread-#0 java.lang.OutOfMemoryError: PermGen space
And checked the the JAVA parameters :
On Thu, Nov 3, 2011 at 16:25, celtic man dheerajman...@hotmail.com wrote:
I see these errors(tomcat 6) :
Exception in thread http-bio-8080-exec-21
java.lang.OutOfMemoryError: PermGen space
Exception in thread com.mchange.v2.async.ThreadPoolAsynchronousRunner
$PoolThread-#0
2011/11/3 Francis GALIEGUE f...@one2team.com:
On Thu, Nov 3, 2011 at 16:25, celtic man dheerajman...@hotmail.com wrote:
I see these errors(tomcat 6) :
Exception in thread http-bio-8080-exec-21
java.lang.OutOfMemoryError: PermGen space
Exception in thread
Hello,
I have a situation where an application is accessable from outside in
staging and production environment, but shouldn't be open for public
in staging environment.
What we did so far was, that we excluded everyone via web.xml:
!-- security configuration --
login-config
Leon,
Is it a requirement for you to use BASIC auth? or could you use
something like the Remote Address Filter to restrict by IP address?
https://tomcat.apache.org/tomcat-6.0-doc/config/valve.html#Remote_Address_Filter
If you configure this valve in the restricted environment you can then
Permgen memory leaks can cause those permgen OOM.
One common cause is webapps not cleaning up after themselves on context
shutdown. This leaks every loaded class from the webapp into the permgen
whenever the application is unloaded.
Knowing this one can workaround these leaks by being careful
