Bug 38883 - LogFilePatternReceiver fails to process multi-line event if message field is delimited on both sides
Summary: LogFilePatternReceiver fails to process multi-line event if message field is ...
Status: REOPENED
Alias: None
Product: Log4j - Now in Jira
Classification: Unclassified
Component: Other (show other bugs)
Version: 1.3alpha
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: log4j-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-07 15:41 UTC by Scott Deboy
Modified: 2008-08-02 18:13 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Deboy 2006-03-07 15:41:36 UTC
An entry in a log file like this:
2006-02-10 16:09:36,977 [INFO] ejb.SecurityManagerBean - [MA Core connected to
remote services...
host: nlveus13.xxxx.com
port: 8561
repository: Foundation
deployment: Remote Services
]

Should be able to be processed with a logFormat field like this:
TIMESTAMP [LEVEL] LOGGER - [MESSAGE]

However, this results in a non-matching entry (see logging output, for example
Chainsaw's chainsaw-log tab).

Multi-line entries work fine if the MESSAGE field is not delimited on both
sides.  For example, this entry:

2006-02-10 16:09:36,977 [INFO] ejb.SecurityManagerBean - MA Core connected to
remote services...
host: nlveus13.xxxx.com
port: 8561
repository: Foundation
deployment: Remote Services

Will be processed correctly with this logFormat:
TIMESTAMP [LEVEL] LOGGER - MESSAGE
Comment 1 Thorbjørn Ravn Andersen 2008-08-02 10:32:10 UTC
Version 1.3 is discontinued, and LogFilePatternAppender does not exist (afaics) in 1.2.  Marking issue WONTFIX.
Comment 2 Scott Deboy 2008-08-02 18:13:16 UTC
LogFilePatternReceiver is a part of the receivers companions..see http://logging.apache.org/log4j/companions/receivers/apidocs/org/apache/log4j/varia/LogFilePatternReceiver.html