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

Bug 79843

Summary:	Importing non-existent log file produces no error messages
Product:	z_Archived	Reporter:	Valentina Popescu <popescu>
Component:	Hyades	Assignee:	Dave Smith <smith>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	curtispd
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 2000
Whiteboard:	closed460

Description Valentina Popescu

2004-11-30 21:10:13 EST

Import -> Log File
Select "IBM Websphere Application Server activity log"

Select a valid server with a working RAC and a valid connection, enter the 
correct websphere server installation directory, but enter an _incorrect_ file 
path for the log (a non-existent log file). Click Ok, Finish.

The log view comes up with an empty log, the profiling monitor view says the 
agent has terminated. But, there is no indication to the user that the 
operation failed. The user is left guessing why the log is empty.

Comment 1 Eugene Chan

2004-12-09 16:48:03 EST

Assign to Dave as requested

Comment 2 Dave Smith

2004-12-09 16:49:39 EST

The GLA runtime support to return messages to the UI has been added with 
bugzilla 61256.

*** This bug has been marked as a duplicate of 61256 ***

Comment 3 Curtis d'Entremont

2004-12-09 17:01:25 EST

Does this mean it does it, or that it only supports it?

Comment 4 Dave Smith

2004-12-09 18:06:46 EST

With the 61256 fix, GLA now throws exceptions for configuration problems like 
file not found, which are caught by the Log Import wizard which then has 
support for showing an error message window with the exception message.  What 
is not supported yet by the Log Import Wizard is showing errors that occur 
during parsing (ie bad data in a particular log record or incorrect rules to 
parse the data) that GLA logs but doesn't throw an exception for.  These are 
errors that don't prevent GLA from continuing to parse the log file but do 
result in loss of parsed log data that the user might want to be aware of.

Comment 5 Dave Smith

2005-02-15 00:44:24 EST

Investigated for 3.3 release.

Comment 6 Dave Smith

2005-04-12 15:39:54 EDT

This feature enhancement (return error to Log import UI if log file does not 
exist) was completed in 3.2 i2.

Comment 7 Paul Slauenwhite

2009-06-30 12:31:52 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 enhancement/defect has been resolved and unverified for more than 1 year 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.