velocity-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geir Magnusson Jr <g...@4quarters.com>
Subject Re: AW: AW: Empty reply from server from time to time (Stacktrace attatched)
Date Fri, 09 Jan 2004 10:35:02 GMT

On Jan 9, 2004, at 3:29 AM, Hans Schmid wrote:

> Any news on this one?

Not yet.

>
> Should I move this problem to velocity-dev for further investigation?

You could.  Would most likely be the same group of people. :)

>
> Thanks,
> Hans
>
>
>> -----Ursprungliche Nachricht-----
>> Von: Hans Schmid [mailto:Hans.Schmid@einsurance.de]
>> Gesendet: Mittwoch, 7. Januar 2004 14:57
>> An: Velocity Users List
>> Betreff: AW: AW: Empty reply from server from time to time (Stacktrace
>> attatched)
>>
>>
>> Hi Geir,
>>
>> I just found another NPE in the logfile:
>>
>>
>> java.lang.NullPointerException
>>         at
>> org.apache.velocity.io.VelocityWriter.write(VelocityWriter.java:358)
>>         at
>> org.apache.velocity.runtime.parser.node.ASTReference.render(ASTRef
>> erence.jav
>> a:301)
>>         at
>> org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java: 
>> 94)
>>         at
>> org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTI
>> fStatement
>> .java:109)
>>         at
>> org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNo
>> de.java:27
>> 1)
>>         at org.apache.velocity.Template.merge(Template.java:296)
>>         at
>> org.apache.velocity.servlet.VelocityServlet.mergeTemplate(Velocity
>> Servlet.ja
>> va:448)
>>         at
>> org.apache.velocity.servlet.VelocityServlet.doRequest(VelocityServ
>> let.java:3
>> 87)
>>         at
>> org.apache.velocity.servlet.VelocityServlet.doPost(VelocityServlet
>> .java:342)
>>         at javax.servlet.http.HttpServlet.service(HttpServlet.java)
>>         at javax.servlet.http.HttpServlet.service(HttpServlet.java)
>>         at
>> org.apache.tomcat.facade.ServletHandler.doService(ServletHandler.java: 
>> 574)
>>         at org.apache.tomcat.core.Handler.invoke(Handler.java:322)
>>         at org.apache.tomcat.core.Handler.service(Handler.java:235)
>>         at
>> org.apache.tomcat.facade.ServletHandler.service(ServletHandler.java: 
>> 485)
>>         at
>> org.apache.tomcat.facade.RequestDispatcherImpl.doForward(RequestDi
>> spatcherIm
>> pl.java:272)
>>         at
>> org.apache.tomcat.facade.RequestDispatcherImpl.forward(RequestDisp
>> atcherImpl
>> .java:174)
>>         at
>> org.apache.struts.action.ActionServlet.processActionForward(Action
>> Servlet.ja
>> va:1759)
>>         at
>> org.apache.struts.action.ActionServlet.process(ActionServlet.java: 
>> 1596)
>>         at
>> de.einsurance.gui.framework.ExtendedActionServlet.process(Extended
>> ActionServ
>> let.java:64)
>>         at
>> org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
>>         at javax.servlet.http.HttpServlet.service(HttpServlet.java)
>>         at javax.servlet.http.HttpServlet.service(HttpServlet.java)
>>         at
>> org.apache.tomcat.facade.ServletHandler.doService(ServletHandler.java: 
>> 574)
>>         at org.apache.tomcat.core.Handler.invoke(Handler.java:322)
>>         at org.apache.tomcat.core.Handler.service(Handler.java:235)
>>         at
>> org.apache.tomcat.facade.ServletHandler.service(ServletHandler.java: 
>> 485)
>>         at
>> org.apache.tomcat.facade.RequestDispatcherImpl.doForward(RequestDi
>> spatcherIm
>> pl.java:272)
>>         at
>> org.apache.tomcat.facade.RequestDispatcherImpl.forward(RequestDisp
>> atcherImpl
>> .java:174)
>>         at
>> org.apache.struts.action.ActionServlet.processActionForward(Action
>> Servlet.ja
>> va:1759)
>>         at
>> org.apache.struts.action.ActionServlet.process(ActionServlet.java: 
>> 1596)
>>         at
>> de.einsurance.gui.framework.ExtendedActionServlet.process(Extended
>> ActionServ
>> let.java:64)
>>         at
>> org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
>>         at javax.servlet.http.HttpServlet.service(HttpServlet.java)
>>         at javax.servlet.http.HttpServlet.service(HttpServlet.java)
>>         at
>> org.apache.tomcat.facade.ServletHandler.doService(ServletHandler.java: 
>> 574)
>>         at org.apache.tomcat.core.Handler.invoke(Handler.java:322)
>>         at org.apache.tomcat.core.Handler.service(Handler.java:235)
>>         at
>> org.apache.tomcat.facade.ServletHandler.service(ServletHandler.java: 
>> 485)
>>         at
>> org.apache.tomcat.core.ContextManager.internalService(ContextManag
>> er.java:91
>> 7)
>>         at
>> org.apache.tomcat.core.ContextManager.service(ContextManager.java:833)
>>         at
>> org.apache.tomcat.modules.server.Http10Interceptor.processConnecti
>> on(Http10I
>> nterceptor.java:176)
>>         at
>> org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java: 
>> 494)
>>         at
>> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(Thre
>> adPool.jav
>> a:516)
>>         at java.lang.Thread.run(Thread.java:534)
>>
>> perhaps related/perhaps not ...
>>
>> Thanks for looking into this,
>> Hans
>>
>>> -----Ursprungliche Nachricht-----
>>> Von: Geir Magnusson Jr [mailto:geir@4quarters.com]
>>> Gesendet: Mittwoch, 7. Januar 2004 13:30
>>> An: Velocity Users List
>>> Betreff: Re: AW: Empty reply from server from time to time  
>>> (Stacktrace
>>> attatched)
>>>
>>>
>>> I can't see how it's your code.  I've been trying to imagine a way it
>>> could be, but I can't see it.  I'll keep staring.  Thanks for the  
>>> info.
>>>
>>> geir
>>>
>>> On Jan 7, 2004, at 6:50 AM, Hans Schmid wrote:
>>>
>>>> Hi Geir,
>>>>
>>>> thanks for your reply.
>>>>
>>>> First let me note, that I now can reproduce this stacktrace with a
>>>> loadtesting tool
>>>> on a test server :)
>>>>
>>>> No other errors occur in the logfile. The templates get loaded from
>>>> the file
>>>> system.
>>>> Since we use an inhereted version of the VelocityServlet I am  
>>>> digging
>>>> now in
>>>> our code
>>>> (written by a contractor which is already gone ...)
>>>> We are doing some portlet kind of stuff in there as well as
>>>> integrating with
>>>> struts workflow component.
>>>>
>>>> Any ideas would be welcome where to put debugging statements in
>>>> Velocity to
>>>> get more information than this stacktrace.
>>>>
>>>> Thanks,
>>>> Hans
>>>>
>>>>
>>>>> -----Ursprungliche Nachricht-----
>>>>> Von: Geir Magnusson Jr [mailto:geir@4quarters.com]
>>>>> Gesendet: Dienstag, 6. Januar 2004 13:24
>>>>> An: Velocity Users List
>>>>> Betreff: Re: Empty reply from server from time to time (Stacktrace
>>>>> attatched)
>>>>>
>>>>>
>>>>>
>>>>> On Jan 5, 2004, at 8:46 AM, Hans Schmid wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> we are running a high traffic production page (+400
>> concurrent users)
>>>>>> at high times. Our external monitoring system (PHP based) shows an
>>>>>> emty page
>>>>>> displayed
>>>>>> from time to time (est. 2 times out of 180 a day all doing exactly
>>>>>> the
>>>>>> same):
>>>>>
>>>>> [SNIP]
>>>>>
>>>>> This is worrysome.  Are there any other errors in the log?  Where  
>>>>> do
>>>>> templates come from?
>>>>>
>>>>>
>>>>> --
>>>>> Geir Magnusson Jr                                   203-247-1713(m)
>>>>> geir@4quarters.com
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------- 
>>>>> --
>>>>> To unsubscribe, e-mail:  
>>>>> velocity-user-unsubscribe@jakarta.apache.org
>>>>> For additional commands, e-mail:
>> velocity-user-help@jakarta.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------- 
>>>> -
>>>> To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
>>>> For additional commands, e-mail:  
>>>> velocity-user-help@jakarta.apache.org
>>>>
>>>>
>>> --
>>> Geir Magnusson Jr                                   203-247-1713(m)
>>> geir@4quarters.com
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail:  
>>> velocity-user-help@jakarta.apache.org
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: velocity-user-help@jakarta.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: velocity-user-help@jakarta.apache.org
>
>
-- 
Geir Magnusson Jr                                   203-247-1713(m)
geir@4quarters.com


---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-user-help@jakarta.apache.org


Mime
View raw message