I had a post
http://anshuiitk.blogspot.com/2010/11/excessive-full-garbage-collection.html
.. it could help in understand the basics .. let me know if more i can help
further ..
--
View this message in context:
On 22/07/10 21:53, James Carman wrote:
I'm running Tomcat, so it's:
$ env | grep CATALINA
CATALINA_OPTS= -Xmx4096m -Xms2048m -XX:MaxPermSize=1024m
-XX:+UseParallelGC -server
Well, if you have increased memory for the permanent generation several
times and keep seeing this error, for me this
i think the problem with those memory analyzers that they give you the heap
Not the non heap, which is currently the problem..
If really constantly classes are leaked without that you constantly
redeploy web applications (because that would be a leak somewhere in
wicket or the app itself)
but the
Johan,
This shouldn't happen if the number of class similar to B are
finite, correct (at least not with 1GB of permgen)? Java shouldn't be
generating constructors multiple times. There would be one
ObjectStreamClass for each type of object (as I understand the code),
since they use that
On 23/07/10 10:19, Johan Compagner wrote:
i think the problem with those memory analyzers that they give you the heap
Not the non heap, which is currently the problem..
Yes, but they are the only thing you have if you do not use a profiler
to look at the running app.
And since the permanent
On 07/22/10 20:30, James Carman wrote:
Guys, our production server is running into an error from time to
time. I get the below stack trace after the site has been running for
a while. It's not running in development mode. It's running in
deployment mode. Any thoughts?
Are you by chance
I am not using intern() anywhere. Who knows if any of the gazillion
third-party libraries are using it, though. Time to fire up jmap
On Fri, Jul 23, 2010 at 7:24 AM, Thomas Kappler
thomas.kapp...@isb-sib.ch wrote:
On 07/22/10 20:30, James Carman wrote:
Guys, our production server is running
as far as i see now if i look that the stacktrace:
java.io.ObjectStreamClass.init(ObjectStreamClass.java:413)
java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:310
so ObjectSTreamClass.lookup call there the constructor of ObjectStreamClass
lookup does check for caches but those are
Here's an interesting error message from jvisualvm:
*** Profiler engine warning: class
sun.reflect.GeneratedConstructorAccessor1 that should be instrumented
is not loaded by target VM
*** Requested classloader: sun.reflect.delegatingclassloa...@7dc5ddc9,
its class = class
On Fri, Jul 23, 2010 at 2:12 PM, James Carman
ja...@carmanconsulting.com wrote:
Here's an interesting error message from jvisualvm:
*** Profiler engine warning: class
sun.reflect.GeneratedConstructorAccessor1 that should be instrumented
is not loaded by target VM
*** Requested classloader:
On Fri, Jul 23, 2010 at 8:20 AM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
In these kind of cases I've learnt to trust Johan.
It appears I'm learning that myself!
-
To unsubscribe, e-mail:
ahh you are already at nr 394 of those :)
Let see how for they come :)
On Fri, Jul 23, 2010 at 14:41, James Carman ja...@carmanconsulting.com wrote:
*** Profiler engine warning: class
sun.reflect.GeneratedSerializationConstructorAccessor394 that should
be instrumented is not loaded by target
I'm running Wicket 1.4.9 and Sun's JDK 1.6.0_20 on a RHEL4 64-bit machine.
On Thu, Jul 22, 2010 at 2:30 PM, James Carman
ja...@carmanconsulting.com wrote:
Guys, our production server is running into an error from time to
time. I get the below stack trace after the site has been running for
a
Where is the outofmemoryerror ?
**
Martin
2010/7/22 James Carman ja...@carmanconsulting.com:
I'm running Wicket 1.4.9 and Sun's JDK 1.6.0_20 on a RHEL4 64-bit machine.
On Thu, Jul 22, 2010 at 2:30 PM, James Carman
ja...@carmanconsulting.com wrote:
Guys, our production server is running
Oops! I must not have copied that line. All it said was PermGen space
On Thu, Jul 22, 2010 at 3:25 PM, Martin Makundi
martin.maku...@koodaripalvelut.com wrote:
Where is the outofmemoryerror ?
**
Martin
2010/7/22 James Carman ja...@carmanconsulting.com:
I'm running Wicket 1.4.9 and Sun's
You did try to change your permgen setting?
http://rimuhosting.com/knowledgebase/linux/java/-Xmx-settings
**
Martin
2010/7/22 James Carman ja...@carmanconsulting.com:
Oops! I must not have copied that line. All it said was PermGen space
On Thu, Jul 22, 2010 at 3:25 PM, Martin Makundi
Of course. It's set at 1024m! I bumped it from 256 to 512 to 1024
now. I'm still seeing the error.
On Thu, Jul 22, 2010 at 3:31 PM, Martin Makundi
martin.maku...@koodaripalvelut.com wrote:
You did try to change your permgen setting?
http://java.sun.com/javase/technologies/hotspot/gc/gc_tuning_6.html
http://java.sun.com/javase/technologies/hotspot/gc/gc_tuning_6.htmlthese
are my settings
set JAVA_OPTS=%JAVA_OPTS% -Xms512m -Xmx1024m -XX:PermSize=256m
-XX:MaxPermSize=256m
2010/7/22 James Carman [via Apache Wicket]
I'm running Tomcat, so it's:
$ env | grep CATALINA
CATALINA_OPTS= -Xmx4096m -Xms2048m -XX:MaxPermSize=1024m
-XX:+UseParallelGC -server
On Thu, Jul 22, 2010 at 3:47 PM, david_ meulemans.da...@gmail.com wrote:
http://java.sun.com/javase/technologies/hotspot/gc/gc_tuning_6.html
what kind of classes are serialized constantly?
are those proxies or other generated onces?
Somehow it has something to do with getting the default constructor of
the first none serializable class
And i think your first class in the hierarchy that is found that
doenst implement Serializable
On Thu, Jul 22, 2010 at 4:11 PM, Johan Compagner jcompag...@gmail.com wrote:
what kind of classes are serialized constantly?
are those proxies or other generated onces?
All sorts of stuff I guess. This doesn't necessarily happen on one
particular page. It just starts happening after a while
21 matches
Mail list logo
