|
From: Leif M. <le...@ta...> - 2003-02-11 15:41:11
|
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
|