Databases
StackOverflow2013
Postsdbo
POSpring logs missing in WAS7
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSpring logs missing in WAS7
    primarykey
    data
    text
    <p>I'm facing this issue for quite some time now. I have an EAR deployed in IBM WAS version 7. My application is spring based and it is not logging any spring related info in the console or in the log file.</p> <p>I have verified the following,</p> <ol> <li>log4j.properties is injected as a bean. A log file is getting created as mentioned in the properties file and it logs only the java logging statements not even a single spring log.</li> <li>I have packaged log4j-1.2.14.jar with the application. I have included commons-logging.jar and commons-logging-api.jar along with it (The same issue without the commons jars)</li> <li>We are using ANT as our build tool.</li> </ol> <p>Can anyone guide me where Iam going wrong?</p> <p>Here is my log4j.properties file:</p> <pre><code>log4j.rootLogger=ALL, console, File </code></pre> <h1>Console Appender</h1> <p>log4j.appender.console=org.apache.log4j.ConsoleAppender log4j.appender.console.layout=org.apache.log4j.PatternLayout log4j.appender.console.layout.ConversionPattern=[%5p] [%t %d{hh:mm:ss}] %X{traceID}-(%F:%M:%L) %m%n</p> <h1>Rolling File Appender</h1> <p>log4j.appender.File=org.apache.log4j.RollingFileAppender log4j.appender.File.maxFileSize=10000KB log4j.appender.File.maxBackupIndex=20 log4j.appender.File.File=C:\logs\new\app.log log4j.appender.File.layout=org.apache.log4j.PatternLayout log4j.appender.File.layout.ConversionPattern=%d{ISO8601} | %-5p | %c | %X{traceID} | %t | %m%n log4j.appender.File.ImmediateFlush=true log4j.appender.File.Append=true</p> <h1>Custom assignments</h1> <p>log4j.logger.endpoint=DEBUG,console,File log4j.logger.controller=DEBUG,console,File log4j.logger.handler=DEBUG,console,File</p> <h1>Disable additivity</h1> <p>log4j.additivity.endpoint=false log4j.additivity.controller=false log4j.additivity.handler=false log4j.additivity.dao=false log4j.additivity.loggingInterceptor=false</p> <h1>log4j.additivity.org.springframework=false</h1>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USpaary
    1. USpaary
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POSpring logs missing in WAS7
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSpring logs missing in WAS7
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI think, the problem would be most likely with the appender and log level.
      singulars
      1. POSpring logs missing in WAS7
      1. USAbhijith Nagarajan
    2. COI have added the my log4j config file entry in my post.
      singulars
      1. POSpring logs missing in WAS7
      1. USpaary
    3. COIs it WAS Base or WAS Network Deployment? The latter "steals" some logs. To see them, check the WAS logging configuration and look at its log files instead of the application log file.
      singulars
      1. POSpring logs missing in WAS7
      1. USpkalinow
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload