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=42921>.
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=42921
Summary: DBReceiverJob queries with wrong datatype.
Product: Log4j
Version: 1.3alpha
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: chainsaw
AssignedTo: log4j-dev@logging.apache.org
ReportedBy: richard.landers@ct.gov
DBReceiverJob queries LOGGING_EVENT_PROPERTIES and LOGGING_EVENT_EXCEPTION with
EVENT_ID expressed as a string (in single quotes). On DB2, at least, this
results in SQL Errors whenever a LOGGING_EVENT has associated properties or
exceptions.
This bug manifests itself in Chainsaw when the DBRecieverJob only retrieves a
portion of the LOGGING_EVENTS available in the database. As soon as a
LOGGING_EVENT has an associated property or exception, the loop iterating over
LOGGING_EVENTS exits because of an SQLException.
The solution is to remove the single-quotes from the EVENT_ID arguments of the
SQL queries on lines 164 and 197 of DBReceiverJob.java.
--
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
|