On Mon, 6 Dec 2004 11:44:28 -0800, Mike Dickson <[EMAIL PROTECTED]> wrote: > Could it be a memory leak? It sounds like it.
That was my initial thought. The site uses XSP (no flow). I'm thinking about redeveloping the site using Flowscript and JXTemplates instead of XSP. But since its production I hate to mess with it too much. I did check the memory for the processes using the "ps" command (and "top").. but I dunno if that would really indicate a memory leak. The tomcat process is still running and it appears to not be taking up any real large amount of memory (if I recall correctly.. I dont think its taking up any more when its failing than when its freshly started). I'll check into it though.. oh.. one more thing.. the site doesnt get a lot of usage so its pretty much idle most of the time. But even idle, it still takes about the same time (a month) for it to stop responding. On Mon, 6 Dec 2004 20:47:11 +0100, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote: > Le 6 d�c. 04, � 20:35, Brent Johnson a �crit : > > I'd start with by getting and analyzing a thread dump from the JVM. > > There's some info at > http://www.unixville.com/~moazam/stories/2004/05/18/ > debuggingHangsInTheJvm.html for example, it's for Solaris but you can > certainly find similar info for your platform. Thanks - I'll definitely give this a try when the process hangs again. Hopefully that will give me a better idea of whats going on. It just drives me crazy when something fails (esp. in production) but doesnt tell me why its failing. Thanks, - Brent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
