My statement was an terse argument for using CBE/Java Logging which it
appears you are using.
Back to the original defect, I guess I do not understand the problem since
the details are sparse. In Java Logging, setting the logging level to
critical, for example, will filter all lower levels.
PS
---------------------------------------------
Paul Slauenwhite
IBM Toronto Lab, Canada
Internet: [EMAIL PROTECTED]
Telephone: (905) 413-3861
Tie Line: 969-3861
---------------------------------------------
Ashish
Patel/Toronto/IBM
@IBMCA To
Sent by: "TPTP PMC communications (including
tptp-pmc-bounces@ coordination, announcements, and
eclipse.org Group discussions)"
<[EMAIL PROTECTED]>
cc
10/25/2006 12:58 [EMAIL PROTECTED], TPTP
AM Tracing and Profiling Tools Project
developer discussions
<[EMAIL PROTECTED]
Please respond to clipse.org>, "TPTP PMC
"TPTP PMC communications \(including
communications coordination, announcements, and
\(including Group discussions\)"
coordination, <[EMAIL PROTECTED]>
announcements, Subject
and Group RE: [tptp-pmc] Re:
discussions\)" [tptp-tracing-profiling-tools-dev]
<[EMAIL PROTECTED] Request for PMC/PG
.org> Approval: Tracing and Profiling
Project - 4.3 i3 Defects.
The logging was in existence since the original contribution of code for
the ARM component from IBM. The IBM recommendation during initial
development was to log to CBEs because the code was running as a separate
java process from the workbench. As a result, we have maintained similar
logging throughout the code for consistency.
I don't understand what you're trying to get at with your statement:
"Java Logging which has clear definitions for the various logging levels,
included as part of the JRE, integrated with TPTP (CBE) and is highly
configurable?"
If you don't want the log to come out as CBE we have a file in the AC
plugin called ARMLogger.properties. In there is a definition for the
logging format. By default this is set to "CBE" - if you want plain text
then you enter "PlainTextFormatter" << this I believe is standard to java
logging.
Please let me know if you have another concern regarding this topic.
Thanks,
Ashish Patel
Lead Developer for IBM Performance Optimization Toolkit (IPOT)
Lead Eclipse Committer for ARM
IBM Toronto Lab
tel: (905) 413-3867 | t/l: 969-3867 | fax: (905) 413-4850
[EMAIL PROTECTED]
Paul
Slauenwhite/Toronto/IBM
@IBMCA To
Sent by: "TPTP PMC communications (including
[EMAIL PROTECTED] coordination, announcements, and
e.org Group discussions)" <[EMAIL PROTECTED]>
cc
[EMAIL PROTECTED], TPTP Tracing
24/10/2006 11:26 AM and Profiling Tools Project developer
discussions
<[EMAIL PROTECTED]
Please respond to g>, "TPTP PMC communications \(including
"TPTP PMC coordination, announcements, and
communications Group discussions\)" <[EMAIL PROTECTED]>
\(including Subject
coordination, RE: [tptp-pmc] Re:
announcements, [tptp-tracing-profiling-tools-dev] Request
and Group for PMC/PG Approval: Tracing
discussions\)" and Profiling Project - 4.3 i3 Defects.
<[EMAIL PROTECTED]>
+1 assuming there are sufficient test cases to cover 148475.
Also, for 158581, why are we not using Java Logging which has clear
definitions for the various logging levels, included as part of the JRE,
integrated with TPTP (CBE) and is highly configurable?
PS
---------------------------------------------
Paul Slauenwhite
IBM Toronto Lab, Canada
Internet: [EMAIL PROTECTED]
Telephone: (905) 413-3861
Tie Line: 969-3861
---------------------------------------------
"Nagarajan, Guru"
<[EMAIL PROTECTED]
ntel.com> To
Sent by: "TPTP PMC communications (including
tptp-pmc-bounces@ coordination, announcements, and
eclipse.org Group discussions)"
<[EMAIL PROTECTED]>, "TPTP
Tracing and Profiling Tools Project
10/23/2006 09:25 developer discussions"
PM <[EMAIL PROTECTED]
clipse.org>
cc
Please respond to
"TPTP PMC Subject
communications RE: [tptp-pmc] Re:
\(including [tptp-tracing-profiling-tools-dev]
coordination, Request for PMC/PG Approval:
announcements, Tracing and Profiling Project - 4.3
and Group i3 Defects.
discussions\)"
<[EMAIL PROTECTED]
.org>
All the bugs below are part of the ARM Preview offering. Affects only ARM
and does not affect the rest of TPTP
148472 : This bug has been closed, since it has hence been noted that this
bug was resolved earlier and the bug was not closed.
148475: A number of Probes were added for ARM instrumentation. These
probes were added for different analysis types and one of the probes to be
supported under this is the JDBC instrumentation.
There is a need to capture additional context information via the JDBC
layer for ARM to Complete the JDBC analysis type support. There are a
number of other analysis types for which probes are being provided under
the ARM offering and this is an incremental code addition.
158581: Currently, in the ARM offering the error logging is default to
Severe/critical and the user sees ?Warnings" and "Informational" errors as
critical issues. This is extremely misleading to the user.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Valentina Popescu
Sent: Monday, October 23, 2006 12:27 PM
To: TPTP Tracing and Profiling Tools Project developer discussions
Cc: TPTP Tracing and Profiling Tools Project developer discussions; TPTP
PMC communications (including coordination, announcements,and Group
discussions); [EMAIL PROTECTED]
Subject: [tptp-pmc] Re: [tptp-tracing-profiling-tools-dev] Request for
PMC/PG Approval: Tracing and Profiling Project - 4.3 i3 Defects.
Guru,
+1 for 161320
148472
- has been upgraded today from normal to critical , P1. The defect
description doesn't state more than the need for an RMI probe. Can you add
more information to the defect please so that the severity of the defect
can be assessed. Things I need to know before I can vote
- what is the actual problem or requirement
- why is this critical
- is this a GA or tech preview function
- what is the code/test impact for providing a fix
- what is the impact for not providing a fix in 4.3
148475 same comments as above
158581 same comments as above
Thank you,
Valentina Popescu
Senior Advisory Analyst
IBM Toronto Labs
Phone: (905)413-2412 (tie-line 969)
Fax: (905) 413-4850
"Nagarajan, Guru"
<[EMAIL PROTECTED]
m>
Sent by: To
tptp-tracing-profiling-t "TPTP PMC communications (including
[EMAIL PROTECTED] coordination, announcements, and
.org Group discussions)" <[EMAIL PROTECTED]>,
"TPTP Tracing and Profiling Tools Project
developer discussions"
10/23/2006 03:16 PM <[EMAIL PROTECTED]
g>
cc
Subject
[tptp-tracing-profiling-tools-dev] Request
Please respond to for PMC/PG Approval: Tracing and
TPTP Tracing and Profiling Project - 4.3 i3 Defects.
Profiling Tools Project
developer discussions
<tptp-tracing-profiling
[EMAIL PROTECTED]>
PMC/PG,
Following today?s Tracing and Profiling weekly project call, we are
requesting PMC/PG approval for the following additional 4.3 i3 defects:
161320 The percentage icon in the toolbar icon of the Method Invocations
tab does not work. There is a patch on hand for this and has been tested.
The following affect the ARM preview feature:
148472 Need probekit .probe file for RMI-IIOP instrumentation
148475 Need probekit .probe file for JDBC instrumentation
158581 Provide error logging at different levels than SEV_CRIT
Thanks,
Guru_______________________________________________
tptp-tracing-profiling-tools-dev mailing list
tptp-tracing-profiling-tools-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/tptp-tracing-profiling-tools-dev
_______________________________________________
tptp-pmc mailing list
[EMAIL PROTECTED]
https://dev.eclipse.org/mailman/listinfo/tptp-pmc
_______________________________________________
tptp-pmc mailing list
[EMAIL PROTECTED]
https://dev.eclipse.org/mailman/listinfo/tptp-pmc
_______________________________________________
tptp-pmc mailing list
[EMAIL PROTECTED]
https://dev.eclipse.org/mailman/listinfo/tptp-pmc
_______________________________________________
tptp-tracing-profiling-tools-dev mailing list
tptp-tracing-profiling-tools-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/tptp-tracing-profiling-tools-dev
