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

Bug 101367

Summary: [Markers] Problems view in GLA editor not being refreshed properly - missing problems
Product: [Eclipse Project] Platform Reporter: Dave Smith <smith>
Component: UIAssignee: Tod Creasey <Tod_Creasey>
Status: CLOSED DUPLICATE QA Contact:
Severity: major    
Priority: P3 CC: popescu
Version: 3.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows 2000   
Whiteboard:
Attachments:
Description Flags
Sample GLA adapter file for reproducing the problem
none
Sample Apache access log file to parse with GLA adapter file. none

Description Dave Smith CLA 2005-06-22 17:40:31 EDT
After creating a new adapter file in the Editor, I run it by clicking the Rerun 
adapter button.  Seven to nine error messages are displayed in the Problems 
view but at the top of the view it says there are 15.  There should be 15 
messages because there are 15 events in the Editor buffer and they are all 
incorrect so there should be a message for each on.  If I click on the Filters 
button on the Problems view and then click OK, then all 15 messages are 
displayed.  There seems to be a problem with the Problems view getting 
refreshed.
Comment 1 Valentina Popescu CLA 2005-06-22 22:28:50 EDT
Dave, I don't own or control what is displayed in the Problems view

This is part of the eclipse framework so please redirect the bug
Comment 2 Dave Smith CLA 2005-06-28 16:00:18 EDT
Valentina looked at this problem some more and could not determine a fix.  It 
may be a bug in the eclipse platform where the Problems view does not get 
refreshed completely when old markers are deleted and new ones are created.  Or 
it may be a problem in how we are calling the delete and create marker API's.

This cannot be contained in 4.0 but the problem will be added to the 4.0 
Readme. Deferring to 4.1.
Comment 3 Ruth Lee CLA 2005-06-28 18:05:36 EDT
Temporarily moving this back to 4.0 because I need to test if the 4.0 Monitoring
query is fixed. I'll move this back to 4.1 after the test is done.
Comment 4 Ruth Lee CLA 2005-06-28 18:06:07 EDT
Moving back to 4.1. 
Comment 5 Dave Smith CLA 2005-07-07 13:37:18 EDT
Created bugzilla 103043 to add 4.0 readme item for this problem.
Comment 6 Dave Smith CLA 2005-10-11 14:13:03 EDT
This appears to be a problem with the Problems view not being refreshed when 
old markers are deleted and new ones are created when the Adapter is rerun 
after being run at least once.  During adapter initialization,  
org.eclipse.hyades.logging.adapter.internal.util.GlaTaskOutputter.update() 
deletes any existing markers associated with the resource (the adapter file). 
During adapter execution, 
org.eclipse.hyades.logging.adapter.internal.util.GlaTaskOutputter.processCBEs 
method creates problem markers for the resource.

Here is how to reproduce this problem:
1) Install the TPTP 4.0 Runtime zip 
(http://www.eclipse.org/downloads/download.php?file=/tptp/4.0.0/TPTP-4.0.0-
200507181519/tptp.runtime-TPTP-4.0.0-200507181519.zip) on top of the Eclipse 
SDK 3.1.0, EMF 2.1.0, XSD 2.1.0.
2) Start Eclipse
3) Create a Simple Project in your workspace called GLAAdapterFiles
4) Copy and paste the attached GLA adapter file gla.adapter into the 
GLAAdapterFiles project.
5) Open the Generic Log Adapter perspective.
6) Double click the gla.adapter file in the Navigator window to open the file 
with the Adapter Configuration Editor.
7) In the top pane of the editor expand Adapter, then Configuration, then 
Context Instance, then "Sensor A single file sensor".
8) Download the attached sample log file apacheaccess.log to your system.
9) In the editor, change the values of "Property directory" and "Property 
fileName" under Sensor, if necessary, for the location of sample log on your 
system.
10) Select Context Instance in the top pane of the editor and then in the 
Extractor Result pane of the editor click the left most tool bar button (green 
triangle with yellow arrow) to run the adapter file.
11) Select the Problems tab in the bottom right pane of the editor.  The 
heading on Problems view should say "15 errors, 1 warning 0 infos".  However, 
the table below the heading may or may not show all 15 errors.  
12) If the Problems view does show all 15 errors, then in the top pane of the 
editor, enter 1000 in the "Maximum idle time" field of the Context Instance and 
save the adapter file by Ctrl-S.  The Problems view should be cleared.
13) Rerun the adapter by clicking the left most tool bar button (green triangle 
with yellow arrow) in the Extractor Result pane.
14) Again the Problems view heading should say "15 errors, 1 warning 0 infos" 
but the table won't show all 15 errors.  For me it only shows 5 errors and 1 
warning.
15) Click the Filters button (button with two black arrows and one bigger 
yellow arror) on the tool bar of the bottom right pane. In the Filters dialog 
window that is displayed, just click the OK button.  The Problems view is 
refreshed and 15 errors and 1 warning are correctly shown.

The markers are associated with the resource but they are not shown in the 
Problems view until it is manually refreshed using the Filter dialog.
Comment 7 Dave Smith CLA 2005-10-11 14:14:15 EDT
Created attachment 28123 [details]
Sample GLA adapter file for reproducing the problem
Comment 8 Dave Smith CLA 2005-10-11 14:15:54 EDT
Created attachment 28125 [details]
Sample Apache access log file to parse with GLA adapter file.
Comment 9 Dave Smith CLA 2005-10-11 14:26:25 EDT
Reassigning this problem because I believe it is a problem in the Eclipse 
Plaform.  Please reassign to the appropriate owner, if necessary.
Comment 10 Tod Creasey CLA 2006-04-07 14:37:15 EDT

*** This bug has been marked as a duplicate of 113455 ***
Comment 11 Paul Slauenwhite CLA 2009-06-30 09:58:15 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 12 Paul Slauenwhite CLA 2009-06-30 10:51:11 EDT
This enhancement/defect was mistaken closed as part of the TPTP 4.6 Bugzilla
housecleaning process (see
http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes) since the originator
of this enhancement/defect has an inactive Bugzilla account.  If this
enhancement/defect is still unresolved and reproducible, please re-open.