On Wed, 2004-07-28 at 15:38, Brent Johnson wrote:
> I'm running a production site using Tomcat 5.0.18 with Cocoon 2.1.4. 
> In the past, after some period of time (around a month or more) the
> site would start returning a blank page.
> 
> I then upped all the pool sizes in cocoon.xconf, upped the heapsize,
> and included the XML parsers in the shared tomcat common lib
> directories.
> 
> However, over the last few months.. around that same time frame of a
> month or so, instead of the site returning a blank page it just stops
> responding.  It happened again this morning.  Everything is fine,
> suddently Tomcat and/or Cocoon stops responding.  The browser just
> sits there spinning and waiting for a response from the server (dont
> get a connection refused).
> 
> A tomcat shutdown fails to kill it so I have to kill it manually with
> a kill -9 and restart.  When I look in the logs (both tomcat and
> cocoon logs) I dont see ANYTHING really fishy other than the following
> line (which happens almost every day anyways.. so I'm not sure what
> the deal is):
> 
> 2004-07-27 12:50:01 StandardWrapperValve[default]: Servlet.service()
> for servlet default threw exception
> java.lang.NullPointerException
>     at java.io.File.<init>(File.java:263)
>     at org.apache.naming.resources.FileDirContext.file(FileDirContext.java:880)
>     at 
> org.apache.naming.resources.FileDirContext.getAttributes(FileDirContext.java:487)
>     at 
> org.apache.naming.resources.BaseDirContext.getAttributes(BaseDirContext.java:797)
>     at 
> org.apache.naming.resources.ProxyDirContext.cacheLoad(ProxyDirContext.java:1491)
>     at 
> org.apache.naming.resources.ProxyDirContext.cacheLookup(ProxyDirContext.java:1412)
>     at org.apache.naming.resources.ProxyDirContext.lookup(ProxyDirContext.java:300)
>     at 
> org.apache.catalina.servlets.DefaultServlet$ResourceInfo.set(DefaultServlet.java:2267)
> 
> This happens (i think) when it tries to call Cocoon when it receives a
> virus page request to hit in IIS server.. here's the log entry prior
> to the NPE:
> 
> 2004-07-28 07:49:30 StandardContext[]:  Mapped to servlet 'default'
> with servlet path '/scripts/..\../winnt/system32/cmd.exe' and path
> info 'null' and update=true
> 
> Anyone have any ideas?  Does this look at ALL familiar to anyone? 
> I've got a government contract and some govm't employees that arent
> going to be too happy if they keep having to call me every month
> because Tomcat and/or Cocoon can't seem to stay running  :)

As you suggest yourself, I don't think the errors above have anything to
do with the blank page problem. Very often, this is caused by
OutOfMemory exceptions. You should be able to see those if you redirect
standard out (or standard error) to a file. Assuming it would be this,
there is something that's leaking memory in either your application,
Cocoon, or any of the third party libraries cocoon uses.

-- 
Bruno Dumon                             http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
[EMAIL PROTECTED]                          [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to