Re: [Wrapper-user] Tomcat console logging: Win XP vs. Win 2K

[Leif M. <le...@ta...>]

Scott,
    Looking over your wrapper.conf file, I do not see any problems.  I 
actually
have a Dual CPU W2k system at home and it has been working perfectly.  So
I don't think it is an issue with the OS.   I will retest it again 
tonight though just
to make sure.   I use it for services rather than for day to day use so 
I may have
overlooked something.

    When the Wrapper starts up it will attempt to write to the log file 
specified
in the wrapper.conf file.  In your case this resolves to
C:/Inventa/ESMIntegrator3.0/portal/var/wrapper.log

    If the Wrapper is unable to write to configured file it will fall 
back to writing
to a log file called wrapper.log which is located in the same directory 
as the
Wrapper.exe file.   When running as an NT service, there are some failure
modes where it is also possible that the wrapper.log file could be 
created in
the C:\Windows\system32 directory.  Or wherever your Windows directory
is located.   Can you please verify that the file does not exist in 
those locations?

    The next thing I would have you try is set the following:
wrapper.syslog.loglevel=STATUS
    This will log all of the info level output to your system event 
log.  It may give
you some useful information.   If not, try a level of INFO.  That will 
fill your log
up fairly quickly as each individual line of output results in a log entry.

>I get no output to the wrapper.log file regardless of
>whether I enable debugging or not.
>
This is strange.  If you are not even getting any output before the JVM 
is launched
then the Wrapper must be having some problems writing to the log file. 

>If I run the app
>via the wrapper console mode (wrapper.exe -c),
>I see the console output (of course) - and it gets logged
>to the wrapper.log file (attached).
>
Ok, that file looked normal.

>  If I run "wrapper -t" 
>to start the app, I get no output beyond the standard 3 log
>statements from Wrapper itself.
>
You should get more than 3 lines if the debug output is enabled?  Can 
you show me
what 3 lines you are talking about?

>  If I start it from the 
>Windows Management Console, *no* wrapper.log file gets
>created at all.  I searched the filesystems to see if it's
>getting created somewhere else, but it's not...
>  
>
Hmm.   Please recheck the locations I mentioned above.

>Any thoughts?
>  
>
"Mondays!" :-)   There must be a logical reason for this.  Post back 
with info I asked for
above and I'll try to think of what could be going wrong for you.

Are you sure that the Wrapper and its JVM are actually running after you 
start it?  There
was a bug fixed for the next release that involved the setting of 
environment variables
when running as an NT service.  It is possible that your use of 
environment variables
with the set.xxx properties could be running into this problem.   This 
but would cause
one or more environment variables to not actually be set.  If your 
application happened to
be using that particular environment variable, it would fail.

Try hardcoding the paths into your wrapper.conf file without using the 
environment
variable replacements.  If that makes the problem go away then you most 
likely running
into this bug.

Cheers,
Leif