If you are new to Log4j, I would avoid using 1.3alpha. You are
welcome to report a bug on 1.3alpha, but you won't get much support
for it. Releases have been few and far in between, though it looks
like there will be a new one coming up here shortly following the
release of Log4j-1.2.14. I
At 05:42 PM 9/16/2006, you wrote:
>Hello every body:
>I am having some difficulties working with log4j, and I need some help
>from some one.
>I am writing a client/server application, in some way it can be compared
>with a chat client, where two or more users connect to the server
>through an appl
Jacob:
Here's what I have,
1- both applications are opend in totally different browsers.
2- in fact both applications are totally different, the applets are
(Host.java , Controller.java).
3- the last assumption might be true about firefox providing one shared
JVM throug the plugin. I will launch
I went back yesterday to 1.2, after the shared JVM issue.
I didn't test it with trace, yet. I will report again if I find it a
problem.
Thanx
Jacob Kjome wrote:
If you are new to Log4j, I would avoid using 1.3alpha. You are welcome
to report a bug on 1.3alpha, but you won't get much suppor
you were right: They are using the same JVM,
ps -A gives
15644 ?00:00:00 firefox
15664 ?00:00:00 run-mozilla.sh
15669 ?00:00:02 firefox-bin
15674 ?00:02:05 java_vm
15985 pts/000:00:00 ps
when both are running
However, I found few JVMs processes (zombies), kiled
Trace is not working, I am using log4j 1.2
It works only from the main class. For example, if I have a class
component, and I do some logging in this class using trace, it's never
shown.
Those are the priorities I found:
ALL -2147483648
TRACE 5000
DEBUG 1
INFO 2
WARN 3
ERROR 4
Dear Bender, Thanks four your xml sample now it works as I expect, on the attached file you will find it. Nevertheless I have some comments, I am not log4j expert, but I guess the syntax could be simplified, and probably it is possible: 1. With your suggestion, I have to specify explici
At 04:50 PM 9/17/2006, you wrote:
>Trace is not working, I am using log4j 1.2
1.2.13? You should be specific. You might want to try 1.2.14, which
should be made an official release shortly. Until then, it is just a
release candidate, so wait for an official release announcement
before assum
Thanks for confirming that the same JVM is used. At this point, you
have to look at the applet classloading model. If both applets end
up being loaded in the same classloader, then they will both be using
the same instance of Log4j. If this is true, then both apps will be
running within th
At 07:19 PM 9/17/2006, you wrote:
Dear Bender,
Thanks four your xml sample now it works as I
expect, on the attached file you will find it.
Nevertheless I have some comments, I am not
log4j expert, but I guess the syntax could be
simplified, and probably it is possible:
1. With your sugge
+1
On 9/16/06, Scott Heaberlin <[EMAIL PROTECTED]> wrote:
I probably should post this to the log4j-dev list, but I figured there
might be other log4j users out there wondering this same thing.
What is the status of log4j 1.3? I was wondering why I felt such
deja-vu writing this, then I recalle
> James Stauffer wrote:
> I suggest that you create 2 loggers per class.
> Logger logger = Logger.getLogger(getClass());
> Logger loggerSpecial = Logger.getLogger("special." + getClass().getName());
>
> log4j.rootLogger=ERROR
> log4j.category.org = A1
> log4j.category.special = SPECIAL_APPENDER
>
Thanks for your extensive answer, see inline..
> Well, when you are using a repository selector, the idea is that you
> have Log4j in a position where it is not part of your app, but part
> of the server; otherwise there's no point to using a repository
> selector. In order for a server wide ins
13 matches
Mail list logo
