----------------------------------------------------------------
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!!!
----------------------------------------------------------------

Hey Fabio,

This is very similar to a problem I once had with JServ on 1.1.X, although
your core-dump seems to be resulting from a different fault.  Regardless,
the sporadic OutOfMemoryErrors were something that we had problems with,
despite having a very big java heap size and having profiled our code and
seen no memory leak.  Using truss, I found that I was getting EMFILE when
the JVM was calling 'open("/dev/zero")'.  This means the process cannot get
any more file descriptors from the OS, and apparently the JVM uses file
descriptors to allocate memory (!).  The default for Solaris is only 64.
When I increased the number of file descriptors to 1024, (try 'ulimit -S -n
1024' from shell that invokes the JVM), the problem disappeared.

(Also check to make sure you're not having a system-wide memory shortfall.
I've found this can cause 1.1.X JVMs to crash and dump core).

If you need to reproduce the problem, try applying some artificial load to
your servlet.  This should cause it to happen quite quickly, if you're
seeing what I was.   If increasing the file descriptor limit doesn't help,
try using 'truss' on the JVM process and look for errors.  'truss' can be a
miracle worker!

Good Luck,
Mike.

> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Fabio
> Mengue
> Sent: Tuesday, June 13, 2000 1:00 PM
> To: [EMAIL PROTECTED]
> Subject: JServ and core dumps
>
>
> ----------------------------------------------------------------
> 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'm having a strange problem. Already read the FAQ (there are
> several items that resemble my problem, already tried most of the
> solutions) but I think that this one is a little bit tricky.
>
>     I'm using:
>
> -Sun Ultra E250, 512Mb RAM, 10Gb disc, Solaris 2.7
> -Apache 1.3.6, with openssl 0.9.4 (I don't remember the version of
> mod_ssl)
> -Jserv 1.0 (manual mode)
> -JDK Native 1.1.7 (Sun Package)
> -JSDK 2.0
> -DB2 Client (DB2 6.0 enterprise server is on another machine)
>
>     The machine is used only to serve servlets. The upload is 0.02
> average. The configuration is up and running for 1,5 years, with one or
> another problem from time to time (mostly programers' mistakes). But now
> (another project is online), several problems are happening.
>
>     I had only one servlet zone, and now I have another two. JServ is
> failing several times a day. I can't tell what servlet is generating the
> error, because sometimes a servlet works, and sometimes it does not.
> When I kill -15 the hava process, things get back to normal for a time.
> Looks to me that the error has something to do with JServ, or the way
> the programers are doing their servlets (they are using IBM VisualAge
> Enterprise, same environment as the first project).
>
>     JServ sometimes is able to be up for hours, and sometimes it keep
> going down every 15 minutes.
>
>     My log files (jserv.log) have almost all error messages in the
> FAQ :). JServ stops working sometimes with core dump, sometimes with
> "ajp11: cannot scan servlet headers", sometimes with "ajp11: connection
> fail". I got OutOfMemory Exception, got DB2 Driver Exceptions...
>
>     As JServ is run in manual mode, I'm able to see what happens when a
> core is dumped, but the messages are not helping much.
>
> Data:Thu Jun  8 16:30:26 EST 2000
> SIGILL    4*   illegal instruction
>     si_signo [4]: SIGILL    4*   illegal instruction
>     si_errno [0]: Error 0
>     si_code [1]: ILL_ILLOPC [addr: 0xfd2b7dc8]
>
>         stackbase=FFBEF948, stackpointer=FFBEE80C
>
> Full thread dump:
>     "Thread-4" (TID:0xfd279878, sys_thread_t:0x154318, state:CW,
> thread_t:
> t@9, sp:0xfed20e48 threadID:0xfed21dc8, stack_base:0xfed21d5c,
> stack_size:0x20000) prio=5
>         org.apache.jserv.JServServletManager.run(Compiled Code)
>         java.lang.Thread.run(Compiled Code)
>     "Thread-3" (TID:0xfd275700, sys_thread_t:0x154288, state:CW,
> thread_t:
> t@8, sp:0xfed50e48 threadID:0xfed51dc8, stack_base:0xfed51d5c,
> stack_size:0x20000) prio=5
>         org.apache.jserv.JServServletManager.run(Compiled Code)
>         java.lang.Thread.run(Compiled Code)
>     "Thread-2" (TID:0xfd271330, sys_thread_t:0x153d00, state:CW,
> thread_t:
> t@6, sp:0xfed80de8 threadID:0xfed81dc8, stack_base:0xfed81d5c,
> stack_size:0x20000) prio=5
>         org.apache.jserv.JServServletManager.run(Compiled Code)
>         java.lang.Thread.run(Compiled Code)
>     "SIGQUIT handler" (TID:0xfd2662a0, sys_thread_t:0x7f568, state:R,
> thread_t: t@5, sp:0xfeec1b40 threadID:0xfeec1dc8, stack_base:0xfeec1d5c,
>
> stack_size:0x20000) prio=0
>     "Finalizer thread" (TID:0xfd266088, sys_thread_t:0x7f4d8, state:CW,
> thread_t: t@4, sp:0xfeef1a80 threadID:0xfeef1dc8, stack_base:0xfeef1d5c,
>
> stack_size:0x20000) prio=1
>     "main" (TID:0xfd2660b0, sys_thread_t:0x7eee8, state:R, thread_t:
> t@1,
> sp:0xffbef4f0 threadID:0x20a18, stack_base:0xffbef948,
> stack_size:0x800000)
> prio=5 *current thread*
>         java.net.PlainSocketImpl.accept(Compiled Code)
> Abort - core dumped
>
>     I had several of these, and they sometimes complains about DB2, like
>
>
>
> Full thread dump:
>     "Thread-284" (TID:0xfd2b3fd8, sys_thread_t:0x70d918, state:R,
> thread_t: t@28
> 9, sp:0xfe3f1d68 threadID:0xfe3f1dc8, stack_base:0xfe3f1d5c,
> stack_size:0x20000)
>  prio=5 *current thread*
>         COM.ibm.db2.jdbc.app.DB2Connection.<init>(Compiled Code)
>         COM.ibm.db2.jdbc.app.DB2Driver.connect(Compiled Code)
>         java.sql.DriverManager.getConnection(Compiled Code)
>         com.ibm.ivj.eab.dab.DatastoreJDBC.connect(Compiled Code)
> ...
> Registered Monitor Dump:
>     Verifier lock: <unowned>
>     PCMap lock: <unowned>
>     Thread queue lock: <unowned>
>     Name and type hash table lock: <unowned>
>     String intern lock: <unowned>
>     JNI pinning lock: <unowned>
>     JNI global reference lock: <unowned>
>     BinClass lock: <unowned>
>     Class loading lock: <unowned>
>     Java stack lock: <unowned>
>     Code rewrite lock: <unowned>
>     Heap lock: <unowned>
>     Has finalization queue lock: <unowned>
>     Finalize me queue lock: <unowned>
>         Waiting to be notified:
>             "Finalizer thread" (0x8bb98)
>     Monitor registry: owner "Thread-284" (0x70d918, 1 entry)
> Abort - core dumped
>
>
>     Well, until now, I put a program to monitor JServ (to put it up in
> case it stop working), tried to increase the HEAP space of JDK, enabled
> servlet trace, disabled servlet trace, did a program-by-program test
> with the System's Analist, but I didn't have a clue of what is going on.
> Most of this because sometimes I get error, and sometimes don't.
>
>     I think that maybe some problem with pointers or garbage collection.
> Maybe if I upgrade to JServ 1.1.1 ?
>
>     I don't know if this is enough for you to get the picture. I don't
> want to send a very long email, so I'll leave the config files out of
> this message. If they are needed, let me know, I'll send them.
>
>     Thanks a lot, sorry for my bad english.
>
>     See ya,
>
> Fabio.
> ---
> State University Of Campinas
> [EMAIL PROTECTED]
> [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]

Reply via email to