Multi-locale support in java.util.logging?

Can I use log (or logrb) methods in the java.util.logging API to localize my messages to a locale other than the default locale? From what I see in the jdk doc & src, it seems like this is not possible. This kind of multi-locale localization support is essential for server applications that talk to clients from different locales.

Well, I've never done localization. In case you haven't seen it, here's some documentation from Logger, but that's all I can offer.
Each Logger may have a ResourceBundle name associated with it. The named bundle will be used for localizing logging messages. If a Logger does not have its own ResourceBundle name, then it will inherit the ResourceBundle name from its parent, recursively up the tree.
Most of the logger output methods take a "msg" argument. This msg argument may be either a raw value or a localization key. During formatting, if the logger has (or inherits) a localization ResourceBundle and if the ResourceBundle has a mapping for the msg string, then the msg string is replaced by the localized value. Otherwise the original msg string is used. Typically, formatters use java.text.MessageFormat style formatting to format parameters, so for example a format string "{0} {1}" would format two parameters as strings.
When mapping ResourceBundle names to ResourceBundles, the Logger will first try to use the Thread's ContextClassLoader. If that is null it will try the SystemClassLoader instead. As a temporary transition feature in the initial implementation, if the Logger is unable to locate a ResourceBundle from the ContextClassLoader or SystemClassLoader the Logger will also search up the class stack and use successive calling ClassLoaders to try to locate a ResourceBundle. (This call stack search is to allow containers to transition to using ContextClassLoaders and is likely to be removed in future versions.)
Formatting (including localization) is the responsibility of the output Handler, which will typically call a Formatter.

Similar Messages

Multi currency support with java.util.Locale

My project has a requirement to support multiple currencies as our first internationalization feature. However, I've come across something with the Locale class that doesn't really make sense to me, and I'm wondering if anyone else has any best practices or insight.
Why can't you create a Locale knowing only the ISO 3166 code? For multi-currency support, it doesn't make sense that I should need to provide a language in order to obtain a Locale, which is needed to generate the proper NumberFormat (and in 1.4 the java.util.Currency) class.
Is there an instance where the language one speaks is directly correlated to the currency that they use?
Actually, it doesn't make much sense that you can create a Locale only from a language either, since if my user a Hispanic-American, the language would be Spanish but the country (and therefore currency) would be US.
It seems to me that if the Locale class can default a country code based on the language, it should also be able to default a language based on the country.
Given these limitations, is there a recommended best practice about obtaining a Locale without a pre-determined language?

Hi,
this was a bit of a bugbear for a long time. Currency kind of wound up inexorably linked to Locale for a long time because the way a currency was formatted depended on the textual layout of the language as well as the country, and as date formatting was an issue too, it was easier for them to implement it the way they did.
It's been an RFE for a long time, and I believe the beta releases of Merlin carry a currency API that is separate from a Locale. The link to the RFE is below. Hopefully Merlin Beta will allow you to achieve what you want - it seems to be pretty stable from what I've seen of it, and Sun do have a good record when it comes to releasing stable betas, so I wouldn't panic too much about the fact you're developing on a "pre-release candidate" JDK.
http://developer.java.sun.com/developer/bugParade/bugs/4290801.html
Hope that helps!
Martin Hughes

Enabling java.util.logging for Toplink

JDeveloper 10.1.3.0.4 Build 3673 running Embedded OC4J (jdk1.5.0_02).
I'm trying to get Toplink to log to a custom handler (a la java.util.logging) while running Embedded OC4J, but nothing I've tried works.
If I use the java.util.logging.LogManager to loop through and print out all of the existing loggers, none of the 145 listed in the Embedded OC4J environment mention anything about toplink. So presumably Toplink is not running in "java" logging mode. I'm not using toplink workbench which seems to have a UI checkbox to enable java logging, and I haven't found a way to turn it on using JDeveloper. I've tried using the system property -Dtoplink.log.destination=JAVA (no effect) and adding my handler to j2ee-logging.xml (couldn't find my custom logging handler class, and won't help anyway if toplink isn't using java.util.logging), and various attempts at hacking sessions.xml with using log-type and java-log elements (I couldn't get them right--xml parse errors).
What do I need to do to get Toplink to log to a custom handler?
TIA,
Clark

Hi Clark,
You can use either java or server log when running an application in OC4J.
1 When you run a CMP application, use system property (e.g. Dtoplink.log.destination=JAVA)
2 When you run a non CMP server application, use the logging tag in sessions.xml (e.g. <logging xsi:type="server-log"/>)
You have the following options to get TopLink to log to a custom handler
1 If you want to do the entire configuration from logging.properties, remove all handlers/loggers declarations from j2ee-logging.xml and in that case all configuration will be from logging.properties
2 Use a combination of j2ee-logging.xml and logging.properties. You can define certain attributes in j2ee-logging.xml. They are "name", "class", "level", "errorManager", "filter", "formatter" and "encoding", and they correspond to the attributes of java.util.logging.Handler. Attributes in subclasses of Handler are not supported. All other properties for the handler are defined in logging.properties. j2ee-logging.xml is processed on top of logging.properties, which means j2ee-logging.xml takes the precedence for certain attributes/properties. Take FileHandler for an example,
j2ee-logging.xml:
     <log_handlers>
     <log_handler name='my-handler' class='java.util.logging.FileHandler'
          formatter='java.util.logging.SimpleFormatter' level='INFO'/>
     </log_handlers>
logging.properties:
     java.util.logging.FileHandler.pattern = %h/java%u.log
     java.util.logging.FileHandler.limit = 10000
     java.util.logging.FileHandler.count = 2
If there are no properties defined in logging.properties, it will use its default values, which are documented in the FileHandler javadoc.
Shannon

Unable to capture messages from java.util.logging

I have a class called (Caller.java) which invokes a method called foo from another java class(Util.java) using reflection API.Now this method foo logs messages using Java's logger.My requirement is to call foo for 3 times from Caller and capture/redirect the log messages into 3 log files.
But only the first log file is capturing the log messages(from logger) and other two are not ?
Plz suggest if I am doing somethin wrong here ?
Caller.java
package project2;
import java.io.File;
import java.io.FileNotFoundException;
import java.io.PrintStream;
import java.lang.reflect.Method;
public class Caller {
    public Caller() {
    public static void main(String[] args) throws Exception {
        Caller caller = new Caller();
        for (int i = 0 ;i<3 ;i++ ) {
            caller.createLogStream(i);
            System.setOut(caller.getPs());
            System.setErr(caller.getPs());
            /*****************Invoking Util.java*****************************/
            Class clas = Class.forName("project2.Util");
            Method m = clas.getMethod("foo",null);
            Object obj =clas.newInstance();
            m.invoke(obj,null);
    public void createLogStream(int i) throws FileNotFoundException {
        ps = new PrintStream(new File(System.getenv("HOME")+File.separator+"MyLog"+i+".log"));
    public void closeLogStream(){
        ps.close();
        ps = null;
    private PrintStream ps = null;
    public PrintStream getPs() {
        return ps;
} Util.java
package project2;
import java.util.logging.Logger;
public class Util {
    Logger logger = null;
    public Util() {
        logger = Logger.getLogger(this.getClass().getName());
    public void foo(){
        System.out.println("Hello out stream");
        System.err.println("Hello error stream");
        logger.info("This is an information");
        logger.warning("This is a warning message");
        logger.severe("This is fatal!! ");
}First Log file MyLog0.log:
Hello out stream
Hello error stream
Feb 16, 2009 7:55:55 PM project2.Util foo
INFO: This is an information
Feb 16, 2009 7:55:55 PM project2.Util foo
WARNING: This is a warning message
Feb 16, 2009 7:55:55 PM project2.Util foo
SEVERE: This is fatal!!
Feb 16, 2009 7:55:55 PM project2.Util foo
INFO: This is an information
Feb 16, 2009 7:55:55 PM project2.Util foo
WARNING: This is a warning message
Feb 16, 2009 7:55:55 PM project2.Util foo
SEVERE: This is fatal!!
Feb 16, 2009 7:55:55 PM project2.Util foo
INFO: This is an information
Feb 16, 2009 7:55:55 PM project2.Util foo
WARNING: This is a warning message
Feb 16, 2009 7:55:55 PM project2.Util foo
SEVERE: This is fatal!! Other 2 log files have only this much
Hello out stream
Hello error stream

A stale Connection Factory or Connection Handle may be used in SOA 11g
Regards,
Anuj

Doubt in java.util.logging

Hi,
I have doubt in logging api provided in java 1.4.
I have a simple program to get the logger and output log into it.
This is how the program looks.
LogTest.java
import java.util.logging.*;
import java.util.*;
public class LogTest {
public static void main(String args[]) {
     LogManager manager = LogManager.getLogManager();
     Logger l = manager.getLogger("global");
     System.out.println(l);
     l.severe("Test");
     System.out.println(manager.getLogger("ivy"));
     System.out.println(manager.getLogger("test"));
I able to get the instance of the global logger, but im not able to get instance of other logger. I getting null for all the other logger
test.properites
=================
handlers = java.util.logging.ConsoleHandler
java.util.logging.ConsoleHandler.level=INFO
java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter
ivy.level = INFO
.ivy.level = INFO
=================
Compilation Command
java -Djava.util.logging.config.file=C:\WorkSpace\test.properties LogTest Output:
java.util.logging.Logger@13f5d07
Jan 25, 2006 7:19:24 PM LogTest main
SEVERE: Test
null
null
I also tried the same with no config properties, Still im getting the null for logger.
Can I know is there anything that im missing. Is there any property that must be set or do i hav set some config properties.
Thanks,
Siva

Well, basically that's part of the formatdefinition
that Properties uses. If you don't do it, then you
aren't really using Properties format and you'llhave
to do your own IO.Thanks for the reply. Is there anyother api or class
that can be used to resolve my problem.What is the problem? A character is escaped, but you will get : when you read the value. You don't have a problem as long as all reading / writing is done through that class.

Java.util.logging: write to one log file from many application (classes)

I have a menuapp to launch many applications, all running in same JVM and i want to add logging information to them, using java.util.logging.
Intention is to redirect the logginginfo to a specific file within the menuapp. Then i want all logging from all applications written in same file. Finally, if needed (but i don't think it is), i will include code to write logging to specific file per app (class). The latter is probably not neccessary because there are tools to analyse the logging-files and allow to select filters on specific classes only.
The applications are in their own packages/jars and contain following logging-code:
        // Redirect error output
        try {
            myHandler = new FileHandler("myLogging.xml",1000000,2);
        } catch (IOException e) {
          System.out.println("Could not create file. Using the console handler");
        myLogger.addHandler(myHandler);
        myLogger.info("Our first logging message");
        myLogger.severe("Something terrible happened");
        ...When i launch the menuapplication, it writes info to "myLogging.xml.0"
but when i launch an application, the app writes info to "myLogging.xml.0.1"
I already tried to leave out the creation of a new Filehandler (try/catch block in code above) but it doesn't help.
Is it possible to write loginfo to same specific file?

You should open/close it somehow at every write from different processes.
But I personally prefer different file names to your forced merging, though.

Getting no output from java.util.logging.FileHandler

I am new to Java as is the company I work for, but we have just landed a contract that specifies J2EE as the platform, so here we are. :-) Please bear with me.
I have been charged with determining our logging architecture and it looks like what is available in java.util.logging will do well (though we may use log4j). However, at this point I am just trying to get anything to work and not having much luck.
We are using JSF on the front end and I have created a very simple JSF page to test logging. The relevant code is below and I hope will be self explanatory: This code is not meant to be efficient or anything. It is just a proof of concept.
    public String button1_action() {
        // User event code here...
        try {
            Logger l = java.util.logging.Logger.getLogger(Page1.class.getName());
            l.entering(Page1.class.getName(), "button1_action");
            l.info(this.textField1.getValue().toString());
            l.exiting(Page1.class.getName(), "button1_action");
            java.util.logging.Handler h = l.getHandlers()[0];
            h.flush();
        catch(Exception ex) {
            //I have tested this and we aren?t catching any errors.
            System.err.println(ex);
        return "";
    }My logger.properties files looks like this:
handlers= java.util.logging.FileHandler
.level= FINEST
java.util.logging.FileHandler.pattern = c:/sun/logs/test-%u.log
java.util.logging.FileHandler.limit = 50000
java.util.logging.FileHandler.count = 1
java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatterI have developed and tested this in Sun Studio Creator 2004Q2 What is happening is that I am getting three log files in c:/sun/logs
test-0.log, test-1.log and test-2.log. The first two contain output from various sun components. (sun.rmi.transport for example). The third log remains empty. (zero length)
I have also deployed the test app to a tomcat 5.0.28 server and get similar results. The only difference is I get only one two log files and the second one remains empty.
Any assistance or suggestions as to what direction I should be taking would be appreciated.
--Ken

Do not use default logger as getLoggers[0] , but use your java.util.Logger.FileHandler and add filehandler object to log your fButtonActions and you do not need to mess with logger.properties too.

How is java.util.logging used to log to unix syslog?

I'm trying to log out to syslog using the java.util.logging that is now in 1.4. I've read all I can find on this topic (not much) and have solicited the used of some syslog free ware (protomatter) but still can't get this to work. I feel like I'm missing something simple here, any help would be appreciated....
Here is my latest attempt:
import java.util.logging.*;
import java.util.*;
import java.io.*;
import com.protomatter.syslog.SyslogHandler;
public class SyslogTest
public static void main(String argv[]){
Logger logger2 = Logger.getLogger("local3");
SyslogHandler ch = new SyslogHandler();
ch.setLevel(Level.WARNING);
logger2.addHandler(ch);
logger2.warning("this is a log message");
if (logger2.isLoggable(Level.WARNING)) {
System.out.println("Is LOGGABLE");
else {
System.out.println("Is not loggable");
When this is run nothing is printed to any of the local3 facilities. I've verified that syslog is running fine from the command line using unix logger, so the problem seems to be isolated to my java.
Thanks.

Hi,
What is in your logging.properties file? Can you also include the contents of this file?
Cheers,
Craig.

SLF4J instead of Java Util Logging?

Hi BDBJE team,
Is it included on the BDBJE roadmap a migration from "Java Util Logging" to a most flexible framework like SLF4J?
BR,
/César.

Hi Cesar,
No, definitely not on the road map, but we are aware of the shortcomings of standard Java logging (as documented on this forum) and we will think about what to do about it. It's a little disappointing, given that we just finished moving to standard Java logging (from our own custom logging) in the last release.
--mark

How to prevent java.util.logging from displaying pop-up dialog on SEVERE?

Hi,
I'm new to using java.util.logging. I notice that whenever I try to make a call to logger.SEVERE(msg) or logger.WARNING(msg), not only does it write the output to file (which I want), but it also pops up a dialog box displaying the exception. I don't want this pop up to appear. How do I prevent the logger from doing this?

What are you talking about?
Hello,
In order to better assist you with your issue please provide us with a screenshot. If you need help to create a screenshot, please see [[How do I create a screenshot of my problem?]]
Once you've done this, attach the saved screenshot file to your forum post by clicking the '''Browse...''' button below the ''Post your reply'' box. This will help us to visualize the problem.
Thank you!

Java.util.logging - Problem with setting different Levels for each Handler

Hello all,
I am having issues setting up the java.util.logging system to use multiple handlers.
I will paste the relevant code below, but basically I have 3 Handlers. One is a custom handler that opens a JOptionPane dialog with the specified error, the others are ConsoleHandler and FileHandler. I want Console and File to display ALL levels, and I want the custom handler to only display SEVERE levels.
As it is now, all log levels are being displayed in the JOptionPane, and the Console is displaying duplicates.
Here is the code that sets up the logger:
logger = Logger.getLogger("lib.srr.applet");
// I have tried both with and without the following statement
logger.setLevel(Level.ALL);
// Log to file for all levels FINER and up
FileHandler fh = new FileHandler("mylog.log");
fh.setFormatter(new SimpleFormatter());
fh.setLevel(Level.FINER);
// Log to console for all levels FINER and up
ConsoleHandler ch = new ConsoleHandler();
ch.setLevel(Level.FINER);
// Log SEVERE levels to the User, through a JOptionPane message dialog
SRRUserAlertHandler uah = new SRRUserAlertHandler();
uah.setLevel(Level.SEVERE);
uah.setFormatter(new SRRUserAlertFormatter());
// Add handlers
logger.addHandler(fh);
logger.addHandler(ch);
logger.addHandler(uah);
logger.info(fh.getLevel().toString() + " -- " + ch.getLevel().toString() + " -- " + uah.getLevel().toString());
logger.info("Logger Initialized.");Both of those logger.info() calls displays to the SRRUserAlertHandler, despite the level being set to SEVERE.
The getLevel calls displays the proper levels: "FINER -- FINER -- SEVERE"
When I start up the applet, I get the following in the console:
Apr 28, 2009 12:01:34 PM lib.srr.applet.SRR initLogger
INFO: FINER -- FINER -- SEVERE
Apr 28, 2009 12:01:34 PM lib.srr.applet.SRR initLogger
INFO: FINER -- FINER -- SEVERE
Apr 28, 2009 12:01:40 PM lib.srr.applet.SRR initLogger
INFO: Logger Initialized.
Apr 28, 2009 12:01:40 PM lib.srr.applet.SRR initLogger
INFO: Logger Initialized.
Apr 28, 2009 12:01:41 PM lib.srr.applet.SRR init
INFO: Preparing Helper Files.
Apr 28, 2009 12:01:41 PM lib.srr.applet.SRR init
INFO: Preparing Helper Files.
Apr 28, 2009 12:01:42 PM lib.srr.applet.SRR init
INFO: Getting PC Name.
Apr 28, 2009 12:01:42 PM lib.srr.applet.SRR init
INFO: Getting PC Name.
Apr 28, 2009 12:01:42 PM lib.srr.applet.SRR init
INFO: Finished Initialization.
Apr 28, 2009 12:01:42 PM lib.srr.applet.SRR init
INFO: Finished Initialization.Notice they all display twice. Each of those are also being displayed to the user through the JOptionPane dialogs.
Any ideas how I can properly set this up to send ONLY SEVERE to the user, and FINER and up to the File/Console?
Thanks!
Edit:
Just in case, here is the code for my SRRUserAlertHandler:
public class SRRUserAlertHandler extends Handler {
     public void close() throws SecurityException {
     public void flush() {
     public void publish(LogRecord arg0) {
          JOptionPane.showMessageDialog(null, arg0.getMessage());
}Edited by: compbry15 on Apr 28, 2009 9:44 AM

For now I have fixed the issue of setLevel not working by making a Filter class:
public class SRRUserAlertFilter implements Filter {
     public boolean isLoggable(LogRecord arg0) {
          if (arg0.getLevel().intValue() >= Level.WARNING.intValue()) {
               System.err.println(arg0.getLevel().intValue() + " -- " + Level.WARNING.intValue());
               return true;
          return false;
}My new SRRUserAlertHandler goes like this now:
public class SRRUserAlertHandler extends Handler {
     public void close() throws SecurityException {
     public void flush() {
     public void publish(LogRecord arg0) {
          Filter theFilter = this.getFilter();
          if (theFilter.isLoggable(arg0))
               JOptionPane.showMessageDialog(null, arg0.getMessage());
}This is ugly as sin .. but I cannot be required to change an external config file when this is going in an applet.
After much searching around, this logging api is quite annoying at times. I have seen numerous other people run into problems with it not logging specific levels, or logging too many levels, etc. A developer should be able to complete configure the system without having to modify external config files.
Does anyone else have another solution?

Java.util.logging.XMLFormatter - need advise

Hi all,
I have this class which suppose to write some message into the custom log file (in XML). Problem is, after the first time of writing it into the same file, it will append additional XML header :
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE log SYSTEM "logger.dtd">
Worse, it will always append below.
For example, the original XML file contains:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE log SYSTEM "logger.dtd">
<log>
<record>
<date>2010-10-20T18:18:33</date>
<millis>1287569913671</millis>
<sequence>0</sequence>
<logger>atm.controller.Log_Controller</logger>
<level>INFO</level>
<class>atm.controller.Log_Controller</class>
<method>writeInfoLog</method>
<thread>10</thread>
<message>message inside thia standard data</message>
</record>
</log>when I write additional message into the same file using logger.info("some message"); on the second rounds, it will append additional XML header* info and become like this:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE log SYSTEM "logger.dtd">
<log>
<record>
<date>2010-10-20T18:18:33</date>
<millis>1287569913671</millis>
<sequence>0</sequence>
<logger>atm.controller.Log_Controller</logger>
<level>INFO</level>
<class>atm.controller.Log_Controller</class>
<method>writeInfoLog</method>
<thread>10</thread>
<message>message inside thia standard data</message>
</record>
</log>
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE log SYSTEM "logger.dtd">
<log>
<record>
<date>2010-10-20T18:21:25</date>
<millis>1287570085050</millis>
<sequence>0</sequence>
<logger>atm.controller.Log_Controller</logger>
<level>INFO</level>
<class>atm.controller.Log_Controller</class>
<method>writeInfoLog</method>
<thread>10</thread>
<message>message inside thia standard data</message>
</record>
</log>--------------------------------------------------
Below is the code.
import java.io.IOException;
import java.util.logging.FileHandler;
import java.util.logging.Logger;
import java.util.logging.XMLFormatter;
public class Log_Controller
    private static Logger logger = Logger.getLogger( Log_Controller.class.getName() );
    private boolean allowAppend = true;
    public Log_Controller()
        try
            XMLFormatter formatterTxt = new XMLFormatter();
            FileHandler fileTxt = new FileHandler( "test.xml", allowAppend );
            fileTxt.setFormatter( formatterTxt );
            logger.addHandler( fileTxt );
        catch ( IOException ioe )
            ioe.printStackTrace();
    public void writeInfoLog( String message )
        logger.info("message inside thia standard data"); //THIS IS THE PART WHERE IT WRITE SOME MESSAGE INTO THE FILE
//        logger.info( message );
}This is something new to me, appreciate if someone can point me what the mistake that I have done.
Thanks thanks.
Edited by: 803699 on 20-Oct-2010 04:15
Edited by: 803699 on 20-Oct-2010 08:45

you cannot append to an xml file using the standard formatter because it makes the log file a "complete xml document" (header and root wrapper tags). if you want to be able to append to an existing xml log file, you will need to roll your own formatter.

Can't load runtime properties in java.util.logging.LogManager

This should be so easy, what am I doing wrong?
I have the following logging.properties located on my classpath:
handlers=java.util.logging.ConsoleHandler
.level=INFO
java.util.logging.ConsoleHandler.level=INFO
java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter
Test.level=FINE
Test.handlers=java.util.logging.ConsoleHandlerI have a very simple Test.java file that should load the new properties file and print out the known logger names (ie Test).
I've also tried putting Test.java in a package, it didn't seem to matter.
public class Test {
public Test() {
    String name = this.getClass().getName();
    //this properties file is should be sitting in same dir as Test class
    java.io.InputStream is = this.getClass().getResourceAsStream("logging.properties");
    try {
      //get log manager instance
      java.util.logging.LogManager lm = java.util.logging.LogManager.getLogManager();
      //read the new configuration
      lm.readConfiguration(is);
      //print out list of logger names
      java.util.Enumeration e = lm.getLoggerNames();
      while (e.hasMoreElements()) {
        System.out.println(e.nextElement());
      //print logger for this class!
      System.out.println("getLogger("+name+"): "+lm.getLogger(name));
    } catch (Exception e) {
    } finally {
      try {
        is.close();
        is = null;
      } catch (Exception e) {}
public static void main(String[] args) {
    Test test1 = new Test();
}The output I get from this is a single logger name, and then null for my desired Test logger.
global
getLogger(Test): null

It seems a logger instance HAS been created for my Test class, I've added the lines below. Though it didn't appear in the logger names enumeration.
java.util.logging.Logger logger = java.util.logging.Logger.getLogger(name);
System.out.println(logger.getName()+"="+logger.getLevel().getName());
logger.severe("severe");
logger.warning("warning");
logger.info("info");
logger.config("config");
logger.fine("fine");
logger.finer("finer");
logger.finest("finest");Output:Test=FINEST
6/10/2003 16:00:01 Test <init>
SEVERE: severe
6/10/2003 16:00:01 Test <init>
WARNING: warning
6/10/2003 16:00:01 Test <init>
INFO: infoObservations:
1) Despite my Test class having the FINEST log level, the default ConsoleHandler had log level of INFO, and hence only up to INFO logged.

Creating a new Handler (java.util.logging API)

Hi,
I'm developping a new Handler (extending the java.util.logging.StreamHandler) and I need to get some initialisation properties from the LogManager. I was taking example from the existing Handlers (SocketHandler, FileHandler...) and wanted to use the LogManager.getLevelProperty, getFilterProperty and so on). Unfortunately these methods are not public.
Is there any good reason for that ? As we are still dealing with a beta version, can't we have them public (same old Open Source problem).
Antonio

I am in a similar situation and agree completely with the above comments. Using the LogManager getProperty() is incredibly cumbersome.
Ciao Ric

OracleLog.properties for java.util.logging

In the Oracle JDBC FAQ the answer to the question "How do I configure java.util.logging to get useful trace output from Oracle JDBC?" <http://otn.oracle.com/tech/java/sqlj_jdbc/htdocs/jdbc_faq.htm#36_03> mentions the file "OracleLog.properties" provided in the "demo.zip" file.
I cannot find the file "OracleLog.properties" anywhere?
Any suggestions?
Kindest Regards,
Gerhard Hofmann

It seems a logger instance HAS been created for my Test class, I've added the lines below. Though it didn't appear in the logger names enumeration.
java.util.logging.Logger logger = java.util.logging.Logger.getLogger(name);
System.out.println(logger.getName()+"="+logger.getLevel().getName());
logger.severe("severe");
logger.warning("warning");
logger.info("info");
logger.config("config");
logger.fine("fine");
logger.finer("finer");
logger.finest("finest");Output:Test=FINEST
6/10/2003 16:00:01 Test <init>
SEVERE: severe
6/10/2003 16:00:01 Test <init>
WARNING: warning
6/10/2003 16:00:01 Test <init>
INFO: infoObservations:
1) Despite my Test class having the FINEST log level, the default ConsoleHandler had log level of INFO, and hence only up to INFO logged.

Multi-locale support in java.util.logging?

Similar Messages

Maybe you are looking for