Jeff,
The Wrapper simply launches the JVM process. I have never seen any
cases where the Wrapper actually affected the way the JVM operated.
This is most likely a problem with the parameters used to launch the
JVM.
Try setting the following:
wrapper.java.command.loglevel=INFO
This will cause the full java command line to be output to the log file.
Copy that directly to the command line, removing the -Dwrapper.key=XXXX
parameter and run it directly. If you also remove the libwrapper.so file
from the library path, you will be operating in a mode almost identical to
the case where the wrapper is not in the equation. You will still be using
the WrapperManager class, but that will be 100% if the native library has
been removed.
Cheers,
Leif
Jeff Greif wrote:
> We are running JBoss under control of the wrapper on Linux with java
> 1.5, where it works fine.
>
> When we try to add a jvm profiling option in wrapper.conf of the form
>
> wrapperjava.additional.7=-Xrunjmp:noods,nomonitors,dumpdir=/home/xxx/profiling-results,dumptimer=1000
>
> the java process starts using many times more memory than before during
> the application startup and becomes swap-bound. The jvm is trying to
> use 2-3x the memory specified in the -Xmx property. We have not yet
> determined where that memory use is occurring, but wonder if anyone has
> seen issues combining the wrapper native library with libjmp.
>
> Jeff
>
|
