Seems no body has any comments on this...oh well :-( I tested in the same conditions an older version of Webwork2 (from CVS, before beta2) and this Exception doesn't happen at all. So I checked what was the difference, and I found out that in that old VelocityResult (that doesn't throw this Exception) it's not used the javax.servlet.jsp.PageContext to merge the template (this is a change introduced in version 1.3 by Patrick), and it just writes it directly to response.getWriter(). So, why is this being thrown when using the ...jsp.PageContext. I assume that it probably depends on the JSP engine used. Has anybody tested this new VelocityResult under high concurrency conditions when using JASPER (which I believe is provided with TOMCAT & JETTY) ? Very curious about this one, since it IS a problem I want to eliminate. Thanks for any feedback at all..
On Friday 16 January 2004 19:49, Fernando Martins wrote: > hi, > I wanted to test my app (using Xwork/Webwork2 from CVS) under extreme load > conditions. So I hit the server (Jetty) with a few concurrent clients > (grinder3.0) and from time to time I get this Exception, which I never got > before when testing single requests (see below). > > And why is it calling something Jasper/JSP related if I'm not using any > kind of JSP and only Velocity? > I understand that for velocity tags to work in JSP you might need some > integration, but If I don't want to use any JSP related stuff, should I be > forced to go throught Jsp Writers and all that? > Maybe that's why Webwork1.x is faster that ww2.... !? > > 18:36:01,243 ERROR ServletDispatcher:187 - Could not execute action > java.lang.NullPointerException > at > org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:375) > at > org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.ja >va:321) at > org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:94) > at > org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatemen >t.java:109) at > org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:94) > at > org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:344) > at > org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.ja >va:153) at > org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:2 >71) at org.apache.velocity.Template.merge(Template.java:296) > at > com.opensymphony.webwork.dispatcher.VelocityResult.doExecute(VelocityResult >.java:89) at > com.opensymphony.webwork.dispatcher.WebWorkResultSupport.execute(WebWorkRes >ultSupport.java:53) at > com.opensymphony.xwork.DefaultActionInvocation.executeResult(DefaultActionI >nvocation.java:274) at > com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocati >on.java:192) at > com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterc >eptor.java:37) at > com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocati >on.java:170) at > com.opensymphony.xwork.DefaultActionProxy.execute(DefaultActionProxy.java:1 >16) at > com.opensymphony.webwork.dispatcher.ServletDispatcher.serviceAction(Servlet >Dispatcher.java:182) at > com.opensymphony.webwork.dispatcher.ServletDispatcher.service(ServletDispat >cher.java:162) > > On Friday 16 January 2004 16:30, Mark Woon wrote: > > In XWorks, what exactly is the role of the ActionContext? Does it sort > > of map to a ServletRequest in the sense that it is supposed to hold all > > the data necessary to process an Action and there will be one for each > > request? > > > > I'm asking because I'm trying to figure out where to store objects that > > can be used by Interceptors and Actions but don't exactly belong in an > > Action (e.g. a Connection to a database). > > > > Thanks, > > -Mark > > > > > > > > ------------------------------------------------------- > > The SF.Net email is sponsored by EclipseCon 2004 > > Premiere Conference on Open Tools Development and Integration > > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > > http://www.eclipsecon.org/osdn > > _______________________________________________ > > Opensymphony-webwork mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
