You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2006/03/07 16:41:37 UTC
DO NOT REPLY [Bug 38883] New: - LogFilePatternReceiver fails to process multi-line event if message field is delimited on both sides
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38883>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38883
Summary: LogFilePatternReceiver fails to process multi-line event
if message field is delimited on both sides
Product: Log4j
Version: 1.3alpha
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: Other
AssignedTo: log4j-dev@logging.apache.org
ReportedBy: sdeboy@iname.com
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
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org