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

Bug 203604

Summary:	Analyze selection reports don't work.
Product:	z_Archived	Reporter:	Giorgio Basilisco <giorgio.basilisco>
Component:	TPTP.monitoring	Assignee:	Alex Nan <apnan>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P1	CC:	apnan, ewchan, giorgio.basilisco
Version:	unspecified	Keywords:	plan
Target Milestone:	---
Hardware:	PC
OS:	Windows 2000
Whiteboard:	closed460

Description Giorgio Basilisco

2007-09-17 11:17:23 EDT

Build ID: 3.3.0

Steps To Reproduce:
I have the plugin that extend LogAnalyzer. In the version 3.1 this work.I have upgraded a SymptomDB to version 2.0. When I run the plugin,I see a Log Records,I see the symptom definitions but when I click on log record > Analyze selection I don't receve the result.
The XPath expression is correct but don't match in some case (e.g. /CommonBaseEvent[contains(@msg, 'AWSBAB001I')]) in my log record the value of CommonBaseEvent XML is :
<?xml version="1.0" encoding="UTF-8"?>
<CommonBaseEvents xmlns="http://www.ibm.com/AC/commonbaseevent1_0_1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.ibm.com/AC/commonbaseevent1_0_1 commonbaseevent1_0_1.xsd">
	<CommonBaseEvent creationTime="2005-11-04T00:52:47.000000+01:00" extensionName="CBECommonBaseEvent" globalInstanceId="TWS83NEW_2005-11-03T24:52:47+01:00_3940" msg="TWS83NEW:MAILMAN:AWSBAB001I my problem test+" elapsedTime="0" priority="0" repeatCount="0" sequenceNumber="3940" severity="50" version="1.0.1">
		<extendedDataElements name="timeZone" type="string">
			<values>+01:00</values>
		</extendedDataElements>
		<extendedDataElements name="twsCpuName" type="string">
			<values>TWS83NEW</values>
		</extendedDataElements>
		<extendedDataElements name="twsLogOffset" type="string">
			<values>0</values>
		</extendedDataElements>
		<extendedDataElements name="twsComponent" type="string">
			<values>MAILMAN</values>
		</extendedDataElements>
	</CommonBaseEvent>
</CommonBaseEvents>


More information:

Comment 1 Alex Nan

2007-09-17 16:08:13 EDT

Giorgio, the problem is that your parser is not setting a source component id for the generated CommonBaseEvent objects. The component attribute of the ComponentIdentification object is also mandatory. The XPath analysis engine assumes this and unfortunately is not doing any checking, so the emitting of symptoms is failing, this is the reason why not result is generated.
Please fix the parser accordingly and the analyze will work fine. 
I will keep this defect to do the changes neccessary to prevent this kind of situation but please lower the severity to normal.

Comment 2 Giorgio Basilisco

2007-09-18 05:31:54 EDT

I have tried with add the source component id but don't work

The code of change :

private final static ComponentIdentification netmanComponentID = null;

    	netmanComponentID.setExecutionEnvironment(environment);
    	netmanComponentID.setComponent(component);
    	netmanComponentID.setSubComponent(subComponent);
    	netmanComponentID.setComponentIdType(componentIdType);
    	netmanComponentID.setComponentType(componentType);
    	netmanComponentID.setLocation("localHostId");
    	netmanComponentID.setLocationType("localHostIdFormat");

ComponentIdentification netmanComponentID = eventFactory.createComponentIdentification();

 messages[arrayIndex].setSourceComponentId(netmanComponentID);

But when I see e properties of Log Record I don't see a Source Component Value,these is all empty. (e.g. Component Name,Classification Type,....)

Comment 3 Giorgio Basilisco

2007-09-18 07:05:46 EDT

I have fix the problem...now I see the SourceComponent properties and the XPath match the situations.

Comment 4 Alex Nan

2007-09-18 08:43:35 EDT

I'm glad to hear that the problem was fixed.

Comment 5 Alex Nan

2007-10-30 23:22:40 EDT

Assigning to i2 for now.

Comment 6 Alex Nan

2007-11-05 18:20:49 EST

Changing target to 4.5 i4.

Comment 7 Alex Nan

2007-11-22 18:35:41 EST

Provided unknown component name in case the source component of a CBE is not set. Created a resource bundle for the messages used by the XPathCorrelation engine, independent of the editor.

Comment 8 Paul Slauenwhite

2009-06-30 13:17:17 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.