Menu
▾
▴
Re: [Wrapper-user] Java number of threads
|
From: Chuck W. <ch...@ma...> - 2006-11-19 18:33:26
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Jaume,<br>
<br>
>From your description it sounds like you are creating the threads
dynamically? What happens if you use a thread pool instead?<br>
<br>
I also use wrapper 3.2.3 on debian etch, although with Sun java
1.5.0_09. I had a problem where dynamically created threads were left
in the defunct state for some time after they terminated. This caused
ps with thread display to show many more threads than expected, and
since I was running with maxed out java heap (-Xmx) led to native heap
OOM's because resources from the defunct threads (e.g., thread stack)
were not cleaned up quickly enough.<br>
<br>
Your problem sounds different, but a thread pool might separate issues
and give you more information.<br>
<br>
Chuck<br>
<br>
<br>
Leif Mortenson wrote on 11/19/2006 02:57 AM:
<blockquote cite="mid...@ta..." type="cite">
<pre wrap="">Jaume,
I can't think of anything that the wrapper would be doing that would
be causing
something like that. First of all make sure that you are using the
expected JVM.
You can see this by setting the wrapper.debug=true property and viewing the
command used to launch the JVM.
Next, after launching your app, try rerunning the shell script with
the dump
command. This will cause the JVM to do a full stack trace. You should then
be able to tell what each of your threads is doing, and thus hopefully
be able
to tell where they are coming from.
Cheers,
Leif
Jaume Obrador wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi people.
I have a problem using the java wrapper.
I used to run an small java chat application server, native compiled as
a daemon. Since I've experienced some problems running that way, I
decided to use java wrapper.
All works fine, but I have a problem in the number of processes given by
linux command "pstree". The application starts 2 new threads for each
new client connection, so "pstree" command should show 2 more processes,
but since I use the java wrapper, it shows 3 new processes, and when
client disconnects, there is a process remaining running, so with the
time, the number of java processes are increasing, which is a problem.
I've revised the code and made sure that only 2 threads where launched,
in fact, when I run the application without using the wrapper, "pstree"
shows the correct number of processes, the problem comes when I run it
as a daemon using the java wrapper.
I use Java wrapper 3.2.3, Debian etch in a VPS virtual server.
java version "1.4.2-03"
Java(TM) 2 Runtime Environment, Standard Edition (build
Blackdown-1.4.2-03)
Java HotSpot(TM) Client VM (build Blackdown-1.4.2-03, mixed mode)
Thanks a lot in advance,
Jaume Obrador.
</pre>
</blockquote>
<pre wrap=""><!---->
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
<a class="moz-txt-link-freetext" href="http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV">http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV</a>
_______________________________________________
Wrapper-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Wra...@li...">Wra...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/wrapper-user">https://lists.sourceforge.net/lists/listinfo/wrapper-user</a>
</pre>
</blockquote>
<br>
</body>
</html>
|
