[Chainsaw] RE: UI comments? Use of 1.4 JDK and LoggingEvent prop erties

[Paul Smith <Pa...@lawlex.com.au>]

I'm back from a relaxing break, so forgive me if my brain is still
foggy(er).

> -----
> #1
> I've included support for regular expression-based display 
> and colorizing filters but built-in support for regexp is 
> only recently available with the 1.4 JDK in the 
> java.util.regex package.  
> 
> Question:  Should I remove the 1.4 dependency?  Is the 
> benefit of 1.4 users not needing to install a separate regexp 
> package (ORO) outweighed by the usefulness of a 1.2 compiled 
> UI and the separate download requirement?  

I'd personally like to remove any dependancy right back to JDK 1.2 in line
with Log4j core. It'd be worth documenting which bits are 1.2+ specific, and
I could make it my goal to write around it, either by reproducing the
behaviour in custom code, or disabling the feature if a specific package is
not available. I think(?) the Preferences stuff is the only real 1.4
specific feature Chainsaw-wide that would take some noticable effort to
convert.

Certainly in the interim starting with 1.4 is not terrible, but working back
to 1.2 IMHO, would make a lot of people pretty happy.  Perhaps for a release
goal, we could target JDK 1.3?  And then work back further over time (if
necessary).
 
> Should the UI be jarred separately?  I understand the benefit 
> of having a UI and the core classes available as a single download.

Yes please.  Log4j core should be as compact as possible.  We could also
look towards a jumbo Log4J Utility jar that could contain lots of nice
little Log4J tools like Chainsaw, LF5, Acorn etc.
 
> There are other benefits to supporting 1.4 - better 
> performance of the collections classes and a scrolling 
> JTabbedPane come to mind.

These could just be the benefit of the user choosing a specific JDK? (we
could mention them in the docs.) 

> The machinename property is added automatically.  Only the 
> first part of the FQDN is used if it can be resolved.  If it 
> can't be resolved, the IP address is used.
>
> Question:  Are these 'universal' properties (useful to anyone 
> consuming loggingevents), and therefore setting these 
> properties on all loggingevents via the appender is OK?  If 
> not, is there a recommendation on how to get them added when 
> the target is known to be the logging UI?

Would it be easier if we just required the user to specify those location
specific properties on the log4j.xml, and Chainsaw just looks for specific
ones?  i.e. No need to for local machine name lookup etc.

cheers,

Paul


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org

IllegalMonitorStateException

[Tara Czutno <tc...@lw-lmco.com>]

I'm getting this exception when trying to initialize log4J (running jdk 1.2.2
and log4j 1.2.8).  Any ideas?

java.lang.IllegalMonitorStateException: current thread not owner
 at
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:406)

 at
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:307)

 at
org.apache.log4j.PropertyConfigurator.configure(PropertyConfigurator.java:315)
 at rossPkg.util.log.Log4JTest.main(Log4JTest.java:35)
Exception in thread "main" Process terminated with exit code 1

import org.apache.log4j.PropertyConfigurator;

public class Log4JTest {
    public Log4JTest() {
    }


    public static void main(String[] args) {

PropertyConfigurator.configure("d:/dev/ross_work/source/rossPkg/log_config2.txt");

        runTest();
    }

    private static void runTest() {
        TestHelper th = new TestHelper("26.25.101.24");

        TestHelper th2 = new TestHelper("10.11.101.12", true);
        Thread t = new Thread(th);
        t.start();
        Thread t2 = new Thread(th2);
        t2.start();
        th.exiting();
        th2.exiting();
    }
}




---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org