RE: [Wrapper-user] Wrapper problems

[Jeff H. <je...@je...>]

Leif,

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> From: Leif Mortenson
>
> No ideas without more info.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

What do you need?

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> The most common problem when running as a service are
> caused by differences in the environment between the
> SYSTEM user and the user used to run the app in a
> console.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

Yeah, I've gathered that from what I've found in the archive that was
similar to my problem.

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> For example.  If you are using the JAVA_HOME environment
> variable, make sure that it is available to the SYSTEM
> user.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

I thought of that, but I didn't use any environment variables in
wrapper.conf.

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> In any case, you should be able to see what the problem
> is by looking at the wrapper.log file.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

Here's the entire dump of log data that's generated when I start the
service.

STATUS | wrapper  | 2003/04/20 16:53:29 | --> Wrapper Started as Service
STATUS | wrapper  | 2003/04/20 16:53:30 | Launching a JVM...
INFO   | jvm 1    | 2003/04/20 16:53:30 | Wrapper (Version 3.0.2)
INFO   | jvm 1    | 2003/04/20 16:53:30 |
INFO   | jvm 1    | 2003/04/20 16:53:30 | Starting client...

The weird thing is that jar file (status.jar) is definitely being used by
the wrapper cause the file is locked, preventing me from overwriting,
renaming, or deleting it.  However, it's web interface doesn't come up as
expected (it basically listens on a specified port and acts as a
mini-webserver) when requested in the same manner used when the jar file is
executed manually.  I check netstat to see what ports the machine is
listening on and don't see the port the jar file is configured to listen on.

I have a sneaking suspicion that the jar file isn't initializing properly
called as a service by the wrapper, but don't know enough about Java to
figure out how to isolate and fix it.  The few things I do know are that
when calling the test batch file (status.bat) it goes through the wrapper
initialization sequence and then opens up a Java GUI (spawned by status.jar,
the jar file I'm trying to run as a service).  The console stays open until
I close the Java GUI.  If I execute status.jar manually then the GUI doesn't
come up the first time.  In order to get the GUI to open I have to have the
jar file running and then manually execute it again (by double-clicking it).
I'm wondering if maybe the GUI opening when using the test batch file
(status.bat) and starting it as a service are at all related.

Thanks,

Jeff

-----------------------------------------------------------
 Jeff Howden                        http://jeffhowden.com/
 mailto:je...@je...          phone://541.913.9261/
-----------------------------------------------------------
 Your source for high performance, dynamic site solutions
-----------------------------------------------------------