Multiple log files using Log4j

Hello,
I want to generate log files based on package structure. Like com.temp.test in test.log ,also I am having a log file at application like app.log .
This is my requirement what has been logged in test.log should not be logged in app.log.This is my log4j.properties file.
# Log4j configuration file.
# Available levels are DEBUG, INFO, WARN, ERROR, FATAL
# Default logger
log4j.rootLogger=DEBUG, PFILE
log4j.logger.com.temp.test=DEBUG,TEST
# PFILE is the primary log file
log4j.appender.PFILE=org.apache.log4j.RollingFileAppender
log4j.appender.PFILE.File=./App.log
log4j.appender.PFILE.MaxFileSize=5120KB
log4j.appender.PFILE.MaxBackupIndex=10
#log4j.appender.PFILE.Threshold=DEBUG
log4j.appender.PFILE.layout=org.apache.log4j.PatternLayout
log4j.appender.PFILE.layout.ConversionPattern=%p %d[%l][%C] %m%n
#log4j.appender.PFILE.layout.ConversionPattern=%p %d %m%n
log4j.appender.TEST=org.apache.log4j.RollingFileAppender
log4j.appender.TEST.File=./test.log
log4j.appender.TEST.MaxFileSize=5120KB
log4j.appender.TEST.MaxBackupIndex=10
log4j.appender.TEST.layout=org.apache.log4j.PatternLayout
log4j.appender.TEST.layout.ConversionPattern=%p %d[%l][%C] %m%n
Can u help me!!!

You have to configure the temp logger so that it does not send its info on to the root logger.
For this, you can use the additivity flag.
# Default logger
log4j.rootLogger=DEBUG, PFILE
log4j.additivity.com.temp.test=false
log4j.logger.com.temp.test=DEBUG,TESTThe rest of the file remains the same.

Similar Messages

Any Tutorial / Sample to create Single PDF from multiple source files using PDF assembler in a watched folder process.

Any Tutorial / Sample to create Single PDF from multiple source files using PDF assembler in a watched folder process. I have a client application which will prepare number of source files and some meta data information (in .XML) which will be used in header/footer. Is it possible to put a run time generated DDX file in the watch folder and use it in Process. If possible how can I pass the file names in the DDX. Any sample Process will be very helpful.

If possible, make use of Assembler API in your client application instead of doing this using watched folder. Here are the Assembler samples : LiveCycle ES2.5 * Programming with LiveCycle ES2.5
Watched folder can accept zip files (sample : Configuring a watched folder to handle multiple input files and write results to a single folder | Adobe LiveCycle Blog ). You can also use execute script to create the DDX at runtime : LiveCycle ES2 * Application Development Using LiveCycle Workbench ES2
Thanks
Wasil

Display data in log file using PL/SQL procedure

Just as srw.message is used in Oracle RDF Reports to display data in log file in Oracle Apps, similarly how it is possible to display data in log file using PL/SQL procedure?
Please also mention the syntax too.

Pl post details of OS, database and EBS versions.
You will need to invoke the seeded FND_LOG procedure - see previous discussions on this topic
Enable debug for pl/sql
https://forums.oracle.com/forums/search.jspa?threadID=&q=FND_LOG&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
HTH
Srini

How to write to log files using java files from JSP

Anybody knows different options in writing to log files using JSP?

Do you have an example?in the init() method of the servlet put the following
        FileOutputStream out = new FileOutputStream("your-log-file");
        PrintStream ps = new PrintStream(out);
        System.setOut(ps);
        System.setErr(ps);load the servlet on startup using <load-on-startup> in web.xml

Export to PDF - Can a single report (rpt file) create multiple PDF files using the export command?

Post Author: markeyjd2
CA Forum: Exporting
Greetings forum members,
My question is, in its entirety: Can a single report (rpt file) create multiple PDF files using the export command, ideally one PDF file per DB record?
In my case; I have a Crystal Report that reads data from a DB table containing ~ 500 records. When I export the report to a PDF file, I get one PDF file, with ~ 500 pages.
What I would like to do is export the report to ~ 500 individual PDF files; One file per DB record. The file names would be based on the table's primary key.
Is this possible?

Post Author: Micha
CA Forum: Exporting
Hi,
you need some lines of code, but its easy. Dependend on how to start the generation of your 500 PDFs, you can write an ASP page and start it via Web Browser, or a Windows Script and start it via scheduled job...
Here's an abstract of the ASP code I use:
First, you create a recordset (here: "rsc") which gives you the list of ID fields you want to export, then you create CrystalRuntime.Application object, then you loop through the recordset, open your report (here: "oRpt") and set login info. Then set the selectionformula, so that the report displays only the data of the current ID, e.g.:
oRpt.RecordSelectionFormula = "(" & oRpt.RecordSelectionFormula & ") AND {myTab.myVal}=" & rsc("myVal")
Then you export the report, move to the next record in recordset, and repeat the loop until recordset.EOF. Then you close recordset and connection.
Micha

How can I log BT device IDs names in a log file using Toshiba BT stack

Hi,
without Microsoft stack I can't use a lot of freeware programs (BluetoothView.exe, BluetoothCL.exe, BTScanner for Windows) to "catch" bluetooth devices in a log file.
How can I log bt device ids/description names in a log file using Toshiba Bluetooth stack?
Thank you

I've just contacted Toshiba here:
http://aps2.toshiba-tro.de/bluetooth/?page=faq/sdk
There are other solutions for Windows XP or Toshiba SDK is the only one?

Getting empty log files with log4j and WebLogic 10.0

Hi!
I get empty log files with log4j 1.2.13 and WebLogic 10.0. If I don't run the application in the application server, then the logging works fine.
The properties file is located in a jar in the LIB folder of the deployed project. If I change the name of the log file name in the properties file, it just creates a new empty file.
What could be wrong?
Thanks!

I assume that when you change the name of the expected log file in the properties file, the new empty file is that name, correct?
That means you're at least getting that properties file loaded by log4j, which is a good sign.
As the file ends up empty, it appears that no logger statements are being executed at a debug level high enough for the current debug level. Can you throw in a logger.error() call at a point you're certain is executed?

Open multiple pdf files using Acrobat Reader?

Can we open and switch between multiple pdf files using Acrobat Reader?

Of course, but if it's Reader X or later each file will appear in its own window. This can't be changed.

Can I monitor a Log file using EMGC 10.2.0.2?

Hi,
I am thinking of monitoring my web application log file using EMGC by creating a generic service is that possible. Now we are using some shell scripts to do that but its bit difficult to maintain all these shell scripts on each of the host. Is there any in built in mechanism that enable me to monitor the log file and when a perticular pattern match I would like to send a email notification to concerned people say application admins if there is no out of box option for this do we have plugins to do this. please let me know the possibility of implementing this using EMGC or extencibility plug-ins.
Ashok Chava.

Hi,
I have used "Log File Pattern Matched Line Count" of host to monitor the log files and below is the pattern I have defined for the log file. But i could not find any alerts even there are so many such exceptions in the log file matching the patteren given in EMGC.
/u01/app/oracle/product/IAS904/sysman/log/emias.log;%oracle.sysman.emSDK.util.jdk.EMException;%
I have even add the log file in agent_home/sysman/config/lfm_ifiles file as given in the documentation but I could not see any alerts as expected am I doint anything wrong in my setup.
Please let me know.
Thanks,
Ashok Chava

Unable to remove *.log files using utl_file.fremove

Hi,
I want to remove .log files using the below command
I want to remvoe all the *.log files but its remvoing only one .log file
utl_file.fremove(location => dir_name, filename => log_file_name);
Any help will be needful for me

In the documentation for your unknown version of oracle you can view the definition of utl_file.fremove.
Everywhere it states utl_file.fremove removes a file, not 1 or more, and the documentation doesn't discuss the use of wildcards.
It seems like the question could have been prevented by reading docs (which almost no one here does), and you need to use Java to address your requirement.
Personally I wouldn't misuse Oracle to perform O/S tasks.
Sybrand Bakker
Senior Oracle DBA

Multiple deployed modules using log4j log to same file

We have deployed two modules in ias 6.5 Solaris - moduleA and moduleB. Each of these modules uses log4j to write to a log file - logA and logB. Each module includes logj4.jar in it's WEB-INF/lib directory and the classes are unzipped upon deployment into an org/apache/log4j directory under each module.
Upon app server startup, neither module is loaded. A request is sent to /NASApp/moduleA. logA is written to as the module is initialized. A request is then sent to /NASApp/moduleB. logB is written to as the module in initialized. A request is then sent to /NASApp/moduleA again. This request should be logged in logA but is instead written to logB.
This happened in ias 6.0 sp3 as well as ias 6.5.
An attempt to determine the source of the problem:
The /APPS/modules/moduleB/WEB-INF/lib/org/apache/log4j directory was removed. This should cause ClassNotFoundExceptions to be thrown when attempts are made to write to log4j from moduleB. The appserver is first stopped, then killed, then started again - neither module is loaded. A request is sent to /NASApp/moduleA. logA is written to as the module is initialized. A request is then sent to /NASApp/moduleB - a request that should result in ClassNotFoundExceptions being thrown because the log4j classes are no longer present in the module's classpath. Instead, logB is written and everything behaves as was described above.
Based on this test, we believe that the root of this problem is once again a class loader issue. Apparently, the log4j classes are being loaded by a class loader that is shared between both moduleA and moduleB. Normally this would not cause a problem, but in the case of log4j, the target log file is being overwritten and causes the log entries to be shared between the two modules.
What must we do to remedy this problem? At present, the only fix we know will work is to run a separate appserver instance for each module - a solution that is not acceptable due to the amount of resources consumed by all of the deployed code.

Hi,
You are correct it is a classloader problem, in sp4/6.5 you have a separate classloader for each module (war/jar) but all the helping classes inside modules share a single classloader, that's why even after deleting the helping files from ModuleB it was working.
The remedy to your problem is to create ear module out of those ModuleA and ModuleB and put the helping jar files in both of the ear modules. For ias an ear file is an J2EE application and a separate classloader instance is dedicated to it, it holds true for all the helping classes in the ear module too and the helping classes in two J2EE application (ear module) no longer share the classloader.
I hope it will solve your problem. For further information regarding classloaders please visit Classloader runtime hierarchy.
Please feel free to ask further questions.
Sanjeev,
Developer Support, Sun ONE Application Server-India.

Very weird issue with server logging when using log4j.properties file

I'm using log4j logging. In log4j.properties the root logger is set up to use the ServerLoggingAppender class so that all our application logs go to the main server logfile. In addition, there are several appenders defined for specific components, with output going to specific per-component log files. Everything is going fine until I launch the server console. At this point all of those per-component log files get wiped out (zero length) and some non-ASCII lines are written to at least one of these files, after which the logs appear to be fine. The main server log file does not appear to be affected (because the root logger is set to "warn" level, while component-specific loggers are set to trace, the contents in these files is different; however I tried disabling all the other appenders and turning the root logger up to trace, and that still did not re-create the problem in the main server log file.
And here's the really weird part -- if I use the same configuration, but in a log4j.xml file, the problem does not happen.

Figured it out.
We were passing in the configuration for log4j as -Dlog4j.configuration=file:/<properties file> and this was added to the command line for both the managed and admin servers. Problem is that the console app starts its own instance of log4j, and when it reads the configuration for the appenders it initializes or rolls over the files. At some point we have two JVMs accessing the same files, so some corruption is bound to happen.
I'm not clear why the .xml file made a difference, but earlier we had been passing the log4j configuration as a jar file placed in the domain/lib folder, so perhaps the designer reverted to that (placed the log4j.xml file in a jar in lib, and not simply changed the -Dlog4j.configuration=file:/ option.

Why multiple log files are created while using transaction in berkeley db

we are using berkeleydb java edition db base api, we have already read/write CDRFile of 9 lack rows with transaction and
without transaction implementing secondary database concept the issues we are getting are as follows:-
with transaction----------size of database environment 1.63gb which is due to no. of log files created each of 10 mb.
without transaction-------size of database environment 588mb and here only one log file is created which is of 10mb. so we want to know how REASON CONCRETE CONCLUSION ..
how log files are created and what is meant of using transaction and not using transaction in db environment and what are this db files db.001,db.002,_db.003,_db.004,__db.005 and log files like log.0000000001.....plz reply soon

we are using berkeleydb java edition db base api, If you are seeing __db.NNN files in your environment root directory, these are environment's shared region files. And since you see these you are using Berkeley DB Core (with the Java/JNI Base API), not Berkeley DB Java Edition.
with transaction ...
without transaction ...First of all, do you need transactions or not? Review the documentation section called "Why transactions?" in the Berkeley DB Programmer's Reference Guide.
without transaction-------size of database environment 588mb and here only one log file is created which is of 10mb.There should be no logs created when transactions are not used. That single log file has likely remained there from the previous transactional run.
how log files are created and what is meant of using transaction and not using transaction in db environment and what are this db files db.001,db.002,_db.003,_db.004,__db.005 and log files like log.0000000001Have you reviewed the basic documentations references for Berkeley DB Core?
- Berkeley DB Programmer's Reference Guide
in particular sections: The Berkeley DB products, Shared memory regions, Chapter 11. Berkeley DB Transactional Data Store Applications, Chapter 17. The Logging Subsystem.
- Getting Started with Berkeley DB (Java API Guide) and Getting Started with Berkeley DB Transaction Processing (Java API Guide).
If so, you would have had the answers to these questions; the __db.NNN files are the environment shared region files needed by the environment's subsystems (transaction, locking, logging, memory pool buffer, mutexes), and the log.MMMMMMMMMM are the log files needed for recoverability and created when running with transactions.
--Andrei

Problem with java.util.logging - write to multiple log files

Hi guys,
I'm having trouble with logging to multiple files - i am using the constructor for creating multiple files with size limitation - FileHandler(String pattern, int limit, int count, boolean append).
The problem i encounter is that it writes to the next log file before exceeding the limit, can it be because of file lock or something? what can i do in order to fill log files in a given limit and then write to the next?

I thought it is synchronized by definition - i'm just creating loggers that write to
the same file(s). When i used 1 file instead of using the limit and several
files - all went well.Just a small question: all these loggers do use the same FileHandler don't they?
I bet they do, just asking ...
The problem started when i wanted each file to reach a limit before start writing
to a new file. Should i synchronize the log somehow? That's what I suggested in my previous reply, but IMHO it shouldn't be necessary
given what I read from the sources ...
What could be the reason for not reaching the limit before opening a new file?Sorry I don't have an answer (yet), still thinking though ... it's a strange problem.
kind regards,
Jos (hrrmph ... stoopid problem ;-)

Unused log file using FileHandler for two Logger

Hi,
I'm having some troubles with the using java.util.logging classes. To demontrate my problem I prepared the following code:
package org.prove.system;
import java.util.logging.Logger;
public class Child
     private static final Logger LOG = Logger.getLogger("org.prove.system");
     public static void main(String[] args)
          Child.LOG.info("I'm ready too!!!");
package org.prove.logging;
import java.io.IOException;
import java.util.logging.FileHandler;
public class ParentFileHandler extends FileHandler {
     public ParentFileHandler() throws IOException, SecurityException {
          super();
package org.prove.logging;
import java.io.IOException;
import java.util.logging.FileHandler;
public class ChildFileHandler extends FileHandler {
     public ChildFileHandler() throws IOException, SecurityException {
          super();
}and the following is the configuration inside my logging.properties file
# Loggers configuration
org.prove.handlers = org.prove.logging.ParentFileHandler
org.prove.level = ALL
org.prove.useParentHandlers = false
org.prove.system.handlers = org.prove.logging.ChildFileHandler
org.prove.system.level = ALL
org.prove.logging.ParentFileHandler.pattern = %h/logs/Parent.%u.log
org.prove.logging.ParentFileHandler.formatter = java.util.logging.SimpleFormatter
org.prove.logging.ParentFileHandler.append = true
org.prove.logging.ChildFileHandler.pattern = %h/logs/Child.%u.log
org.prove.logging.ChildFileHandler.formatter = java.util.logging.SimpleFormatter
org.prove.logging.ChildFileHandler.append = trueNow, if you try my example you can find, inside the "logs" directory specified in the configuration file, some files:
- Child.0.log, which is the file for the org.prove.logging.ChildFileHandler;
- Parent.0.log, which is the file for the org.prove.logging.ParentFileHandler.
but you can also find:
- Parent.1.log;
- Parent.1.log.lck.
In particular the last two files are generated by the initialization of the org.prove.logging.ParentFileHandler, because inside the method addLogger of the LogManager class, after the initialization of the demanded logger there is a cycle to identify the parent of the logger itself.
Inside that cycle is invoked again the method demandLogger that, if not already initialized, creates the Logger, and after instantiates the handlers of that logger, generating the Parent.1.log and its lock file Parent.1.log.lck. This files are not used and at the end of the execution the lock file is not deleted as the others.
I hope my problem is clear and someone can help me to identify how to resolve it.
Thanks in advance
Alessandro Cristiani

It is not possible to redirect the two different type of logs by using same log level. you have to use to different log levels for both and then in your code you have to mark specifically.
to do this you can use log levels ERROR (for exceptions) and FATAL (for errors).
First define your own logger class that will be using the log4j API's
import org.apache.log4j.Logger;
public class MyLogger {
   static Logger log = Logger.getLogger(MyLogger.class);
   public static logThrowable(Throwable th){
       if(th instanceof Exception) {
          log.error(th.getMessage());
       } else {
           log.fatal(th.getMessage());
}and for your log4j.xml
change the level for your ERROR_FILE to FATAL
in your LogExample
remove:
static Logger log = Logger.getLogger(LogExample.class);change:
}catch(Exception e){
log.error("Exception e");
}to
}catch(Throwable e){
MyLogger.logThrowable(e);
}Hope this helps. Or if you do not want to do in this way then you can also create your own log levels. It is not advisable but you can certainly do that.
Please visit [Log4j Manual|http://logging.apache.org/log4j/1.2/manual.html] for more on this.

Multiple log files using Log4j

Similar Messages

Maybe you are looking for