Re: [Wrapper-user] Java number of threads

[Leif M. <le...@ta...>]

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:
> 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.
>