RE: [Wrapper-user] wrapper performance problem

[Kool, M (Marcel) <M....@rf...>]

Leif,

Thanks very much for your reply. My problem seems to have solved itself
when
a network administrator changed my account security settings. I should
have
been full local admin but there were still some restrictions,
particularly
in accessing the registry. I don't know if this is a plausible cause for
the
performance problems I have experienced, but after the change to my
account
I fired up the wrapper and it performed really well! The service runs
under
system account. I did not change anything in the code or the jvm used
etc.
Can it be that the wrapper tries to access the registry about every
second?
(I saw execution halt every second when I had the performance problem).

Thanks,

Marcel

-----Oorspronkelijk bericht-----
Van: Leif Mortenson [mailto:le...@ta...]
Verzonden: dinsdag 11 februari 2003 16:40
Aan: wra...@li...
Onderwerp: Re: [Wrapper-user] wrapper performance problem


Marcel,
    I wonder what is causing that.  I always use the Wrapper with very 
I/O intensive
applications and have never experienced any problems with performance.
The
I/O between the Wrapper and the JVM is very light weight.  I can't 
imagine that
would be the problem.

    Could you try a few things out for me?

1) What Wrapper version, JVM version, and platform are you running?

2)  Is it possible that your application is not using the JVM that you 
are expecting
when running under the Wrapper?   You can verify this by enabling DEBUG 
output.
Towards the top of the log output, you will see something like the 
following:
---
Initializing WrapperManager native library.
Java Executable: D:\Sun\j2sdk1.4.0_03\bin\java.exe
Java Version   : 1.4.0_03-b04 Java HotSpot(TM) Client VM
Java VM Vendor : Sun Microsystems Inc.
---
I have seen cases where the Wrapper is finding the Microsoft JVM on the 
path.

3) From the debug output above, you will also see the command that the 
wrapper
uses to launch the JVM.   Please copy that into a batch file and remove
the
-Dwrapper.key="xxxxxxx" parameter.   You should then be able to run your
application with the exact same JVM parameters as with the Wrapper,
while at
the same time, taking the wrapper out of the loop.
Carefully compare the command line with the command line that you used 
without
the wrapper and make sure that they are the same.

Can you also post your wrapper.conf along with the first 100 or so lines
of debug
output?

Cheers,
Leif




-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user



================================================
De informatie opgenomen in dit bericht kan vertrouwelijk zijn en 
is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht 
onterecht ontvangt, wordt u verzocht de inhoud niet te gebruiken en 
de afzender direct te informeren door het bericht te retourneren. 
================================================
The information contained in this message may be confidential 
and is intended to be exclusively for the addressee. Should you 
receive this message unintentionally, please do not use the contents 
herein and notify the sender immediately by return e-mail.