Hello.
The sources of my current development dir is D:\projects\SPI\java\src and I
am using log4j to log the app's messages. In the log4.properites file I have
defined several Appenders and I wonder why the following happens:
log4j.appender.SPEventAppender.file=\logs\SPEventLogfile.log --
Thorbjørn Ravn Andersen nospam at c.dk writes:
We use Eclipse for development and I like the way that stacktraces are
shown and linked to the underlying source, so I was pondering whether
similar functionality is possible for the numerous debug messages we
have? I looked at the
In my log file, I have this lines.
13:41:55,291 DEBUG [org.jboss.deployment.MainDeployer]
(MainDeployer.java:816) Starting deployment (init step) of package at:
file:/C:/jboss-4.0.3SP1/server/bem-sigo/deploy/ejb3.deployer/
13:41:55,291 DEBUG [org.jboss.deployment.MainDeployer]
You dont need a filter for doing this, because this is covered by the core idea
of the log4j framework.
Just define a logger named org.jboss.deployment.MainDeployer, attach the
desired file appender to this class and set the additivity flag to false. If
you don't attach the same appender to
I don't understand your answer, because i'm a newbie in this. But, I don't
have any access to the org.jboss.deployment.MainDeployer, because it's a
class already created by jboss. I only work with the compiled java file
(class), not java source files.
In other words, I'm using a jboss
I dont know JBoss, but I assume they use the logging framework like foreseen,
i.e. they get the loggers the way I described before.
Just try my suggestion and see if it works.
Heri
-Original Message-
From: Pedro Costa [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 01, 2006 3:48
sorry for the nube question, but are you talking about Eclipse being able to
log its own internal messages, or Eclipse running an use developed
application and formatting the log messages to its console?
Thanks.
On 2/1/06, Stephen Schaub [EMAIL PROTECTED] wrote:
Thorbjørn Ravn Andersen
Hi,
Could you please give me some CLUE, on how to proceed to test the following
method:
public int decide(LoggingEvent inEvent) {
boolean retCode = false;
if (inEvent != null) {
Matcher matcher =
targetPattern.matcher(inEvent.getLoggerName());
Hi,
I am trying to use Chainsaw to read our log files, which are in fact
generated by a C++ application, but conforms quite well with normal
log4j formats. Here is a sample line from our log:
[2006-02-01 15:33:57] INFO :
[EMAIL PROTECTED]:
articles: Finished running
I am trying to parse
I was able to process this event:
[2006-02-01 15:33:57] INFO :[EMAIL PROTECTED]:articles: Finished running
Using this logFormat expression:
[TIMESTAMP] LEVEL*:LOGGER:NDC:MESSAGE
And this timestamp format:
-MM-d HH:mm:ss
I assumed there were extra spaces after the level, thus the *
One minor change:
Here's an updated logFormat that will create a new 'machine' property for the
portion of the logger name after the @ symbol:
[TIMESTAMP] LEVEL*:[EMAIL PROTECTED](machine):NDC:MESSAGE
Scott Deboy
COMOTIV SYSTEMS
111 SW Columbia Street Ste. 950
Portland, OR 97201
Telephone:
Hi all,
I was just wondering if anyone has worked on an RMI-based logger that
might be modified to be used as a Jini service?
I have several programs running on different machines, and I'd like to
monitor all of them from a single computer. If loggers registered
themselves with a lookup
Not as a Jini service.
How do you want to monitor them?
If you'd like to use Chainsaw, there are a few options based on if you are ok
losing messages or not, and if you're in an environment that can send/receive
multicast/udp packets.
Multicast/udp:
- Use the recently-added support for JMDNS
Hello all,
Well, I have program that is appending it's logs with a JmsAppender and I
want to monitor it will Chainsaw using a JmsReceiver. When I start chainsaw
up and point it to my receiver configfile I the following error shows up in
chainsaw's log panel.
Could not instantiate object of
Hi Scott,
Thanks for your recommendations. I'm currently using
SocketHubAppenders, but it means that I have to know which computers
I'll be running loggers on.
I'm working on applications for a sample 'interactive workspace', a
room with hardware and software infrastructure for users coming and
Superb! That did it!
I am most grateful - also for making Chainsaw available!
The best of luck with the 1.3 development :-)
- Thomas
-Original Message-
From: Scott Deboy [mailto:[EMAIL PROTECTED]
Sent: 1. februar 2006 17:20
To: Log4J Users List
Subject: RE: Trouble specifing logFormat
The more appenders/receivers the better..
The JMDNS (Java implementation of zeroconf/rendezvous/bonjour) option may work
well for you, as would a well-known multicast group using
multicastappender/receiver.
Paul wrote a ZeroConfSocketHubAppender - and it will work with log4j 1.2.x.
Here's a
It looks like you need to add a jar containing javax.jms.MessageListener to
your classpath.
Scott Deboy
COMOTIV SYSTEMS
111 SW Columbia Street Ste. 950
Portland, OR 97201
Telephone: 503.224.7496
Cell: 503.997.1367
Fax:503.222.0185
[EMAIL PROTECTED]
This is actually a problem for lots of folks even on the Java side since a lot
of people use %5p to make the logs easier to read.
We'll have to think about it a bit.
Scott Deboy
COMOTIV SYSTEMS
111 SW Columbia Street Ste. 950
Portland, OR 97201
Telephone: 503.224.7496
Cell:
Quoting Dirk Ulrich [EMAIL PROTECTED]:
Hello.
The sources of my current development dir is D:\projects\SPI\java\src and I
am using log4j to log the app's messages. In the log4.properites file I have
defined several Appenders and I wonder why the following happens:
Hmmm...
The JmDNS solution looks promising, where might I find this
ZeroConfSocketHubAppender?
-Sam
On 2/1/06, Scott Deboy [EMAIL PROTECTED] wrote:
The more appenders/receivers the better..
The JMDNS (Java implementation of zeroconf/rendezvous/bonjour) option may
work well for you, as
Okay, here's the situation.
The receiver seems to be functioning well. Chainsaw starts it up fine and
there are no errors in chainsaw's console from the console appender.
I think there are problems with the JmsAppender.
Things that make me think the jmsReceiver is okay:
1)chainsaw starts it up
To test the theory of jmsAppender being bad, perhaps you can use
Hermes to browse the ActiveMQ Topic to see if it's sending the events
correctly?
http://www.hermesjms.com/
Straightforward to configure, give me a hoi if you have trouble
getting activemq hermes working together.
Paul
On
I am attempting to set our logs up so that they will save Chinese
characters properly, and I'm not having much luck. We have a class
which extends FileAppender, and in it I'm doing a brute-force
appender.setEncoding(UTF-16), but unfortunately I'm still seeing
question marks in the log file.
This is coming RSN, seriously I promise., I just want to get the next
version of Chainsaw out with the latest in the distribution
mechanism, and then complete the ZeroConf stuff and then release
that. A lot of the remaining is tidying up the documentation,
however I have been side tracked
On Feb 1, 2006, at 3:05 PM, Crook, Laura wrote:
I am attempting to set our logs up so that they will save Chinese
characters properly, and I'm not having much luck. We have a class
which extends FileAppender, and in it I'm doing a brute-force
appender.setEncoding(UTF-16), but unfortunately
I am having the same problem is there any solution ?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Kaustuva,
If you post your code inline, I would be at least get an idea what the
problem is.
Thanks,
-Kamal.
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of kaustuva mukherjee
Sent: Wednesday, February 01, 2006 5:44 PM
To: log4j-user@logging.apache.org
Subject: Re:
Hi,
Why do you think, I am getting an error, when I run the test case
I use the following test case, I get error: I would appreciate any help.
Test Case:
public void testdecide() {
Logger logger = Logger
.getLogger(com.webmethods.sc.logging.test.unit.WmLoggerFilterTes);
The following change fixed it:
public void testdecide() {
Logger logger = Logger
.getLogger(com.webmethods.sc.logging.test.unit.WmLoggerFilterTes);
WmLoggerFilter subjectWmLoggerFilter = new WmLoggerFilter();
//MessageRenderer mr = new
Perhaps you could set the logging level to FATAL or OFF for the
rootLogger, and later down your xml file set
org.jboss.deployment.MainDeployerPedro level to info? Works in my
properties file, so should work for an xml version also.
In my log file, I have this lines.
13:41:55,291 DEBUG
Latest 'release' bundle (alpha) of Chainsaw is now available.
Webstart version should auto-update, OSX and DOS/Unix version
available from:
http://logging.apache.org/log4j/docs/chainsaw.html
Comments appreciated, a new build process has been put in place, so
there could be a couple of
32 matches
Mail list logo
