What I understand in your answer, is that with JBoss we should=20
- avoid making separate configurations files or launching the listener
- set globally the log4j in Jboss's log4j file
- eventually set categories for used packages like com.interface21 in
De=A0: Kopylenko, Dmitry [mailto:dkopylenko@...
Envoy=E9=A0: vendredi 25 juillet 2003 23:34
=C0=A0: 'JP Pawlak '; 'springframework-developer@... '
Objet=A0: RE: [Springframework-developer] log4j and jboss
we just use JBoss' log4J service. Just add the Category configurations
the JBoss' master config file like :
From: JP Pawlak
Sent: 7/25/2003 2:48 PM
Subject: [Springframework-developer] log4j and jboss
I have no more issue with ";jsession". So thanks also to Alef who
started to battle with.
I just committed changes on config files. By testing, I was stopped by
the log4j configuration file once more.
I have in fact two issues.
1) As I heard on a JBoss List, the log4j architecture doesn't allow two
masters. So the JBoss config and the application one are a bit tied and
have to be at least a bit compatible.
As this, I cannot, for example, redefine the console. I had this error
with the original config :
18:15:11,078 INFO [jbossweb] Initializing Log4J from C:\Documents and
ERROR: invalid console appender config detected, console stream is
2) The issue I tell about. There is no real crash, only the
logging stops. So I let the config location in web.xml, but launching
the setup with the listener creates and populates correctly the file as
expected. But the JBoss logging doesn't more exist. And the console
equally will no more write anything.