>From recent experience with this kind of problems you may want to run "prstat
>-L -p " on the process using the CPU to identify the thread that loops.
Then use gdb to either attach to the process, or to analyse a core that you
have forced by sending the process an adequate signal (e.g. QUIT, T
This looks to me like something is attempting to allocate memory in a
loop, until the request succeeds. But it's never succeeding.On 11/22/05, Kjell Grindalen <
[EMAIL PROTECTED]
> wrote:
Hi everyone!
I am runninng apache-2.0.55 on a Solaris 9 SPARC server.
I use the server a a frontend
On 11/23/05, Kjell Grindalen <[EMAIL PROTECTED]> wrote:
> Hello, and thank you for the reply!
>
> First of all I am not using any dynamically loaded module, and I am not
> realyy using the proxy module either.
> I could eaily rmove them and get the same functonality
>
> Here is the output of pstack
On 11/22/05, Kjell Grindalen <[EMAIL PROTECTED]> wrote:
> I am runninng apache-2.0.55 on a Solaris 9 SPARC server.
> I use the server a a frontend for my websphere 5.1 server
> My configure looks like this
>
> ./configure --prefix=/usr/local/apache_prod --with-mpm=prefork --enable-info
> --enable-s
