Re: OutOfMemoryError PermGen Space...
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: http://apache-wicket.1842946.n4.nabble.com/OutOfMemoryError-PermGen-Space-tp2299132p3066250.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: OutOfMemoryError PermGen Space...
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 sounds like a memory leak. Tuning the java garbage collection will in all cases not help here, because java only throws an out of memory error if garbage collection does not help any more. I would enable the following for tomcat: -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/java/whatever Then you can analyse what holds all the memory after the next crash. A nice tool for that is the Eclipse Memory Analyzer: http://www.eclipse.org/mat/ A little how to for getting started: http://wiki.eclipse.org/index.php/MemoryAnalyzer And you should search what they have at the tomcat pages and on their mailing list archives: http://wiki.apache.org/tomcat/OutOfMemory This is most likely not specific to wicket itself. Andreas 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 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] ml-node+2299232-642663496-232...@n4.nabble.comml-node%2b2299232-642663496-232...@n4.nabble.com 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 [hidden email] http://user/SendEmail.jtp?type=nodenode=2299232i=0 wrote: You did try to change your permgen setting? http://rimuhosting.com/knowledgebase/linux/java/-Xmx-settings ** Martin 2010/7/22 James Carman [hidden email]http://user/SendEmail.jtp?type=nodenode=2299232i=1: 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 [hidden email] http://user/SendEmail.jtp?type=nodenode=2299232i=2 wrote: Where is the outofmemoryerror ? ** Martin 2010/7/22 James Carman [hidden email]http://user/SendEmail.jtp?type=nodenode=2299232i=3: 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 [hidden email]http://user/SendEmail.jtp?type=nodenode=2299232i=4 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? What's with this generateSerializationConstructor() stuff? - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: OutOfMemoryError PermGen Space...
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 only thing you do is serializing these kind of objects:
// not serializeable and doesnt have a default constructor
public class A {
String name;
// add this constructor so the compiler doesnt generate a default one.
public A(String name) {
this.name = name;
}
}
public class B extends A implements Serializable {
int aNumber;
public B() {
super(B);
aNumber = 10;
}
}
If you then serialize instances of B then i think you will come into
the section of the stacktrace James gave.
But this shouldnt really leak into the none heap. (and result in an
never ending grow) that would just a bug in java itself if you ask me.
i think the work around is to give the A class a private constructor:
private A() {}
Then i think nothing is tried to be generated.
2010/7/23 Andreas Prieß a...@metaphysis.net:
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 sounds like a memory leak.
Tuning the java garbage collection will in all cases not help here,
because java only throws an out of memory error if garbage collection
does not help any more.
I would enable the following for tomcat:
-XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=/var/log/java/whatever
Then you can analyse what holds all the memory after the next crash.
A nice tool for that is the Eclipse Memory Analyzer:
http://www.eclipse.org/mat/
A little how to for getting started:
http://wiki.eclipse.org/index.php/MemoryAnalyzer
And you should search what they have at the tomcat pages and on their
mailing list archives:
http://wiki.apache.org/tomcat/OutOfMemory
This is most likely not specific to wicket itself.
Andreas
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
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]
ml-node+2299232-642663496-232...@n4.nabble.comml-node%2b2299232-642663496-232...@n4.nabble.com
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
[hidden email] http://user/SendEmail.jtp?type=nodenode=2299232i=0
wrote:
You did try to change your permgen setting?
http://rimuhosting.com/knowledgebase/linux/java/-Xmx-settings
**
Martin
2010/7/22 James Carman [hidden
email]http://user/SendEmail.jtp?type=nodenode=2299232i=1:
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
[hidden email] http://user/SendEmail.jtp?type=nodenode=2299232i=2
wrote:
Where is the outofmemoryerror ?
**
Martin
2010/7/22 James Carman [hidden
email]http://user/SendEmail.jtp?type=nodenode=2299232i=3:
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
[hidden email]http://user/SendEmail.jtp?type=nodenode=2299232i=4
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? What's with this
generateSerializationConstructor() stuff?
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: OutOfMemoryError PermGen Space...
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 lookup() method to find them. Or, could I somehow
be leaking classes (hibernate-generated subclasses of my entities,
proxy classes generated by wicket-spring, etc.)? That's going to be
harder to track down.
On Fri, Jul 23, 2010 at 4:19 AM, Johan Compagner jcompag...@gmail.com wrote:
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 only thing you do is serializing these kind of objects:
// not serializeable and doesnt have a default constructor
public class A {
String name;
// add this constructor so the compiler doesnt generate a default one.
public A(String name) {
this.name = name;
}
}
public class B extends A implements Serializable {
int aNumber;
public B() {
super(B);
aNumber = 10;
}
}
If you then serialize instances of B then i think you will come into
the section of the stacktrace James gave.
But this shouldnt really leak into the none heap. (and result in an
never ending grow) that would just a bug in java itself if you ask me.
i think the work around is to give the A class a private constructor:
private A() {}
Then i think nothing is tried to be generated.
2010/7/23 Andreas Prieß a...@metaphysis.net:
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 sounds like a memory leak.
Tuning the java garbage collection will in all cases not help here,
because java only throws an out of memory error if garbage collection
does not help any more.
I would enable the following for tomcat:
-XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=/var/log/java/whatever
Then you can analyse what holds all the memory after the next crash.
A nice tool for that is the Eclipse Memory Analyzer:
http://www.eclipse.org/mat/
A little how to for getting started:
http://wiki.eclipse.org/index.php/MemoryAnalyzer
And you should search what they have at the tomcat pages and on their
mailing list archives:
http://wiki.apache.org/tomcat/OutOfMemory
This is most likely not specific to wicket itself.
Andreas
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
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]
ml-node+2299232-642663496-232...@n4.nabble.comml-node%2b2299232-642663496-232...@n4.nabble.com
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
[hidden email] http://user/SendEmail.jtp?type=nodenode=2299232i=0
wrote:
You did try to change your permgen setting?
http://rimuhosting.com/knowledgebase/linux/java/-Xmx-settings
**
Martin
2010/7/22 James Carman [hidden
email]http://user/SendEmail.jtp?type=nodenode=2299232i=1:
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
[hidden email] http://user/SendEmail.jtp?type=nodenode=2299232i=2
wrote:
Where is the outofmemoryerror ?
**
Martin
2010/7/22 James Carman [hidden
email]http://user/SendEmail.jtp?type=nodenode=2299232i=3:
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
[hidden email]http://user/SendEmail.jtp?type=nodenode=2299232i=4
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? What's with this
generateSerializationConstructor() stuff?
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: OutOfMemoryError PermGen Space...
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 generation does not grow on it's own without any
link to the heap, you can find the reason for the problem this way with
a little luck.
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)
It can be a problem in any library that you use and that are generally
quite many these days...
I had similar problems with database drivers and object mapping libs,
but you are right, in this case the problem normally arises with
redeployments of the app without restart of the container.
http://dev.eclipse.org/blogs/memoryanalyzer/2008/05/17/the-unknown-generation-perm/
but the only thing you do is serializing these kind of objects:
You may be right with your analysis of the serialization, I just want to
note here that in case of an out of memory error the stack trace can be
completely irrelevant. It just shows at what step the memory was full,
but that step does not have to be the cause for the memory filling up.
// not serializeable and doesnt have a default constructor
public class A {
String name;
// add this constructor so the compiler doesnt generate a default one.
public A(String name) {
this.name = name;
}
}
public class B extends A implements Serializable {
int aNumber;
public B() {
super(B);
aNumber = 10;
}
}
If you then serialize instances of B then i think you will come into
the section of the stacktrace James gave.
But this shouldnt really leak into the none heap. (and result in an
never ending grow) that would just a bug in java itself if you ask me.
i think the work around is to give the A class a private constructor:
private A() {}
Then i think nothing is tried to be generated.
2010/7/23 Andreas Prieß a...@metaphysis.net:
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 sounds like a memory leak.
Tuning the java garbage collection will in all cases not help here,
because java only throws an out of memory error if garbage collection
does not help any more.
I would enable the following for tomcat:
-XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=/var/log/java/whatever
Then you can analyse what holds all the memory after the next crash.
A nice tool for that is the Eclipse Memory Analyzer:
http://www.eclipse.org/mat/
A little how to for getting started:
http://wiki.eclipse.org/index.php/MemoryAnalyzer
And you should search what they have at the tomcat pages and on their
mailing list archives:
http://wiki.apache.org/tomcat/OutOfMemory
This is most likely not specific to wicket itself.
Andreas
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: OutOfMemoryError PermGen Space...
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 using String.intern()? That is a candidate for filling up the PermGen space. As Andreas noted, the stack trace can be completely irrelevant to the reason for running out of memory. -- Thomas -- --- Thomas Kapplerthomas.kapp...@isb-sib.ch Swiss Institute of Bioinformatics Tel: +41 22 379 51 89 CMU, rue Michel Servet 1 1211 Geneve 4 Switzerland http://www.uniprot.org --- - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: OutOfMemoryError PermGen Space...
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 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 using String.intern()? That is a candidate for filling up the PermGen space. As Andreas noted, the stack trace can be completely irrelevant to the reason for running out of memory. -- Thomas -- --- Thomas Kappler thomas.kapp...@isb-sib.ch Swiss Institute of Bioinformatics Tel: +41 22 379 51 89 CMU, rue Michel Servet 1 1211 Geneve 4 Switzerland http://www.uniprot.org --- - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: OutOfMemoryError PermGen Space...
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 soft caches so these can be cleared. It can mean 2 things, or somehow you have constantly different classes (proxies or cglib generated other stuff?) or the softcaches are cleared quite often they kind of do that quite often, SoftReferences are NOT only cleared when the jvm needs more mem but also much sooner! You can set this system property: -XX:SoftRefLRUPolicyMSPerMB=360 that will result in a much longer live softreference... Because there is constantly a ObjectStreamClass generated i think you are then hitting the MethodAccessorGenerator: private MagicAccessorImpl generate(final Class declaringClass, String name, Class[] parameterTypes, Class returnType, Class[] checkedExceptions, int modifiers, boolean isConstructor, boolean forSerialization, Class serializationTargetClass) and that is constructing byte code on the fly and calling defineClass on it which results in a new class all the time that is a implementation of MagicAccessorImpl that then is a fake constructor for your first none serializable class (that didnt have one on its own) On Fri, Jul 23, 2010 at 13:26, James Carman ja...@carmanconsulting.com wrote: 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 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 using String.intern()? That is a candidate for filling up the PermGen space. As Andreas noted, the stack trace can be completely irrelevant to the reason for running out of memory. -- Thomas -- --- Thomas Kappler thomas.kapp...@isb-sib.ch Swiss Institute of Bioinformatics Tel: +41 22 379 51 89 CMU, rue Michel Servet 1 1211 Geneve 4 Switzerland http://www.uniprot.org --- - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: OutOfMemoryError PermGen Space...
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 sun.reflect.DelegatingClassLoader, index = 542, hashcode = 2110119369 *** Profiler engine warning: target VM cannot load class to instrument sun.reflect.GeneratedConstructorAccessor1 *** probably it has been unloaded recently Sounds like we're on the right track, perhaps? On Fri, Jul 23, 2010 at 7:54 AM, Johan Compagner jcompag...@gmail.com wrote: 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 soft caches so these can be cleared. It can mean 2 things, or somehow you have constantly different classes (proxies or cglib generated other stuff?) or the softcaches are cleared quite often they kind of do that quite often, SoftReferences are NOT only cleared when the jvm needs more mem but also much sooner! You can set this system property: -XX:SoftRefLRUPolicyMSPerMB=360 that will result in a much longer live softreference... Because there is constantly a ObjectStreamClass generated i think you are then hitting the MethodAccessorGenerator: private MagicAccessorImpl generate(final Class declaringClass, String name, Class[] parameterTypes, Class returnType, Class[] checkedExceptions, int modifiers, boolean isConstructor, boolean forSerialization, Class serializationTargetClass) and that is constructing byte code on the fly and calling defineClass on it which results in a new class all the time that is a implementation of MagicAccessorImpl that then is a fake constructor for your first none serializable class (that didnt have one on its own) On Fri, Jul 23, 2010 at 13:26, James Carman ja...@carmanconsulting.com wrote: 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 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 using String.intern()? That is a candidate for filling up the PermGen space. As Andreas noted, the stack trace can be completely irrelevant to the reason for running out of memory. -- Thomas -- --- Thomas Kappler thomas.kapp...@isb-sib.ch Swiss Institute of Bioinformatics Tel: +41 22 379 51 89 CMU, rue Michel Servet 1 1211 Geneve 4 Switzerland http://www.uniprot.org --- - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: OutOfMemoryError PermGen Space...
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: sun.reflect.delegatingclassloa...@7dc5ddc9, its class = class sun.reflect.DelegatingClassLoader, index = 542, hashcode = 2110119369 *** Profiler engine warning: target VM cannot load class to instrument sun.reflect.GeneratedConstructorAccessor1 *** probably it has been unloaded recently Sounds like we're on the right track, perhaps? In these kind of cases I've learnt to trust Johan. Martijn - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: OutOfMemoryError PermGen Space...
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: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: OutOfMemoryError PermGen Space...
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 VM *** Requested classloader: sun.reflect.delegatingclassloa...@51159ff2, its class = class sun.reflect.DelegatingClassLoader, index = 582, hashcode = 1360371698 *** Profiler engine warning: target VM cannot load class to instrument sun.reflect.GeneratedSerializationConstructorAccessor394 *** probably it has been unloaded recently On Fri, Jul 23, 2010 at 8:40 AM, James Carman ja...@carmanconsulting.com wrote: On Fri, Jul 23, 2010 at 8:37 AM, Johan Compagner jcompag...@gmail.com wrote: the only thing i dont get is that for you the forSerialization flag should be true (at least the stack trace you shown us) So for your serialization thing you should have: GeneratedSerializationConstructorAccessor1 or something.. I have those too! :) - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: OutOfMemoryError PermGen Space...
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 while. It's not running in development mode. It's running in deployment mode. Any thoughts? What's with this generateSerializationConstructor() stuff? sun.misc.Unsafe.defineClass(Native Method) sun.reflect.ClassDefiner.defineClass(ClassDefiner.java:45) sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:381) java.security.AccessController.doPrivileged(Native Method) sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:377) sun.reflect.MethodAccessorGenerator.generateSerializationConstructor(MethodAccessorGenerator.java:95) sun.reflect.ReflectionFactory.newConstructorForSerialization(ReflectionFactory.java:313) java.io.ObjectStreamClass.getSerializableConstructor(ObjectStreamClass.java:1327) java.io.ObjectStreamClass.access$1500(ObjectStreamClass.java:52) java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:437) java.security.AccessController.doPrivileged(Native Method) java.io.ObjectStreamClass.init(ObjectStreamClass.java:413) java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:310) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1106) java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:416) org.apache.wicket.Component.writeObject(Component.java:4438) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461) java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1338) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1146) java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: OutOfMemoryError PermGen Space...
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 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? What's with this generateSerializationConstructor() stuff? sun.misc.Unsafe.defineClass(Native Method) sun.reflect.ClassDefiner.defineClass(ClassDefiner.java:45) sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:381) java.security.AccessController.doPrivileged(Native Method) sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:377) sun.reflect.MethodAccessorGenerator.generateSerializationConstructor(MethodAccessorGenerator.java:95) sun.reflect.ReflectionFactory.newConstructorForSerialization(ReflectionFactory.java:313) java.io.ObjectStreamClass.getSerializableConstructor(ObjectStreamClass.java:1327) java.io.ObjectStreamClass.access$1500(ObjectStreamClass.java:52) java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:437) java.security.AccessController.doPrivileged(Native Method) java.io.ObjectStreamClass.init(ObjectStreamClass.java:413) java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:310) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1106) java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:416) org.apache.wicket.Component.writeObject(Component.java:4438) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461) java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1338) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1146) java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: OutOfMemoryError PermGen Space...
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 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 while. It's not running in development mode. It's running in deployment mode. Any thoughts? What's with this generateSerializationConstructor() stuff? sun.misc.Unsafe.defineClass(Native Method) sun.reflect.ClassDefiner.defineClass(ClassDefiner.java:45) sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:381) java.security.AccessController.doPrivileged(Native Method) sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:377) sun.reflect.MethodAccessorGenerator.generateSerializationConstructor(MethodAccessorGenerator.java:95) sun.reflect.ReflectionFactory.newConstructorForSerialization(ReflectionFactory.java:313) java.io.ObjectStreamClass.getSerializableConstructor(ObjectStreamClass.java:1327) java.io.ObjectStreamClass.access$1500(ObjectStreamClass.java:52) java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:437) java.security.AccessController.doPrivileged(Native Method) java.io.ObjectStreamClass.init(ObjectStreamClass.java:413) java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:310) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1106) java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:416) org.apache.wicket.Component.writeObject(Component.java:4438) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461) java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1338) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1146) java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: OutOfMemoryError PermGen Space...
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 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 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 while. It's not running in development mode. It's running in deployment mode. Any thoughts? What's with this generateSerializationConstructor() stuff? sun.misc.Unsafe.defineClass(Native Method) sun.reflect.ClassDefiner.defineClass(ClassDefiner.java:45) sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:381) java.security.AccessController.doPrivileged(Native Method) sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:377) sun.reflect.MethodAccessorGenerator.generateSerializationConstructor(MethodAccessorGenerator.java:95) sun.reflect.ReflectionFactory.newConstructorForSerialization(ReflectionFactory.java:313) java.io.ObjectStreamClass.getSerializableConstructor(ObjectStreamClass.java:1327) java.io.ObjectStreamClass.access$1500(ObjectStreamClass.java:52) java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:437) java.security.AccessController.doPrivileged(Native Method) java.io.ObjectStreamClass.init(ObjectStreamClass.java:413) java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:310) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1106) java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:416) org.apache.wicket.Component.writeObject(Component.java:4438) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461) java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1338) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1146) java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: OutOfMemoryError PermGen Space...
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://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 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 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 while. It's not running in development mode. It's running in deployment mode. Any thoughts? What's with this generateSerializationConstructor() stuff? sun.misc.Unsafe.defineClass(Native Method) sun.reflect.ClassDefiner.defineClass(ClassDefiner.java:45) sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:381) java.security.AccessController.doPrivileged(Native Method) sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:377) sun.reflect.MethodAccessorGenerator.generateSerializationConstructor(MethodAccessorGenerator.java:95) sun.reflect.ReflectionFactory.newConstructorForSerialization(ReflectionFactory.java:313) java.io.ObjectStreamClass.getSerializableConstructor(ObjectStreamClass.java:1327) java.io.ObjectStreamClass.access$1500(ObjectStreamClass.java:52) java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:437) java.security.AccessController.doPrivileged(Native Method) java.io.ObjectStreamClass.init(ObjectStreamClass.java:413) java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:310) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1106) java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:416) org.apache.wicket.Component.writeObject(Component.java:4438) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461) java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1338) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1146) java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: OutOfMemoryError PermGen Space...
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] ml-node+2299232-642663496-232...@n4.nabble.comml-node%2b2299232-642663496-232...@n4.nabble.com 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 [hidden email] http://user/SendEmail.jtp?type=nodenode=2299232i=0 wrote: You did try to change your permgen setting? http://rimuhosting.com/knowledgebase/linux/java/-Xmx-settings ** Martin 2010/7/22 James Carman [hidden email]http://user/SendEmail.jtp?type=nodenode=2299232i=1: 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 [hidden email] http://user/SendEmail.jtp?type=nodenode=2299232i=2 wrote: Where is the outofmemoryerror ? ** Martin 2010/7/22 James Carman [hidden email]http://user/SendEmail.jtp?type=nodenode=2299232i=3: 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 [hidden email]http://user/SendEmail.jtp?type=nodenode=2299232i=4 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? What's with this generateSerializationConstructor() stuff? sun.misc.Unsafe.defineClass(Native Method) sun.reflect.ClassDefiner.defineClass(ClassDefiner.java:45) sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:381) java.security.AccessController.doPrivileged(Native Method) sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:377) sun.reflect.MethodAccessorGenerator.generateSerializationConstructor(MethodAccessorGenerator.java:95) sun.reflect.ReflectionFactory.newConstructorForSerialization(ReflectionFactory.java:313) java.io.ObjectStreamClass.getSerializableConstructor(ObjectStreamClass.java:1327) java.io.ObjectStreamClass.access$1500(ObjectStreamClass.java:52) java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:437) java.security.AccessController.doPrivileged(Native Method) java.io.ObjectStreamClass.init(ObjectStreamClass.java:413) java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:310) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1106) java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:416) org.apache.wicket.Component.writeObject(Component.java:4438) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461) java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1338) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1146) java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) - To unsubscribe, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=2299232i=5 For additional commands, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=2299232i=6 - To unsubscribe, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=2299232i=7 For additional commands, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=2299232i=8 - To unsubscribe, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=2299232i=9 For additional commands, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=2299232i=10
Re: OutOfMemoryError PermGen Space...
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 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] ml-node+2299232-642663496-232...@n4.nabble.comml-node%2b2299232-642663496-232...@n4.nabble.com 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 [hidden email] http://user/SendEmail.jtp?type=nodenode=2299232i=0 wrote: You did try to change your permgen setting? http://rimuhosting.com/knowledgebase/linux/java/-Xmx-settings ** Martin 2010/7/22 James Carman [hidden email]http://user/SendEmail.jtp?type=nodenode=2299232i=1: 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 [hidden email] http://user/SendEmail.jtp?type=nodenode=2299232i=2 wrote: Where is the outofmemoryerror ? ** Martin 2010/7/22 James Carman [hidden email]http://user/SendEmail.jtp?type=nodenode=2299232i=3: 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 [hidden email]http://user/SendEmail.jtp?type=nodenode=2299232i=4 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? What's with this generateSerializationConstructor() stuff? sun.misc.Unsafe.defineClass(Native Method) sun.reflect.ClassDefiner.defineClass(ClassDefiner.java:45) sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:381) java.security.AccessController.doPrivileged(Native Method) sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:377) sun.reflect.MethodAccessorGenerator.generateSerializationConstructor(MethodAccessorGenerator.java:95) sun.reflect.ReflectionFactory.newConstructorForSerialization(ReflectionFactory.java:313) java.io.ObjectStreamClass.getSerializableConstructor(ObjectStreamClass.java:1327) java.io.ObjectStreamClass.access$1500(ObjectStreamClass.java:52) java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:437) java.security.AccessController.doPrivileged(Native Method) java.io.ObjectStreamClass.init(ObjectStreamClass.java:413) java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:310) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1106) java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:416) org.apache.wicket.Component.writeObject(Component.java:4438) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461) java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1338) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1146) java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) - To unsubscribe, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=2299232i=5 For additional commands, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=2299232i=6 - To unsubscribe, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=2299232i=7 For additional commands, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=2299232i=8 - To unsubscribe, e-mail:
Re: OutOfMemoryError PermGen Space...
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 doesnt also have a default constructor Then when that state is found it will generate a constructor method or something (so some kind of quick asm wrapper class with that constructor) So look at the classes that you serialize, find the first one that is none serializeble and give it a default constructor. (it could be that that default constructor needs to be private) johan On Thu, Jul 22, 2010 at 20:30, 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 while. It's not running in development mode. It's running in deployment mode. Any thoughts? What's with this generateSerializationConstructor() stuff? sun.misc.Unsafe.defineClass(Native Method) sun.reflect.ClassDefiner.defineClass(ClassDefiner.java:45) sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:381) java.security.AccessController.doPrivileged(Native Method) sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:377) sun.reflect.MethodAccessorGenerator.generateSerializationConstructor(MethodAccessorGenerator.java:95) sun.reflect.ReflectionFactory.newConstructorForSerialization(ReflectionFactory.java:313) java.io.ObjectStreamClass.getSerializableConstructor(ObjectStreamClass.java:1327) java.io.ObjectStreamClass.access$1500(ObjectStreamClass.java:52) java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:437) java.security.AccessController.doPrivileged(Native Method) java.io.ObjectStreamClass.init(ObjectStreamClass.java:413) java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:310) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1106) java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:416) org.apache.wicket.Component.writeObject(Component.java:4438) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461) java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1338) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1146) java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: OutOfMemoryError PermGen Space...
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 and the application just starts throwing these stack traces. 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 doesnt also have a default constructor Then when that state is found it will generate a constructor method or something (so some kind of quick asm wrapper class with that constructor) So look at the classes that you serialize, find the first one that is none serializeble and give it a default constructor. (it could be that that default constructor needs to be private) Man, where to begin. I'm going to look at my IDE to see if it has a code inspection for this! :) - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
