Relevance evaluation not completing (via Web Reports SOAP interface)

Reporting
1

(imported topic written by SystemAdmin)

Hello there,

I’m currently having a problem when trying to retrieve

results

from

bes fixlets

via the Web Reports SOAP interface. I simply get no response back and the SOAP client returns a read timeout.

Here is a working request:

Relevance:

number of bes fixlets whose ( (name of site of it = 
"Enterprise Security" OR name of site of it = 
"Updates for Windows Applications" OR name of site of it = 
"Vulnerabilities to Windows Systems"))

SOAP request:

POST /soap HTTP/1.1 Content-Type: text/xml; charset=UTF-8 SOAPAction: 
"http://schemas.bigfix.com/Relevance/soapaction" User-Agent: Axis2 Host: tem:9090 Content-Length: 600   <?xml version=
'1.0' encoding=
'UTF-8'?><soapenv:Envelope xmlns:soapenv=
"http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><ns1:GetRelevanceResult xmlns:ns1=
"http://schemas.bigfix.com/Relevance"><ns1:relevanceExpr>number of bes fixlets

whose (
(name of site of it =
“Enterprise Security” OR
name of site of it =
“Updates for Windows Applications” OR
name of site of it =
“Vulnerabilities to Windows Systems”))</ns1:relevanceExpr>ns1:usernamewebadmin</ns1:username>ns1:password********</ns1:password></ns1:GetRelevanceResult></soapenv:Body></soapenv:Envelope>

and Response:

HTTP/1.1 200 OK Content-type: text/xml   <?xml version=
"1.0" encoding=
"UTF-8"?> <soapenv:Envelope xmlns:soapenv=
"http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body> <GetRelevanceResultResponse xmlns=
"http://schemas.bigfix.com/Relevance"> <a>10154</a> </GetRelevanceResultResponse> </soapenv:Body> </soapenv:Envelope>

Here is a failing request:

Relevance:

number of results of bes fixlets whose ( (name of site of it = 
"Enterprise Security" OR name of site of it = 
"Updates for Windows Applications" OR name of site of it = 
"Vulnerabilities to Windows Systems"))

SOAP request:

POST /soap HTTP/1.1 Content-Type: text/xml; charset=UTF-8 SOAPAction: 
"http://schemas.bigfix.com/Relevance/soapaction" User-Agent: Axis2 Host: tem:9090 Content-Length: 611   <?xml version=
'1.0' encoding=
'UTF-8'?><soapenv:Envelope xmlns:soapenv=
"http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><ns1:GetRelevanceResult xmlns:ns1=
"http://schemas.bigfix.com/Relevance"><ns1:relevanceExpr>number of results of bes fixlets

whose (
(name of site of it =
“Enterprise Security” OR
name of site of it =
“Updates for Windows Applications” OR
name of site of it =
“Vulnerabilities to Windows Systems”))</ns1:relevanceExpr>ns1:usernamewebadmin</ns1:username>ns1:password********</ns1:password></ns1:GetRelevanceResult></soapenv:Body></soapenv:Envelope>

I never see any response.

A debug trace of Web Reports shows entry to the Relevance Evaluation function… but it never returns.

Wed, 18 Jan 2012 15:48:52 +0000 -- / (3988) -- User webadmin authenticated successfully Wed, 18 Jan 2012 15:48:52 +0000 -- / (3988) --     Entering WebReportsRelevanceEvaluator::Evaluate( number of results of bes fixlets whose ( (name of site of it = 
"Enterprise Security" OR name of site of it = 
"Updates for Windows Applications" OR name of site of it = 
"Vulnerabilities to Windows Systems")) ) <nothing more>

If I run the failing relevance query via the Presentation Editor it returns 0 - but I assume this is because it is running in Console context and not Web Reports context.

What could be the problem here? I wonder if the evaluation is timing out, or running out of memory, but I don’t see any errors like that in the Web Reports debug log (set to “all” messages). Maybe I’m looking in the wrong place?

I’m running TEM 8.2 (Server is 8.2.1093.0).

Thanks in advance.

Jon.

2

(imported comment written by SSYU_P_Grey)

Hi John,

My understanding is that there were no problems running these queries against TEM 8.0.1. Is that true?

3

(imported comment written by SystemAdmin)

I didn’t try it myself but the relevance I’m failing to get working was developed against TEM 8.0.2.

4

(imported comment written by Lee Wei)

This is likely bug# 46892 “Slow session relevance statement (fixlet results) in 8.2”.

The intent was to load Fixlet results from the database on demand rather than pre-caching it as was previously.

This is done to reduce memory footprint.

Engineering intends to fix this for the next release, but I don’t know the scheduled date.

Lee Wei

5

(imported comment written by SystemAdmin)

Thanks Lee Wei - sounds promising.

6

(imported comment written by SystemAdmin)

Hello there,

I just found some time to retest this now that my TEM Server is running 8.2.1175.0.

I don’t see any change in behaviour; I still get the same timeouts.

Can anyone confirm whether the fix mentioned above is in the version I’m now running?

Thanks… Jon.