[Bug 1004] New: Log4j logging doesn't work anymore

[email protected] Fri, 13 Mar 2015 11:37:11 +0000
Newsgroups gmane.comp.corba.jacorb.bugs
Message-ID <[email protected]/bugzilla/>
http://www.jacorb.org/bugzilla/show_bug.cgi?id=1004

            Bug ID: 1004
           Summary: Log4j logging doesn't work anymore
           Product: JacORB
           Version: 3.5
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: major
          Priority: P5
         Component: ORB
          Assignee: [email protected]
          Reporter: [email protected]

Hi,

We actualy use JacORB3.2 and the SLF4J log4j12 logging system.

the log4.properties is :

# par defaut niveau = WARN
#
log4j.rootLogger=WARN,sas,jsys

# définition des logs à inscrire dans le journal système
log4j.appender.jsys=sas.trace.serveur.TraceLog4JAppender
# définition du motif de sortie
log4j.appender.jsys.layout=org.apache.log4j.PatternLayout
log4j.appender.jsys.layout.ConversionPattern=%d %5p [%t] (%F\:%L) - %m%n

# définition des logs fichier du serveurs SAS
# Logs rotatifs
log4j.appender.sas=org.apache.log4j.RollingFileAppender
# Fichier destination
log4j.appender.sas.File=/home/opsnetv3/fichiers/log/opsnetv3/services.log
log4j.appender.sas.ImmediateFlush=true
# Nombre de fichiers de rotation (en plus du fichiers de log)
log4j.appender.sas.MaxBackupIndex=10
# Taille maximum avant rotation
log4j.appender.sas.MaxFileSize=100000KB
# définition du motif de sortie
log4j.appender.sas.layout=org.apache.log4j.PatternLayout
log4j.appender.sas.layout.ConversionPattern=%d %5p [%t] (%F\:%L) - %m%n

log4j.logger.jacorb=DEBUG,jacorb
log4j.additivity.jacorb=false
# Logs rotatifs
log4j.appender.jacorb=org.apache.log4j.RollingFileAppender
# Fichier destination
log4j.appender.jacorb.File=/home/opsnetv3/fichiers/log/orb/jacorb.log
log4j.appender.jacorb.ImmediateFlush=true
# Nombre de fichiers de rotation (en plus du fichiers de log)
log4j.appender.jacorb.MaxBackupIndex=10
# Taille maximum avant rotation
log4j.appender.jacorb.MaxFileSize=100000KB
# définition du motif de sortie
log4j.appender.jacorb.layout=org.apache.log4j.PatternLayout
log4j.appender.jacorb.layout.ConversionPattern=%d %5p [%t] (%F\:%L) - %m%n


This was working fine because in the jacorb.log file we have outputs like :

2015-03-13 11:14:09,191  INFO [main] (ORBSingleton.java:102) - created
ORBSingleton
2015-03-13 11:14:09,237  INFO [main] (InterceptorManager.java:88) -
InterceptorManager started with 2 Server Interceptors, 2 Client Interceptors
and 0 IOR Interceptors
2015-03-13 11:14:09,803  INFO [main] (ClientConnectionManager.java:130) -
ClientConnectionManager: created new ClientGIOPConnection to
vsasdev4.dev.cy.cassidian.net:14200 (656e018a)
2015-03-13 11:14:09,827  INFO [main] (ClientIIOPConnection.java:169) -
Connected to vsasdev4.dev.cy.cassidian.net:14200 from local port 46439

But since the migration to JacORB 3.6 the file remain empty
A test has been made with JacORB 3.4 with the same result.


It looks like a regression or we have missed a configuration option

Thanks for your assistance

-- 
You are receiving this mail because:
You are the assignee for the bug.

_______________________________________________
jacorb-bugs mailing list
[email protected]
https://lists.spline.inf.fu-berlin.de/mailman/listinfo/jacorb-bugs