- I am running the tomcat using 'nohup' (UNIX command) on Solaris. My
OutOfMemory errors were logged in nohup.log
- Also, I remember seeing that NullPointer error when the old Tomcat didn't
shutdown properly. I manually killed the old hanging java process using
'kill -9' and the new one is all set (no errors).
Hope this helps,
-Sri
At 10:20 AM 05/21/2001 -0700, Hunter Hillegas wrote:
>Which log file would I look in?
>
>servlet.log shows nothing, neither does jasper.log...
>
>Hunter
>
>> From: Srinadh Karumuri <[EMAIL PROTECTED]>
>> Reply-To: [EMAIL PROTECTED]
>> Date: Mon, 21 May 2001 12:03:45 -0400
>> To: [EMAIL PROTECTED], Tomcat User List
>> <[EMAIL PROTECTED]>
>> Subject: Re: 3.2.1 Dies
>>
>> Did you check the log files?
>> This sounds like a OutOfMemoryError.
>>
>> You can increase the heap size while starting the tomcat.
>>
>> -Sri
>>
>> At 08:16 AM 05/21/2001 -0700, Hunter Hillegas wrote:
>>> I am running a high traffic site with Tomcat 3.2.1/Sun JVM 1.3/Linux
>>> 2.4.4/Apache 1.3.19. After a few days of serving up the hits very well,
>>> Tomcat just dies. It won't respond to shutdown requests and stops serving
>>> pages, giving out only null pointer exceptions. Killing the java processes
>>> manually and restarting Tomcat clears it up.
>>>
>>> Anyone else seen this? Any idea how to work around it?
>>>
>>> Hunter
>
________________________________________________________
Srinadh Karumuri
Senior Programmer/Analyst
Business Apps.
BBN Technologies (Verizon)
Ph:(617)873-2841
