----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
I checked IBM's web site and it appears that the JDK they make available
does not run on Solaris.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of M.
Greenblatt
Sent: Thursday, October 28, 1999 12:36 PM
To: Java Apache Users
Subject: Re: Apache eats swap and dies every 15 days or so...
----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
This sounds like it may be memory mismanagement by the JVM. Have you
tried JVMs from other venders such as IBM?
- MG
Kyle Hodgson wrote:
>
> ----------------------------------------------------------------
> BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
> WHEN YOU POST, include all relevant version numbers, log files,
> and configuration files. Don't make us guess your problem!!!
> ----------------------------------------------------------------
>
> Hello. I did not check the FAQ, but it is down and I don't think my
> question's answer is in it.
>
> First my setup:
>
> Ultra Sparc 5 / Solaris 2.6 / Java1.1.8_09 / Apache 1.3.6 / JSDK 2.0 /
JServ
> 1.0
>
> Problem:
>
> Memory usage grows and grows. The system has 256 MB, so it takes it a
while
> to get to the point where it's swapping at all. When we were running JDK
> 1.1.7_0x it took 5 days, now it takes 15 or so since we upgraded to
> 1.1.8_09. Once it gets to the point where it has to bite disk for more
> memory, our servlets stop responding. A full stop and restart of Apache
> will solve the problem for a few hours, but it does not return all the
> improperly allocated memory to the system so it just happens all over
again
> 4 hours later or so.
>
> Potential complications:
>
> 1. We are doing a `kill -HUP $mainapachepid` every night to facilitate
daily
> log rollover. Kill -HUP does not seem to restart the JVM. But then
again,
> neither does a full kill and restart.
>
> 2. We are using a regular ODBC bridge from Intersolv on one of our servlet
> zones. We have noticed performance issues and parallel insert problems
> using this bridge. Our other zone is using the Merant (Intersolv) JDBC
> drivers and is much more stable. Both servlet zones go down when the
> symptoms are present.
>
> Any ideas?
>
> Kyle Hodgson
> Network Administrator
> Insite Communications
>
> --
> --------------------------------------------------------------
> Please read the FAQ! <http://java.apache.org/faq/>
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://java.apache.org/main/mail.html>
> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
