Logging API: Java 1.5 logs a lot in FINE, etc.

I noticed that my application log contains a lot more entries since I use Java 1.5 when I log fine/finer/finest messages. I tried to workaround this by just change the log levels of my loggers (by inspecting the logger name prefixes). But the Java messages still log:
     * Set level for all registered loggers of the LogManager.
     * @param level New level to set.
     * @param prefix Optional prefix string for loggers to consider.
    static public void setGlobalLevel(Level level, String prefix) {
        if (level != null) {
            LogManager logManager = LogManager.getLogManager();
            if (logManager != null) {
                Enumeration<String> enu = logManager.getLoggerNames();
                boolean first = true;
                while (enu.hasMoreElements()) {
                    String loggerName = enu.nextElement();
                    if (prefix == null || loggerName.startsWith(prefix)) {
                        Logger logger = logManager.getLogger(loggerName);
                        if (logger != null) {
                            logger.setLevel(level);
                        }//else: logger unavailable
                        if (first) {
                            logger.log(Level.CONFIG, "Global log level changed to "+level);
                            first = false;
                }//next logger
            }//else: LogManager unavailable
        }//else: level unavailable
    }//setGlobalLevel()

Okay, I try to explain it differently. SInce Java 1.5, why I log messages with level FINE, FINER, or FINEST, I get lots of additional entries like:
2005-04-19 13:13:22.076 FINER focus owner is javax.swing.JButton[,12,97,161x33,alignmentX=0.0,alignmentY=0.5,border=javax.swing.plaf.BorderUIResource$CompoundBorderUIResource@19d3b3a,flags=424,maximumSize=,minimumSize=,preferredSize=,defaultIcon=javax.swing.ImageIcon@19050a0,disabledIcon=,disabledSelectedIcon=,margin=javax.swing.plaf.InsetsUIResource[top=2,left=14,bottom=2,right=14],paintBorder=true,paintFocus=true,pressedIcon=,rolloverEnabled=false,rolloverIcon=,rolloverSelectedIcon=,selectedIcon=,text=Log-Datei,defaultCapable=true] [java.awt.focus.KeyboardFocusManager]
2005-04-19 13:13:22.076 FINER >>> java.awt.event.KeyEvent[KEY_PRESSED,keyCode=18,keyText=Alt,keyChar=Undefined keyChar,modifiers=Alt,extModifiers=Alt,keyLocation=KEY_LOCATION_LEFT] on frame0 [java.awt.focus.KeyboardFocusManager]
2005-04-19 13:13:22.404 FINER focus owner is javax.swing.JButton[,12,97,161x33,alignmentX=0.0,alignmentY=0.5,border=javax.swing.plaf.BorderUIResource$CompoundBorderUIResource@19d3b3a,flags=424,maximumSize=,minimumSize=,preferredSize=,defaultIcon=javax.swing.ImageIcon@19050a0,disabledIcon=,disabledSelectedIcon=,margin=javax.swing.plaf.InsetsUIResource[top=2,left=14,bottom=2,right=14],paintBorder=true,paintFocus=true,pressedIcon=,rolloverEnabled=false,rolloverIcon=,rolloverSelectedIcon=,selectedIcon=,text=Log-Datei,defaultCapable=true] [java.awt.focus.KeyboardFocusManager]
2005-04-19 13:13:22.404 FINER >>> java.awt.event.KeyEvent[KEY_RELEASED,keyCode=9,keyText=Tabulator,keyChar=Tabulator,modifiers=Alt,extModifiers=Alt,keyLocation=KEY_LOCATION_STANDARD] on frame0 [java.awt.focus.KeyboardFocusManager]
2005-04-19 13:13:22.716 FINER focus owner is javax.swing.JButton[,12,97,161x33,alignmentX=0.0,alignmentY=0.5,border=javax.swing.plaf.BorderUIResource$CompoundBorderUIResource@19d3b3a,flags=424,maximumSize=,minimumSize=,preferredSize=,defaultIcon=javax.swing.ImageIcon@19050a0,disabledIcon=,disabledSelectedIcon=,margin=javax.swing.plaf.InsetsUIResource[top=2,left=14,bottom=2,right=14],paintBorder=true,paintFocus=true,pressedIcon=,rolloverEnabled=false,rolloverIcon=,rolloverSelectedIcon=,selectedIcon=,text=Log-Datei,defaultCapable=true] [java.awt.focus.KeyboardFocusManager]
2005-04-19 13:13:22.716 FINER >>> java.awt.event.KeyEvent[KEY_RELEASED,keyCode=18,keyText=Alt,keyChar=Undefined keyChar,keyLocation=KEY_LOCATION_LEFT] on frame0 [java.awt.focus.KeyboardFocusManager]
2005-04-19 13:13:22.732 FINE >>> java.awt.event.WindowEvent[WINDOW_LOST_FOCUS,opposite=null,oldState=0,newState=0] on frame0 [java.awt.focus.KeyboardFocusManager]
2005-04-19 13:13:22.732 FINE java.awt.event.WindowEvent[WINDOW_LOST_FOCUS,opposite=null,oldState=0,newState=0] on frame0 [java.awt.focus.DefaultKeyboardFocusManager]
2005-04-19 13:13:22.732 FINE Active de.icomps.prt.gui.ClientReportPrinterConsole[frame0,110,46,1140x794,invalid,layout=java.awt.BorderLayout,title=iComps Client Report Printer 1.1.6,resizable,normal,defaultCloseOperation=DO_NOTHING_ON_CLOSE,rootPane=javax.swing.JRootPane[,4,23,1132x767,layout=javax.swing.JRootPane$RootLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=16777673,maximumSize=,minimumSize=,preferredSize=],rootPaneCheckingEnabled=true], Current focused de.icomps.prt.gui.ClientReportPrinterConsole[frame0,110,46,1140x794,invalid,layout=java.awt.BorderLayout,title=iComps Client Report Printer 1.1.6,resizable,normal,defaultCloseOperation=DO_NOTHING_ON_CLOSE,rootPane=javax.swing.JRootPane[,4,23,1132x767,layout=javax.swing.JRootPane$RootLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=16777673,maximumSize=,minimumSize=,preferredSize=],rootPaneCheckingEnabled=true], losing focus de.icomps.prt.gui.ClientReportPrinterConsole[frame0,110,46,1140x794,invalid,layout=java.awt.BorderLayout,title=iComps Client Report Printer 1.1.6,resizable,normal,defaultCloseOperation=DO_NOTHING_ON_CLOSE,rootPane=javax.swing.JRootPane[,4,23,1132x767,layout=javax.swing.JRootPane$RootLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=16777673,maximumSize=,minimumSize=,preferredSize=],rootPaneCheckingEnabled=true] opposite null [java.awt.focus.DefaultKeyboardFocusManager]
2005-04-19 13:13:22.732 FINE >>> java.awt.event.FocusEvent[FOCUS_LOST,temporary,opposite=null] on javax.swing.JButton[,12,97,161x33,alignmentX=0.0,alignmentY=0.5,border=javax.swing.plaf.BorderUIResource$CompoundBorderUIResource@19d3b3a,flags=424,maximumSize=,minimumSize=,preferredSize=,defaultIcon=javax.swing.ImageIcon@19050a0,disabledIcon=,disabledSelectedIcon=,margin=javax.swing.plaf.InsetsUIResource[top=2,left=14,bottom=2,right=14],paintBorder=true,paintFocus=true,pressedIcon=,rolloverEnabled=false,rolloverIcon=,rolloverSelectedIcon=,selectedIcon=,text=Log-Datei,defaultCapable=true] [java.awt.focus.KeyboardFocusManager]
2005-04-19 13:13:22.732 FINE java.awt.event.FocusEvent[FOCUS_LOST,temporary,opposite=null] on javax.swing.JButton[,12,97,161x33,alignmentX=0.0,alignmentY=0.5,border=javax.swing.plaf.BorderUIResource$CompoundBorderUIResource@19d3b3a,flags=424,maximumSize=,minimumSize=,preferredSize=,defaultIcon=javax.swing.ImageIcon@19050a0,disabledIcon=,disabledSelectedIcon=,margin=javax.swing.plaf.InsetsUIResource[top=2,left=14,bottom=2,right=14],paintBorder=true,paintFocus=true,pressedIcon=,rolloverEnabled=false,rolloverIcon=,rolloverSelectedIcon=,selectedIcon=,text=Log-Datei,defaultCapable=true] [java.awt.focus.DefaultKeyboardFocusManager]
2005-04-19 13:13:22.732 FINE java.awt.event.FocusEvent[FOCUS_LOST,temporary,opposite=null] on javax.swing.JButton[,12,97,161x33,alignmentX=0.0,alignmentY=0.5,border=javax.swing.plaf.BorderUIResource$CompoundBorderUIResource@19d3b3a,flags=424,maximumSize=,minimumSize=,preferredSize=,defaultIcon=javax.swing.ImageIcon@19050a0,disabledIcon=,disabledSelectedIcon=,margin=javax.swing.plaf.InsetsUIResource[top=2,left=14,bottom=2,right=14],paintBorder=true,paintFocus=true,pressedIcon=,rolloverEnabled=false,rolloverIcon=,rolloverSelectedIcon=,selectedIcon=,text=Log-Datei,defaultCapable=true] [java.awt.focus.Component]
2005-04-19 13:13:22.732 FINE >>> java.awt.event.WindowEvent[WINDOW_DEACTIVATED,opposite=null,oldState=0,newState=0] on frame0 [java.awt.focus.KeyboardFocusManager]
2005-04-19 13:13:22.732 FINE java.awt.event.WindowEvent[WINDOW_DEACTIVATED,opposite=null,oldState=0,newState=0] on frame0 [java.awt.focus.DefaultKeyboardFocusManager]
2005-04-19 13:13:22.748 FINER Setting global active window to null, old active de.icomps.prt.gui.ClientReportPrinterConsole[frame0,110,46,1140x794,invalid,layout=java.awt.BorderLayout,title=iComps Client Report Printer 1.1.6,resizable,normal,defaultCloseOperation=DO_NOTHING_ON_CLOSE,rootPane=javax.swing.JRootPane[,4,23,1132x767,layout=javax.swing.JRootPane$RootLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=16777673,maximumSize=,minimumSize=,preferredSize=],rootPaneCheckingEnabled=true] [java.awt.focus.KeyboardFocusManager]
2005-04-19 13:13:22.748 FINE >>> java.awt.event.FocusEvent[FOCUS_LOST,permanent,opposite=null] on frame0 [java.awt.focus.KeyboardFocusManager]
So, I try just to set the levels FINE, FINER, FINEST for my applications loggers that all have logger names being the Java package name and class name (e.g. "one.two.three.MyClass"). So, I change the levels of all logers who's lagger name starts with "one.two.three". That should lead to log messages of FINE/FINER/FINEST from my loggers. But I still get the log messages of Java internal loggings like
>>> java.awt.event.FocusEvent[FOCUS_LOST,permanent,opposite=null] on frame0
from java.awt.focus.KeyboardFocusManager.

Similar Messages

Customize Java logging API

Want to customize java.util.logging api, like write message to message queue, xml file, etc. Would you guys give me some useful suggestion or resource or link? Thanks.

Just write a sub-class of Handler such as this:
public class JMSHandler extends Handler {
}Look into the JDK source code such as MemoryHandler and StreamHandler on how to implement it.

Practical use of Java Logging API

There was a recent technical tip about the Java Logging API, but after reading it I still don't understand how to use it in a real situation.
Can anyone help me with this with a practical example?
At the moment I have try-catch clauses that catch exceptions and print a message in a System.err log that I can consult if there's a specific problem.
How should I be using the Logging API? I feel sure that it can help me, but can't see how.
Thanks for any practical information.

What if you don't want to write to system.err anymore? What if you need to write something to the windows event log? What if system.err is irrelevant (nt service), ...
Btw, lots of examples on the JDK1.4 logging api:
http://www.esus.com/docs/GetIndexPage.jsp?uid=265

Java logging API (1.4) -- where's the file?

Where on God's green earth does the log file get written to?
I am doing some very simple code:
import java.util.logging.*;
public class SimpleLogging {
   static Logger jcfeLog = Logger.getLogger("test1");
   static Logger sampleLog = Logger.getLogger("test2");
   public static void main(String [] args)
      jcfeLog.warning("sample warning");
      sampleLog.log(Level.INFO, "sample info entry");
      byte[] moreInfo = new byte[10];
      //fill moreInfo with some binary info
      jcfeLog.log(Level.FINEST, "Some obscure event", new Object[]{moreInfo});
} doesn't get much simpler, plus I am using the default properties file. I get the console output but simply cannot find the log file anywhere on my system. Just for kicks, here is the config entry for the file:
java.util.logging.FileHandler.pattern =%t/java%u.logmy understanding is that it should go to the temp directory?
also, why aren't the specs for the config file listed anywhere, all these %t, %u, etc.....????

The FileHandler API gives the meaning for the % symbols.
http://java.sun.com/j2se/1.4/docs/api/java/util/logging/FileHandler.html
Your pattern indicates that the file should be put in the system's temp directory, with the file name java###.log.
Maybe you should try calling the addHandler method on your Loggers, and add a FileHandler to write the messages to that file.

Problem with java logging API

Hi there
It`s the first time I`m using (I have to use) the standard java logging API.
My need is to integrate it in an existing web-application based on struts.
So my first step was to include the following code into an Struts Action-class:
FileHandler file = new FileHandler("/pathToLogFile/myLogFile.log",true);
file.setFormatter(new SimpleFormatter());
logger.info("create info");
By intention is to have exactly one log-file for the whole application, but indeed I'm getting multiple log-files, even for each request of one and the same Action/Servlet class, like
myLogFile.log
myLogFile.log.1
myLogFile.log.2
myLogFile.log.3
Why does using append=true not work in the constructor of "FileHandler"
Do I have to close the FileHandler each time I've used it?
Is this a known issue?
Thanks for any responds!

@ Stone.li
First, thanks for your answer.
perhaps my question was quite confusing .... but my need is just
to establish the logging API in an existing Web-Application and to have exactly one log-file for the whole application. This means I would have to provide in each servlet a FileHandler referencing to the log-file. I thought it would be part of the job of the logging API to synchronise this file access.

Logging api hangs

Im starting a java application from an applet calling Runtime.getRuntime().exec("java bla bla bla")
Worked fine until I implemented Java 1.4 logging api. Now the application hangs after writing a few info lines to a FileHandler log. It's clearly the logger that hangs because if I set log level = OFF the the program runs just fine.
Has anyone seen anything similar?
* To make it harder to debug, the problem only occurs when starting the application from an applet.

That might happen that spawn process generates lots of output.
Runtime.getRuntime().exec() returns object of type java.lange.Process. That object provide access to the stdout and stderror of the newly created process. If those streams are not cleaned properly then process will hang as soon as OS buffers of those stdout and stderr streams get full.
One way to work around it just read output from the process and throw it away. You can try using something like this:
package com.xxx;
import java.io.InputStream;
public class ProcessOutputWaster {
    public ProcessOutputWaster(Process process)
        throws Exception {
        createWorker(process.getErrorStream()).start();
        createWorker(process.getInputStream()).start();
    protected Worker createWorker(InputStream is) {
        return new Worker(is);
    protected static class Worker
              extends Thread {
        private InputStream inputStream_;
        public Worker(InputStream inputStream) {
            inputStream_ = inputStream;
        public void run() {
            if (getInputStream() != null) {
                try {
                    byte[] buffer = new byte[1024];
                    int read;
                    while(true) {
                        read = inputStream_.read(buffer);
                        if (read < 0)
                           break;
                catch(Exception ex) {
                    Handle the error some how. E.g. show the error box.
Process process = Runtime.getRuntime().exec(strCommand);
ProcessOutputWaster outputWaster = new ProcessOutputWaster(process);

Is this logging code faster than using a standard logging API like log4J

is this logging code faster than using a standard logging API like log4J or the logging API in java 1.4
As you can see my needs are extremely simple. write some stuff to text file and write some stuff to dos window.
I am thinking about using this with a multi threaded app. So all the threads ~ 200 will be using this simultaneously.
* Tracer.class logs items according to the following criteria:
* 2 = goes to text file Crawler_log.txt
* 1 = goes to console window because it is higher priority.
* @author Stephen
* @version 1.0
* @since June 2002
import java.io.*;
import java.net.*;
import java.util.*;
import java.text.*;
class Tracer{
public static void log(int traceLevel, String message, Object value)
if(traceLevel == 1){
System.out.println(getLogFileDate(new Date()) +" >" + message+ " value = " + value.toString()););
}else{
pout.write(getLogFileDate(new Date()) +" >" + message + " value = " + value.toString());
pout.flush();
public static void log(int traceLevel, String message )
if(traceLevel == 1){System.out.println(message);
}else{
pout.write(message ) ;
pout.flush();
//public static accessor method
public static Tracer getTracerInstance()
return tracerInstance;
private static String getLogFileDate(Date d )
String s = df.format(d);
String s1= s.replace(',','-');
String s2= s1.replace(' ','-');
String s3= s2.replace(':','.');
System.out.println("getLogFileDate() = " + s3 ) ;
return s3;
//private instance
private Tracer(){
System.out.println("Tracer constructor works");
df = DateFormat.getDateTimeInstance(DateFormat.MEDIUM, DateFormat.MEDIUM);
date = new java.util.Date();
try{
pout = new PrintWriter(new BufferedWriter(new FileWriter("Crawler_log"+getLogFileDate(new Date())+".txt", true)));
pout.write("**************** New Log File Created "+ getLogFileDate(new Date()) +"****************");
pout.flush();
}catch (IOException e){
System.out.println("**********THERE WAS A CRITICAL ERROR GETTING TRACER SINGLETON INITIALIZED. APPLICATION WILL STOP EXECUTION. ******* ");
public static void main(String[] argz){
System.out.println("main method starts ");
Tracer tt = Tracer.getTracerInstance();
System.out.println("main method successfully gets Tracer instance tt. "+ tt.toString());
//the next method is where it fails - on pout.write() of log method. Why ?
tt.log(1, "HIGH PRIORITY");
System.out.println("main method ends ");
//private static reference
private static Tracer tracerInstance = new Tracer();
private static Date date = null;
private static PrintWriter pout = null;
public static DateFormat df = null;
}

In general I'd guess that a small, custom thing will be faster than a large, generic thing with a lot of options. That is, unless the writer of the small program have done something stupid, og the writer of the large program have done something very smart.
One problem with java in this respect is that it is next to impossible to judge exactly how much machine-level processing a single java statement takes. Things like JIT compilers makes it even harder.
In the end, there is really only one way to find out: Test it.

How to create logs in java if the application stops abruptly,

Hi,
I wrote a java code for handling one of my applications in built commands. Right now iam handling the logs using an arrayList and at the end of my java progem iam writing them to a file.
If the program runs completely then my logs are generated, but my application takes almost 6hours to fully complete.. if ther is anyproblem like service of application stops or any other problem then i have to stop my java code forcefully.. in that case my code is not working ...like iam not able to see that part of my logs.
Help me in writing the logs even if the java code stops in between. or iam stopping it.
Thanks in adcance

You may want to use the "Shotdown hooks" API -- http://java.sun.com/j2se/1.4.2/docs/api/java/lang/Runtime.html#addShutdownHook(java.lang.Thread).

CREATE PDF fails with ALC-PDG-null-Generic Log Message java.lang.OutOfMemoryError

Adobe LiveCycle PDF Generator ES (Version: 8.2.1)
The CREATE PDF service fails. It does not convert word documents to PDF. It used to work earlier. We haven't changed any configuration. The Server.log has the below entries:
2014-01-07 10:18:49,536 INFO [com.adobe.pdfg.GeneratePDFImpl] ALC-PDG-001-000-
Job ID for the submitted createPDF job =BXU004275.docx911bb3-b13cac-ba31d8-1e253f-c932e7-fa2bf0
2014-01-07 10:18:52,176 INFO [com.adobe.pdfg.BMCCaller] ALC-PDG-001-024-BXU004275.docx: Time Job Submitted: 1/7/14 10:18 AM
2014-01-07 10:18:52,458 INFO [com.adobe.pdfg.BMCCaller] ALC-PDG-001-021-BXU004275.docx: PDF Settings Used: pdfg Standard 55865
2014-01-07 10:18:52,458 INFO [com.adobe.pdfg.BMCCaller] ALC-PDG-001-022-BXU004275.docx: Security Settings Used: No Security
2014-01-07 10:18:52,458 INFO [com.adobe.pdfg.BMCCaller] ALC-PDG-001-023-BXU004275.docx: FileType Settings Used: Standard
2014-01-07 10:18:52,458 INFO [com.adobe.pdfg.BMCCaller] ALC-PDG-001-017-BXU004275.docx: Job Submitted by User: administrator
2014-01-07 10:18:52,536 INFO [com.adobe.service.ProcessResource] BMC505: Service PDFMakerSvc: Starting native process with command line "C:\\Adobe\\LiveCycle8.2\\jboss\\server\\all\\svcnative\\PDFMakerSvc\\bin\\dll\\pdfgen.ex e" PDF-PD1936a0002 -beginExecutable "C:\\Java\\jdk1.5.0_14\\jre\\bin\\javaw.exe" -endExecutable -Xmx64m -cp "C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/adobe-appmon.jar;C:/Ado be/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/adobe-appmondata.jar;C:/Adobe/L iveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/adobe-bslj.jar;C:/Adobe/LiveCycle8. 2/jboss/server/all/svcnative/PDFMakerSvc/bin/adobe-csa.jar;C:/Adobe/LiveCycle8.2/jboss/ser ver/all/svcnative/PDFMakerSvc/bin/adobe-generatepdf-client.jar;C:/Adobe/LiveCycle8.2/jboss /server/all/svcnative/PDFMakerSvc/bin/adobe-pdfg-common-jaxb.jar;C:/Adobe/LiveCycle8.2/jbo ss/server/all/svcnative/PDFMakerSvc/bin/adobe-pdfg-common.jar;C:/Adobe/LiveCycle8.2/jboss/ server/all/svcnative/PDFMakerSvc/bin/adobe-pdfg-commonbmc.jar;C:/Adobe/LiveCycle8.2/jboss/ server/all/svcnative/PDFMakerSvc/bin/adobe-pdfg-idl-bmc-websphere.jar;C:/Adobe/LiveCycle8. 2/jboss/server/all/svcnative/PDFMakerSvc/bin/adobe-pdfg-idl-bmc.jar;C:/Adobe/LiveCycle8.2/ jboss/server/all/svcnative/PDFMakerSvc/bin/adobe-utilities.jar;C:/Adobe/LiveCycle8.2/jboss /server/all/svcnative/PDFMakerSvc/bin/avalon-framework-4.1.5.jar;C:/Adobe/LiveCycle8.2/jbo ss/server/all/svcnative/PDFMakerSvc/bin/comfyj-2.4.jar;C:/Adobe/LiveCycle8.2/jboss/server/ all/svcnative/PDFMakerSvc/bin/jacorb.jar;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/ PDFMakerSvc/bin/jaxb-api.jar;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/ bin/jaxb-impl.jar;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/jaxb-li bs.jar;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/jniw2.9.5_acrobat1 .1.jar;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/jniw2.9.5_autocad1 .1.jar;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/jniw2.9.5_autocad2 007.jar;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/jniw2.9.5_excel1. 3.jar;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/jniw2.9.5_pdfmapi1. 0.jar;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/jniw2.9.5_ppt2.6.ja r;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/jniw2.9.5_project4.4.ja r;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/jniw2.9.5_publisher1.0. jar;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/jniw2.9.5_visio4.a.ja r;C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/jniw2.9.5_word8.1.jar;C :/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/jniwrap-3.6.1.jar;C:/Adobe /LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/logkit-1.2.jar;C:/Adobe/LiveCycle 8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/namespace.jar;C:/Adobe/LiveCycle8.2/jboss/s erver/all/svcnative/PDFMakerSvc/bin/PDFMakerConverterServer.jar;C:/Adobe/LiveCycle8.2/jbos s/server/all/svcnative/PDFMakerSvc/bin/winpack-3.6.jar;C:/Adobe/LiveCycle8.2/jboss/server/ all/svcnative/ServicesNatives2/jars/adobe-bslj.jar" com.adobe.native2pdf.bmc.PDFMakerServer -IOR IOR:000000000000002249444C3A636F6D2F61646F62652F736572766963652F4D616E616765723A312E30000 0000000000200000000000000D8000102000000000D31302E32302E3133302E353200000DC8000000134A426F7 3732F42522D312F010000000000000000000000050000000000000008000000004A414300000000010000001C0 000000000010001000000010501000100010109000000010501000100000021000000500000000000000001000 0000000000024000000200000007E00000000000000010000000D31302E32302E3133302E353200000DC900000 0000000000000000000000000000000000000000000000000000000002000000004000000000000001F0000000 400000003000000010000002000000000000000020000002000000004000000000000001F0000000400000003 -AppServer jboss
2014-01-07 10:18:52,567 INFO [STDOUT] Command line '"C:\Java\jdk1.5.0_14\jre\bin\javaw.exe"'
2014-01-07 10:18:52,770 INFO [STDOUT] [configuration loaded from classpath resource jar:file:/C:/Adobe/LiveCycle8.2/jboss/server/all/svcnative/PDFMakerSvc/bin/adobe-pdfg-com monbmc.jar!/jacorb.properties]
2014-01-07 10:18:53,942 INFO [com.adobe.native2pdf.bmc.WordToPDFConverter] ALC-PDG-001-001-Begin processing job : C:\Documents and Settings\infodba\Local Settings\Temp\pdfg-infodba\6f\40a5-a1cb14-9618a9-a39550-d1e383-217845\native-in.docx
2014-01-07 10:19:04,925 INFO [com.adobe.pdfg.BMCCaller] ALC-PDG-001-016-BXU004275.docx: Job Type: Convert to PDF
2014-01-07 10:19:04,940 INFO [com.adobe.pdfg.BMCCaller] ALC-PDG-001-027-BXU004275.docx: Job Completion Status: Succeeded
2014-01-07 10:19:04,940 INFO [com.adobe.pdfg.BMCCaller] ALC-PDG-001-025-BXU004275.docx: Time Job Completed: 1/7/14 10:19 AM
2014-01-07 10:19:04,940 INFO [com.adobe.pdfg.BMCCaller] ALC-PDG-001-026-BXU004275.docx: Time of Job Execution: 12,764 ms
2014-01-07 10:19:04,940 INFO [com.adobe.aes.web.create.CreatePDFAct] ALC-PDG-001-018-BXU004275.docx: User Connected from Host: 10.2.113.168/10.2.113.168
2014-01-07 10:19:04,940 INFO [com.adobe.aes.web.create.CreatePDFAct] ALC-PDG-001-029-BXU004275.docx: Job Source: Admin UI
2014-01-07 10:19:05,018 ERROR [com.adobe.aes.web.create.CreatePDFAct] ALC-PDG-null-Generic Log Message
java.lang.OutOfMemoryError
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(FileInputStream.java:194)
at com.adobe.idp.Document.passivateInitData(Document.java:1219)
at com.adobe.idp.Document.passivate(Document.java:1055)
at com.adobe.idp.Document.passivate(Document.java:1012)
at com.adobe.idp.Document.getInputStream(Document.java:1524)
at com.adobe.idp.Document.copyToFile(Document.java:1623)
at com.adobe.aes.web.create.CreatePDFAct.execute(CreatePDFAct.java:192)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at com.adobe.aes.web.AesActionServlet.service(AesActionServlet.java:63)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.adobe.idp.um.auth.filter.AuthenticationFilter.doFilter(AuthenticationFilter.java:154)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.ja va:159)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11P rotocol.java:744)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:595)

Thanks guys for the response..
I checked the IR and the SAP Basis has been added. Here are the details I got.
Name: SAP_BASIS
Version: 700
SWCV: SAP BASIS 7.00
Available Support Packages: 12
Any more suggesions/feedback will be greatly appreciated.
Thanks

Java code for logging from servlet on AS

Hi guys,
I have developed a servlet on SAP AS and I need to log information from processing. Can you please suggest me the best way to do that? I am not an Java expert but when I see the code I'd understand it. Can you please provide some Java logging example code which would work on AS 7.3?
Thanks a lot,
Peter

Hi Peter,
Please have a look of the below logging links/docs
Sample Java Code with Logging - Using Central Development Services - SAP Library
Tracing and Logging - SAPNetWeaver Application Server Java Security Guide - SAP Library
Integrating Third-Party Logging Frameworks into SAP NetWeaver CE
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20ecb0f4-ccb0-2a10-46aa-ceee8895f34b?QuickLink=index&overridelayout=true&25009594565056
Or
You can simply use System.err.println() or System.out.println()
Thanks,
Hamendra

How to set NC Log API

Hi all,
I want to use the following NC log API,but I don't know how to initialize the interface's java object and set the parameter "ApplicationVO".
Interface LogNCApplicationInterface
Method ApplicationVO addNDone(ApplicationVO applicationvo)
Please help me.Thank you!
Qiang Liu

if you just need to log an NC the minimum fields you need to set are the following:
CreateNCRequest ncRequest = new CreateNCRequest();
ncRequest.setActivity("NC500"); // activity where NC is logged - can be any name
ncRequest.setSfcRef(new SFCBOHandle(site, sfcParent).toString());// the SFC for which you are reporting an NC
// ncRequest.setValidateNCCodeOperation(true); // no need to set it, it's true by default
// nc code reference for nc code that is reported
// nc code must exist in the system
ncRequest.setNcCodeRef(new NCCodeBOHandle(site,"NCCODE").toString());
// required custom fields must be set
CreateNCResponse ncResponse = ncPSI.createNC(ncRequest);

Simple logging under Java 1.3.1?

Hi,
I am not able to use Java 1.4 at the moment and so cannot take advantage of
its new logging classes, can anyone point me in the direction of any
tutorials on doing basic transaction logging with 1.3? Is it just a case of
calling a function that opens a file and appends a line to the end of it
every time I want to log something or is there more to it than that?
Richard

there is something critical that you must use 1.4 final release from sun because it contains some modifications of the logging APIs, i found that a book uses an old 1.4 beta 1 logging APIs which changed in 1.4 beta 3 and 1.4.0 final release, and also i found this probelm in one of sun's offecial publications
here is my email : Simon Ritter - Sun UK, i asked him for an explanation
so, you will see the old version of Logging APIs and the NEW one after it, understand this code and use java 1.4.0 docs to learn more, and take care of old version of the new java logging APIs
Date: Mon, 4 Feb 2002 12:14:45 +0000 (GMT)
From: "Simon Ritter - Sun UK" <[email protected]> | Block Address | Add to Address Book
Reply-to: Simon Ritter - Sun UK <[email protected]>
Subject: Re: is Bug or New
To: [email protected]
Mohammad,
thanks for the feedback on the sample code/presentation. I've just
checked the
latest JDK1.4 which is the release candidate made available in the last
couple
of weeks. You are right, they have changed the API for LogManager.
This is the
problem with working at the leading edge and dealing with Beta code. I
will
change my presentation and sample code to reflect the new API
definition.
Regards,
Simon.
Date: Mon, 4 Feb 2002 04:04:04 -0800 (PST)
From: Mohammad Nabil <[email protected]>
Subject: is Bug or New
To: [email protected]
Dear sir,
i downloaded:
Java � 2 Standard Edition
A Tutorial Of New
Features in J2SE v1.4.
on 23.01.2002.
and i have some comments on the Logging APIs.
and also, I hope you tell me some sites from where i
can know more about those new features of J2SDK 1.4.
best regards,
mohammad nabil
Note:
i'm sure you are busy but here is my comments if
you want:
generaly i downloaded a sample chapter of somebook
that uses the following methods in LogManager
void addGlobalHandler(Handler handler)
void removeAllGlobalHandlers()
void removeGlobalHandler(Handler handler)
void setLevel(String namespace, Level level)
which are not exist at all in the
"java.util.logging.LogManager"
also this situation is reported in the Java � 2
Standard Edition A Tutorial Of New Features in J2SE
v1.4 page 7 & 8 of 42
the Tutorial code is:
     import java. util. logging.*;
     try {
          Handler logHandler = new FileHandler(" example.
log");
     } catch (IOException ioe) {
          // Handle exception
     LogManager lm = LogManager. getLogManager();
     lm. addGlobalHandler( logHandler);
     lm. setLevel(" loggerExample", Level. FINEST);
     Logger logger = Logger. getLogger(" loggerExample");
     logger. fine(" User " + loginId + "logged in");
     logger. log( Level. WARNING, "Bad password entered 3
times");
my suggested, which is compiled and working properly,
my code is:
     import java.util.logging.*;
     import java.io.*;
     Handler logHandler = null;
     try {
     logHandler = new FileHandler("d:\\example.log");
//OR     logHandler = new
FileHandler("d:\\example.xml");
//OR     logHandler = new ConsoleHandler();
//OR     logHandler = new SocketHandler(String host,
int port)
     } catch (IOException ioe) {
     // Handle exception
     System.exit(0);
     LogManager lm = LogManager.getLogManager();
     Logger logger = Logger.getLogger("loggerExample");
logger.addHandler(logHandler);
lm.addLogger(logger);
logger.fine(" User " + "loginId" + "logged
in");
logger.log( Level. WARNING, "Bad password
entered 3 times");
     //Now logger is registered in LogManager and we can
get it.
     Logger newLogger = lm.getLogger("loggerExample");
     newLogger.setLevel(Level.WARNING);
// this second logger.fine will not appear in
the file;
logger.fine(" User " + "loginId" + "logged in
again");
newLogger.log( Level. WARNING, "Bad password
entered 3 times again??!!");
>
i hope you tell me if that java tutorial is too new so
i can't find the code in my J2SDK version 1.4
candidate Release "Released from about 2 weeks only",
or that version 1.4 i have is newer than the one used
by tutorial.
thanks.
hope this help

Setting Logging API config file

Hi,
Is there a way I can set the Logging API's config file (java.util.logging.config.file) from within my program? I have tried using System.setProperty but it doesn't seem to work. The only way I seem to be able to set the property is with -D on the command line.
Thanks
Rob

Is there a way I can set the Logging API's config file (java.util.logging.config.file) from within my program? I have tried using System.setProperty but it doesn't seem to work. The only way I seem to be able to set the property is with -D on the command line.Read the Logging Overview Dokumentation
anyway
InputStream inputStream = new FileInputStream("logging.properties");
LogManager.getLogManager().readConfiguration(inputStream);
...

Logging API AdapterFramework 3.0

Hello,
i still wonder why it was necessary to provide an own API for Logging and Tracing inside the Adapter Framework.
The Web AS Logging API does the same.
Developing an JCA Adapter that can be used inside the XI Adapter Framework and as a Basic JCA 1.0 Adapter in the Web AS, theres's need to provide support for both APIs.
Has anyone an idea to solve this problem?

There is a lot of logging to the console with 2.3.0 RC1 when I am doing
any trips to the datastore, is it possible to switch this off? I am
using Kodo.rar in Jboss 3.0.0Remove the 'com.solarmetric.kodo.Logger' property from your properties file. You can also remove it from the Properties instance you use to construct the PersistenceManagerFactory. If you'd like to log to a file instead, change the property to the name of a file to log to.

How come logging is so hard? - JDK1.4 Logging API

Have a small project on hand. A standalone java program trigged by unix cron job and do some data cleaning. Need to implement a very simple logger. Tried to use JDK1.4 Logging API, here's my code:
public class MyLogManager {
     public final static String NAME = "mylog";
     public final static String LOG_FILE_NAME = "C:/my.log";
     private static Logger logger;
     static {
          try {
               logger = Logger.getLogger(NAME);
               Handler fh = new FileHandler(LOG_FILE_NAME);
               fh.setFormatter(new SimpleFormatter());
               logger.addHandler(fh);
               logger.setLevel(Level.ALL);
          } catch (Exception e) {
               System.out.println("Unable to initialize logger: " + e.toString());
               System.exit(1);
     public static Logger getLogger() {
          return logger;
and use MyLogManager.getLogger().info("message") to log message.
It works and my.log was generated with log message. However, the problem is everytime a new job (java myprogam ...) runs, it deletes the old log file and create a new one.
I want the message to be appended by the end of old log file. What should I do? Any help?

Use log4j (google for it - it's on http://jakarta.apache.org).
If log4j.jar is in your classpath, the JDK 1.4 logging framework will use it automatically. Then all you have to do is to configure a log4j.properties file in your classpath to log wherever you want it to.
And log4j is sorta-smart about multiple programs logging to the same file.

Logging API: Java 1.5 logs a lot in FINE, etc.

Similar Messages

Maybe you are looking for