[Wrapper-user] No GUI ?!?

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Hello all,
	I am attempting to use wrapper 2.2.9 on WIndows 2000, and I have everything working....except....The GUI 
of my swing app doesnt show!!!  I am using the WrapperSimpleApp method to call my main, which constructs my 
mainFrame, calls mainFrame.show();, and then does some other stuff on startup.  Well, I see the output of the other 
stuff, but the GUI never pops up, minimized or otherwise.  I turned debug level to DEBUG, but didnt get an errors.
	Help!!!!!!!!
	-Kevin

ps. Wrapper is a great program after *struggling* with JavaService!!!

Here is a copy of my wrapper.log with DEBUG on:

STATUS | wrapper  | 2002/12/06 10:10:05 | --> Wrapper Started as Service
STATUS | wrapper  | 2002/12/06 10:10:06 | Launching a JVM...
INFO   | jvm 1    | 2002/12/06 10:10:06 | Wrapper Manager: JVM #1
INFO   | jvm 1    | 2002/12/06 10:10:06 | Wrapper Manager: Registering shutdown hook
INFO   | jvm 1    | 2002/12/06 10:10:06 | Wrapper Manager: Using wrapper
INFO   | jvm 1    | 2002/12/06 10:10:06 | Calling native initialization method.
INFO   | jvm 1    | 2002/12/06 10:10:06 | Initializing WrapperManager native library.
INFO   | jvm 1    | 2002/12/06 10:10:06 | Java Executable: C:\WINNT\system32\java.exe
INFO   | jvm 1    | 2002/12/06 10:10:06 | Java Version   : 1.4.1_01-b01 Java HotSpot(TM) Client VM
INFO   | jvm 1    | 2002/12/06 10:10:06 | Java VM Vendor : Sun Microsystems Inc.
INFO   | jvm 1    | 2002/12/06 10:10:06 | 
INFO   | jvm 1    | 2002/12/06 10:10:06 | Wrapper (Version 2.2.9)
INFO   | jvm 1    | 2002/12/06 10:10:06 | 
INFO   | jvm 1    | 2002/12/06 10:10:06 | Open socket to wrapper...
INFO   | jvm 1    | 2002/12/06 10:10:06 | Opened Socket
INFO   | jvm 1    | 2002/12/06 10:10:06 | Send a packet 110 : 4QGMfYBgsq8SluYi
INFO   | jvm 1    | 2002/12/06 10:10:06 | handleSocket(Socket[addr=/127.0.0.1,port=1777,localport=1230])
INFO   | jvm 1    | 2002/12/06 10:10:07 | Received a packet 112 : 1
INFO   | jvm 1    | 2002/12/06 10:10:07 | Wrapper Manager: LowLogLevel from Wrapper is 1
INFO   | jvm 1    | 2002/12/06 10:10:07 | Received a packet 100 : start
INFO   | jvm 1    | 2002/12/06 10:10:07 | calling listener.start()
INFO   | jvm 1    | 2002/12/06 10:10:07 | WrapperSimpleApp: start(args)
INFO   | jvm 1    | 2002/12/06 10:10:07 | WrapperSimpleApp: invoking main method
INFO   | jvm 1    | 2002/12/06 10:10:09 | WrapperSimpleApp: start(args) end.  Main Completed=false, exitCode=null
INFO   | jvm 1    | 2002/12/06 10:10:09 | returned from listener.start()
INFO   | jvm 1    | 2002/12/06 10:10:09 | Send a packet 106 : 
INFO   | jvm 1    | 2002/12/06 10:10:11 | Received a packet 103 : ping
INFO   | jvm 1    | 2002/12/06 10:10:11 | Send a packet 103 : ok
INFO   | jvm 1    | 2002/12/06 10:10:12 | 10:10:12.064 EVENT  Starting Jetty/4.2
INFO   | jvm 1    | 2002/12/06 10:10:12 | 10:10:12.114 EVENT  Started ServletHttpContext[/]
INFO   | jvm 1    | 2002/12/06 10:10:12 | 10:10:12.134 EVENT  Started SocketListener on 0.0.0.0:82
INFO   | jvm 1    | 2002/12/06 10:10:12 | 10:10:12.134 EVENT  Started org.mortbay.jetty.Server@9b688e
INFO   | jvm 1    | 2002/12/06 10:10:12 | WrapperSimpleApp: main method completed
INFO   | jvm 1    | 2002/12/06 10:10:17 | Received a packet 103 : ping
INFO   | jvm 1    | 2002/12/06 10:10:17 | Send a packet 103 : ok
INFO   | jvm 1    | 2002/12/06 10:10:23 | Received a packet 103 : ping
INFO   | jvm 1    | 2002/12/06 10:10:23 | Send a packet 103 : ok

Here is a copy of my wrapper.conf:

#********************************************************************
# Wrapper parameters
#********************************************************************
# Java Application
wrapper.java.command=java

# Java Main class
wrapper.java.mainclass=com.silveregg.wrapper.WrapperSimpleApp

# Set the first application parameter to the name of the class whose main method
# is to be launched.  Additional parameters come after this one.
wrapper.app.parameter.1=com.ustream.server.Main

# Java Additional Parameters
wrapper.java.additional.1=-Djava.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol

# Java Classpath (include wrapper.jar)  Add class path elements as
#  needed starting from 1
wrapper.java.classpath.1=3rdparty/lib/Wrapper_2.2.9/wrapper.jar
wrapper.java.classpath.2=3rdparty/lib/Dom4J_1.3/dom4j-full.jar
wrapper.java.classpath.3=3rdparty/lib/JD3Lib_a4/jd3lib-a4.jar
wrapper.java.classpath.4=3rdparty/lib/Jetty_4.2.2/ant.jar
wrapper.java.classpath.5=3rdparty/lib/Jetty_4.2.2/com.sun.net.ssl.jar
wrapper.java.classpath.6=3rdparty/lib/Jetty_4.2.2/crimson.jar
wrapper.java.classpath.7=3rdparty/lib/Jetty_4.2.2/javax.servlet.jar
wrapper.java.classpath.8=3rdparty/lib/Jetty_4.2.2/javax.xml.jaxp.jar
wrapper.java.classpath.9=3rdparty/lib/Jetty_4.2.2/org.mortbay.jetty.jar
wrapper.java.classpath.10=3rdparty/lib/Jetty_4.2.2/start.jar
wrapper.java.classpath.11=3rdparty/lib/Log4j_1.2.7/log4j-1.2.7.jar
wrapper.java.classpath.12=3rdparty/lib/SkinLF_1.2.3/nativeskin.jar
wrapper.java.classpath.13=3rdparty/lib/SkinLF_1.2.3/skinlf.jar
wrapper.java.classpath.14=3rdparty/lib/XML-RPC_1.1/xmlrpc-1.1.jar
wrapper.java.classpath.15=webapps/root/WEB-INF/classes

# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=3rdparty/lib/Wrapper_2.2.9/

# Initial Java Heap Size (in MB)
wrapper.java.initmemory=16

# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=64

# Port which the native wrapper code will attempt to connect to
wrapper.port=1777

#********************************************************************
# Wrapper Logging parameters
#********************************************************************
# Format of output for the console.  (See docs for formats)
wrapper.console.format=PM

# Log Level for console output.  (See docs for log levels)
wrapper.console.loglevel=DEBUG

# Log file to use for wrapper output logging.
wrapper.logfile=logs/wrapper.log

# Format of output for the log file.  (See docs for formats)
wrapper.logfile.format=LPTM

# Log Level for log file output.  (See docs for log levels)
wrapper.logfile.loglevel=INFO

# Maximum size that the log file will be allowed to grow to before
#  the log is rolled. Size is specified in bytes.  The default value
#  of 0, disables log rolling.  May abbreviate with the 'k' (kb) or
#  'm' (mb) suffix.  For example: 10m = 10 megabytes.
wrapper.logfile.maxsize=10m

# Maximum number of rolled log files which will be allowed before old
#  files are deleted.  The default value of 0 implies no limit.
wrapper.logfile.maxfiles=10

# Log Level for sys/event log output.  (See docs for log levels)
wrapper.syslog.loglevel=NONE

#********************************************************************
# Wrapper Unix daemon parameters
#********************************************************************
# File to write process ID to
wrapper.pidfile=/var/run/testwrapper.pid

#********************************************************************
# Wrapper NT Service parameters
#********************************************************************
# WARNING - Do not modify any of these parameters when an application
#  using this configuration file has been installed as a service.
#  Please uninstall the service before modifying this section.  The
#  service can then be reinstalled.

# Name of the service
wrapper.ntservice.name=U-stream

# Display name of the service
wrapper.ntservice.displayname=U-stream

# Description of the service
wrapper.ntservice.description=U-stream Service Wrapper

# Service dependencies.  Add dependencies as needed starting from 1
wrapper.ntservice.dependency.1=

# Mode in which the service is installed.  AUTO_START or DEMAND_START
wrapper.ntservice.starttype=AUTO_START

# Priority at which the service is run.  NORMAL, LOW, HIGH, or
#  REALTIME
wrapper.ntservice.process_priority=NORMAL