The following article:
http://java.sun.com/products//jdk/1.2/docs/tooldocs/solaris/threads.html
It discusses native and green threads on Solaris, and says:
"In some instances, it may be advisable to use the default green threads.
Native code that is not multithread safe (MT-safe) may not work correctly
with native threads."
AFAIK, the only native code in Tomcat is the mod_jserv/mod_jk stuff, so it
wouldn't explain why using the built-in server does it too.
Anyway, you could try `setenv THREADS_FLAG green`, and then restart Tomcat
*and* Apache, and see if that helps.
This profiling tool may also be of use:
http://java.sun.com/people/billf/heap/
--Jeff
On Thu, 7 Dec 2000, Matt White wrote:
> Hello...
>
> I'm attempting to setup Tomcat 3.2 on a Solaris 8/x86 machine. My setup is as
>follows:
>
> - Solaris 8/x86
> - Apache 1.3.14
> - mod_jk
> - PHP 4.0.3pl1
> - mod_dav 1.0.2
>
> java -version reports:
>
> java version "1.2.2"
> Solaris VM (build Solaris_JDK_1.2.2_05a, native threads, sunwjit)
>
>
> With that out of the way, here's my problem.
>
> When I attempt to execute a .JSP page the Java VJM launches (as seen
> with top), and starts to run. However, it keep on running, consuming
> more and more CPU power until it reaches around 50%. (This is a dual
> processor box.) The VJM will not quit. I've let it go for around three
> minutes before I've killed it several times.
>
> I get the exact same result when I use Tomcat via Apache/mod_jk, as
> well as the built-in HTTP server in Tomcat. (The HTTP server in Tomcat
> works, I should add.)
>
> I'm out of ideas for debugging. I see nothing unusual in the logs. Has
> anyone seen this before? I'm stumped.
>
> Thanks,
> Matt White
> Mad River Local Schools
> [EMAIL PROTECTED]
>
