RE: [Wrapper-user] JBoss 3.2.2 logging problems

[Sal I. <sal...@vo...>]

JBoss 3.2.2 logging problemswhen the system is starting / stopping it uses
the jboss/server/default/conf/log4j.xml / properties to control logging.
however, if one of your apps deployed in jboss/server/default/deploy
contains a log4j.jar / lo4j.xml / log4j.properties, it may take over the
initial logger used for bootup.
that will behave differently depending of whether you have setup a jboss
loader repository in your jboss-serverice.xml in your jar/war/ear/sar/xml:
<loader-repository>jboss.loader.repository:sar=support-watchdog.sar</loader-
repository>
when jboss stops, it undeployes your app, and hence your logger.  at this
point, it reverts to the /conf logger (the bootup logger), which logs
differently than your logger.
that's why you can see the shutdown being logged.
so this perfectly explains your situation: just take a look at what you are
deploying.
remember that jboss uses a class loader hierarchy.  you can read about in
the jboss docs to better understand how it affects your app.

if it's still happens, i have only one more idea:
i have a couple of tools that log a LOT to the console.
that's System.out.println () calls which are in turn stdout calls.
after a while my program runs, windows/log4j decides that it's not going to
print out stdout calls anymore.
i don't know why they does that, but i can tell you that that's NOT the
wrapper.

now try changing your your wrapper.console.loglevel=INFO to
wrapper.console.loglevel=DEBUG and see if it's any better.

good luck.
  -----Original Message-----
  From: wra...@li...
[mailto:wra...@li...]On Behalf Of Fuechsel,
Andre
  Sent: Friday, July 23, 2004 1:01 AM
  To: 'wra...@li...'
  Subject: [Wrapper-user] JBoss 3.2.2 logging problems


  Hi,

  I set up my JBoss 3.2.2 with the wrapper_win32_3.1.1 and everything works
well except the logging. Running the JBoss.bat script everything works as
expected and I get all the JBoss loggings as configured in the configuration
file${jboss.home}/server/myserver/conf/log4j.xml.

  But having JBoss now installed as a Windows service, the logging behaviour
is very strange:

  The startup process is logged correctly both in wrapper.log and in
server.log from JBoss.

  After the server has been started, nothing else is logged in both files
(the last line is the usual

  INFO   | jvm 1    | 2004/07/22 14:07:07 | 14:07:07,221 INFO  [Server]
JBoss (MX MicroKernel) [3.2.2 (build: CVSTag=JBoss_3_2_2 date=200310182216)]
Started in 3m:49s:941ms

  The shutdown process is logged again as usual.

  Any ideas where the other logs are going to? This is my configuration:

  wrapper.console.format=PM
  wrapper.console.loglevel=INFO
  wrapper.logfile=..\logs\wrapper.log
  wrapper.logfile.format=LPTM
  wrapper.logfile.loglevel=INFO
  wrapper.logfile.maxsize=1m
  wrapper.logfile.maxfiles=50
  wrapper.syslog.loglevel=STATUS

  Thanks in advance.

  André