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

Bug 147102

Summary:	Find Log Record "Find Next" button doesn't always enable
Product:	z_Archived	Reporter:	Ruth Lee <ruthdaly>
Component:	TPTP.monitoring	Assignee:	vrushali satpute <vsatpute>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P1	CC:	ewchan, jkubasta, rohit.shetty, smith
Version:	unspecified	Keywords:	plan
Target Milestone:	---
Hardware:	PC
OS:	Windows 2000
Whiteboard:	closed460

Description Ruth Lee

2006-06-14 14:42:43 EDT

1. Create a time based correlation between access_V400_Apache.log and error_V400_Apache.log. 
2. Highlight the correlation, right click, open with > log interactions.
3. Open the Find Log Record dialog, enter Severity = 50. 
4. In the Log Navigator view, change the focus from the correlation to the apache error log. Select the Find Log Record dialog again; "Find Next" is disabled. Change several values in the Find Log Record dialog but "Find Next" remains disabled. Close the dialog and reopen it and "Find Next" is enabled.

Comment 1 Eugene Chan

2006-09-25 10:39:34 EDT

Targeting to post 4.3 release.

Comment 2 Eugene Chan

2007-01-31 18:32:43 EST

Target to future. Cannot be contained in 4.4 due to limitation of resource.

Comment 3 Eugene Chan

2007-01-31 23:35:49 EST

Move target back to 4.4. Trace defects are mistakenly targeted in bulk move.

Comment 4 Dave Smith

2007-04-12 13:11:03 EDT

Re-assigning to Vrushali

Comment 5 vrushali satpute

2007-04-16 07:58:35 EDT

Hello Eugene,

While reproducing Bug 147102,I found that functionality is working fine.

"Find Log Record dialog" works for Log Interation and Log view. If Log interation view or Log View is selected the "Find Next" button of "Find Log Record dialog" will be enabled. But if current selection is Log navigator View "find Next" button will be disabled as find log record functionality is not intended for that view.

Log Interation View or Log View can be selected by double clicking Log files or correlation from the Log Navigator and "Find Next" button will get enabled after selection of that. so I believe that functioanlity is working as per designed.

Comment 6 Eugene Chan

2007-04-16 11:27:15 EDT

Hi Vrushali, you are correct. I also verify with tptp.runtime.allInOne.win32.win32.x86-TPTP-4.4.0-200703270100C build and it's working as design.

Comment 7 Paul Slauenwhite

2009-06-30 09:49:56 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 8 Paul Slauenwhite

2009-06-30 09:52:38 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.