We get a strange NullPointerException from time to time in method net.sf.tapestry.BaseComponent.readTemplate(). We are using Tapestry 2.1, Tomcat 4.0.6, JDK 1.4.1_01 server VM. When we execute a load test on our application (6 concurrent clients), after about 5 to 15 minutes, some local variables in method BaseComponent.readTemplate() suddenly become null. Method readTemplate loops over a list of tokens in the (HTML) template. After some iterations the local variable componentTemplate suddenly becomes null. This happens for a template that has been correctly read many times before in the test. Another effect is, that the NPE that results from this problem has no stack trace. We only found the source of this NPE with a debugger. This behaviour seems to be due to a bug in the JDK 1.4.1 server VM, because we don't get this problem when we use JDK 1.3.1_06 or when we use the VM option "-Xint" (interpreted mode) with the 1.4.1_01 VM. In the BugParade at java.sun.com, I found a reported VM bug that could be related to this problem (see http://developer.java.sun.com/developer/bugParade/bugs/4761344.html).
Did anyone of you encounter this problem as well? If yes, is there a workaround? Our current workaround is to go back to JVM 1.3.1. Regards, Martin Schnyder ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
