> > - use a 1.6 JVM
Tried with Sun 1.6 JVM. Same problems. Not the same exact stack traces but for example: Thread 24427: (state = BLOCKED) - java.lang.String.toCharArray() @bci=4, line=2725 (Compiled frame) - java.beans.Introspector.decapitalize(java.lang.String) @bci=46, line=252 (Compiled frame) - org.hibernate.property.BasicPropertyAccessor.getterMethod(java.lang.Class, java.lang.String) @bci=47, line=325 (Compiled frame) - org.hibernate.property.BasicPropertyAccessor.getGetterOrNull(java.lang.Class, java.lang.String) @bci=33, line=297 (Interpreted frame) - org.hibernate.property.BasicPropertyAccessor.getGetterOrNull(java.lang.Class, java.lang.String) @bci=71, line=304 (Interpreted frame) - org.hibernate.property.BasicPropertyAccessor.setterMethod(java.lang.Class, java.lang.String) @bci=2, line=251 (Interpreted frame) - org.hibernate.property.BasicPropertyAccessor.getSetterOrNull(java.lang.Class, java.lang.String) @bci=33, line=230 (Interpreted frame) - org.hibernate.property.BasicPropertyAccessor.createSetter(java.lang.Class, java.lang.String) @bci=2, line=214 (Interpreted frame) - org.hibernate.property.BasicPropertyAccessor.getSetter(java.lang.Class, java.lang.String) @bci=2, line=209 (Interpreted frame) - org.hibernate.mapping.Property.getSetter(java.lang.Class) @bci=10, line=277 (Interpreted frame) - org.hibernate.tuple.entity.PojoEntityTuplizer.buildPropertySetter(org.hibernate.mapping.Property, - try different JVM settings, particularly GC related ones Any thoughts on which GC parameters I should change. > - switch to/from client from/to server JVM Have tried with "-server" flag. Same problems. I agree with you on JVM problem especially given that all the blocked threads are blocked in calls to the String object. Problem is I'm not doing anything exotic with the JVM. We simply did an "apt-get" to get the latest Sun JVM for Ubuntu. I've been searching their forums as well for any mention of incompatibilities with Sun's JVM. Thanks for your help so far. - Bradley On Mon, Aug 31, 2009 at 4:22 PM, Mark Thomas <ma...@apache.org> wrote: > > Bradley Wagner wrote: > > Mark, > > Sorry, I should have mentioned this before, but in all cases I tried the > > thread dumps 2-3 times at least 30s apart and none of the threads have > > progressed at all. > > Hmm. That smells like a JVM issue to me, particularly if it goes away > when you use JPDA. > > Things to try: > - use a 1.6 JVM > - try different JVM settings, particularly GC related ones > - switch to/from client from/to server JVM > > Mark > > > > > > - Bradley > > > > On Mon, Aug 31, 2009 at 3:52 PM, Mark Thomas <ma...@apache.org> wrote: > > > >> Bradley Wagner wrote: > >>> Ok, I have some information to add here. I was able to get thread dumps > >> with > >>> "jstack <pid>" (very handy!) because "kill -3" wouldn't work on a hung > >>> process. > >>> I've listed 3 consecutive tests that I run and the thread is blocked at > >> the > >>> time the process is hung. > >> That isn't the way to analyse this. It is almost impossible to detect a > >> hung thread from a single thread dump. > >> > >> For a single hang, take three thread dumps ~10s apart and then examine > >> those to see which thread(s) has(have) not progressed between dumps. > >> > >> Mark > >> > >> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > >> For additional commands, e-mail: users-h...@tomcat.apache.org > >> > >> > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org >
