[Wrapper-user] Starting the Wrapper from the Command Line (Say for Profiling)

[Robert D. <rdi...@tr...>]

I added the DEBUG flags to my configuration.

Then I started the wrapper as usual.

I was hoping I could take the command line and paste it into a
dos-prompt to run the wrapper that way. Basically something like this:

"..\jre\bin\java"=20
-Dtw.home=3D"C:/apps/tnd"=20
-classpath "../lib/wrapper.jar;<other stuff>=20
-Dwrapper.key=3D"..." -Dwrapper.port=3D32000 -Dwrapper.debug=3D"TRUE"=20
-Dwrapper.use_system_time=3D"TRUE"=20
-Dwrapper.version=3D"3.1.1"=20
-Dwrapper.native_library=3D"wrapper"=20
-Dwrapper.disable_shutdown_hook=3D"TRUE"=20
-Dwrapper.cpu.timeout=3D"10"=20
-Dwrapper.jvmid=3D1=20
com.tripwire.space.bootstrap.ServerLauncher

However, when I do this, I get an exception. Here's the output:

WrapperManager class initialized by thread: main  Using classloader:
sun.misc.Launcher$AppClassLoader@e80a59
Wrapper Manager: JVM #1
Wrapper Manager: Using wrapper
Loaded native library: wrapper.dll
Calling native initialization method.
Initializing WrapperManager native library.
Java Executable: C:\apps\tnd\jre\bin\java.exe
Windows version: 5.1.2600
Java Version   : 1.4.2_02-b03 Java HotSpot(TM) Server VM
Java VM Vendor : Sun Microsystems Inc.

Wrapper (Version 3.1.1) http://wrapper.tanukisoftware.org

WrapperManager.start(com.tripwire.space.bootstrap.ServerLauncher@152513a
, args[]) called by thread: main
Open socket to wrapper...
Failed to connect to the Wrapper.
java.net.ConnectException: Connection refused: connect
Exiting JVM...
WrapperManager.stopImmediate(1) called by thread: Wrapper-Connection
Send a packet STOP : 1
Send a packet STOPPED : 1

Any ideas what I'm doing wrong?

R.