Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 194850

Summary: Messages and exceptions written to Eclipse .log file
Product: z_Archived Reporter: Dave Smith <smith>
Component: TPTP.monitoringAssignee: Hariharan L Narayanan <harihnar>
Status: CLOSED WONTFIX QA Contact:
Severity: major    
Priority: P2 CC: analexee, apnan, hollisc, jacalcat, jkubasta
Version: unspecifiedKeywords: plan
Target Milestone: ---   
Hardware: PC   
OS: Windows 2000   
Whiteboard: closed460
Attachments:
Description Flags
Eclipse log containing MAX messages none

Description Dave Smith CLA 2007-06-28 17:51:41 EDT 
Opening the Managed Agent Explorer with a JMX resource results in many messages and exceptions written to the Eclipse .log file.  I launched MAX with a JMX configuration to manage Apache Tomcat and many errors were written to the .log.  I'll attach a file with the errors.  I was using the TPTP 4.4 GA build.  MAX should not write warning messages and exception stack traces to the Eclipse log.  Any errors that the user needs to know about should be displayed in an error dialog.  Note, similar messages are written to the Eclipse log when opening MAX from the Windows -> Show View -> Other ... -> Managed Agent menu.
Comment 1 Dave Smith CLA 2007-06-28 17:52:25 EDT 
Should try to fix this in 4.4.1
Comment 2 Dave Smith CLA 2007-06-29 02:02:23 EDT 
Created attachment 72757 [details]
Eclipse log containing MAX messages
Comment 3 Alex Nan CLA 2007-08-30 10:14:04 EDT 
Please retarget this to 4.5, my understanding is that it requires new PII changes.
Comment 4 Alex Nan CLA 2007-08-30 10:14:45 EDT 
Retargetting...
Comment 5 Alex Nan CLA 2008-02-22 11:34:43 EST 
Sounds like this defect is conflicting with bug 185625 which has been fixed in i4.5 i5.
Returning this defect. Reopen if you consider that the fix in bug 185625 is not satisfactory.
Comment 6 Paul Slauenwhite CLA 2009-06-30 09:55:54 EDT 
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this originator of this enhancement/defect has an inactive Bugzilla account and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
Comment 7 Paul Slauenwhite CLA 2009-06-30 09:56:32 EDT 
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since the originator of this enhancement/defect has an inactive Bugzilla account and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.