10.3 Portal: Inspection view empty

[Philippe Bernard]

Hi,

Inspection view, in Portal, doesn't show any data for VS - however session data is OK.
We updated the property "log4j.logger.VSE" in logging.properties: with different values: "DEBUG, VSEAPP",  "TRACE, VSEAPP", "INFO,VSEAPP" 
but without any effect.
vse_matches.log and VS_<virtual service name>.log files are there and updated, so what's wrong with the inspection view ?

Thanks.

[Premalatha Gadde]

Hi Philippe,

Which version of DevTest are you using? Can you share the screenshot of Inspection view? 

Regards,
Prema

[Sankar Natarajan]

Hi Philippe
                  In addition to providing what Premas has asked, please check the following settings too. These two settings play a roll in showing the events in inspection view.

File: LISA_HOME\lisa.properties

# This property controls how many inbound VSE requests for which a full set of DevTest events is
# buffered. The number of events is per VS model so if you have 2 VS models deployed with the
# default request buffer size of 5, then a total of 10 sets of events (grouped by inbound
# request) will be buffered. These sets of events are the source for the "Events" tab of the
# VS model inspection page in the VSE dashboard.
lisa.vse.request.event.set.buffer.size=50

# This property controls how many VSE matching related events are buffered. The number of
# events is per VS model so if you have 2 VS models deployed with the default event buffer size
# of 100, then a total of 200 events will be buffered. These events are the source for the
# "Match" tab of the VS model inspection page in the VSE dashboard.
lisa.vse.match.event.buffer.size=100

regards
Sankar

------------------------------
Sankar Natarajan
Service Virtualization Product Engineering Team
Broadcom
------------------------------

[Philippe Bernard]

Hi SAnkar,

Thanks - as in the title, it is 10.3 version.
Here is the lisa.properties:

# This property controls how many VSE matching related events are buffered. The number of
# events is per VS model so if you have 2 VS models deployed with the default event buffer size
# of 100, then a total of 200 events will be buffered. These events are the source for the
lisa.vse.match.event.buffer.size=100
# This property controls how many inbound VSE requests for which a full set of DevTest events is
# buffered. The number of events is per VS model so if you have 2 VS models deployed with the
# default request buffer size of 5, then a total of 10 sets of events (grouped by inbound
# request) will be buffered. These sets of events are the source for the "Events" tab of the
lisa.vse.request.event.set.buffer.size=50


Regards
Philippe.

[Sankar Natarajan]

Hi Philippe
             These setting are looking good. Please could you open the developer tools and check if you notice any errors in the 'console' tab or 'network' tab. Shown below is the developer tools in chrome browser when the inspection view is refreshed by clicking the icon at top right corner of inspection view.

------------------------------
Sankar Natarajan
Service Virtualization Product Engineering Team
Broadcom
------------------------------

[Philippe Bernard]

Hi Sankar,

I see no error in the network tab:

but one error in the console:

Regards
Philippe.

[Sankar Natarajan]

Hi Philippe
            Thanks for your response. Please could you follow the steps below in order to isolate the 'Console error' as the root cause of empty inspection view.

1. Clear the contents of 'Console tab' of developer tools
2. Clear contents of 'Network tab' of developer tools
3. Refresh the inspection view (using top right icon)
4. Observe if you still see the JSON Parse Error in console tab
5. If you still find the same error in console, then please go to 'Network tab'. Click on the url that fetches inspection view data (something similar to http://localhost:1507/devtest/api/sv/vse/service/inspectionData/VSE/<VS NAME>). Go to response tab and copy the response data. It will be in JSON format, something like the one shown below. Please share the JSON data.

{"message":"","value":{"errData":[],"matchData":[],"reqData":[{"steps":[{"events":[{"eventId":6,"instance":1,"longInfo":"N/A","modelName":"VS_LiveInvoke01","robot":0,"runName":null,"shortInfo":"N/A","simulator":"local","stepName":"N/A","timestamp":1546155955234,"timestampStr":"2019-08-12T07:45:55.234+0000"},{"eventId":11,"instance":1,"longInfo":"","modelName":"VS_LiveInvoke01","robot":0,"runName":null,"shortInfo":"373D981ABCD511E9A8E1FA9EB42804A1","simulator":"local","stepName":"","timestamp":1546155955238,"timestampStr":"2019-08-12T07:45:55.238+0000"},{"eventId":17,"instance":1,"longInfo":"Request {id=0, operation=\"POST /v1/risksimtestserv/decision\", arguments=, attributes=HTTP-Segment-Attr-0=v1&HTTP-Segment-Attr-1=risksimtestserv&HTTP-Segment-Attr-2=decision, metaData=HTTP-Method=POST&HTTP-URI=/v1/risksimtestserv/decision&HTTP-Version=1.1&Content-Type=application/json&cache-control=no-cache&Postman-Token=edac3cb3-7163-4c32-9703-d16aeeac2454&User-Agent=PostmanRuntime/7.6.0&Accept=*/*&Host=localhost:8111&cookie=ca_devtest_landing_url=http://localhost:1507&accept-encoding=gzip, deflate&content-length=42&Connection=keep-alive&lisa.vse.request.client.id=127.0.0.1:49806, matchTolerance=Exact, binary=false, body=(non-binary)[42 bytes] {\"amount\":\"200.00\",\"account_id\":\"12345\"}\r\n}","modelName":"VS_LiveInvoke01","robot":0,"runName":null,"shortInfo":"Virtual HTTPS Listener 8111","simulator":"local","stepName":"Virtual HTTPS Listener 8111","timestamp":1546158845011,"timestampStr":"2019-08-12T08:34:05.011+0000"},{"eventId":47,"instance":1,"longInfo":"Respond from: {\"id\":6,\"request\":{\"id\":14,\"matchTolerance\":\"EXACT\",\"operation\":\"POST /v1/risksimtestserv/decision\",\"arguments\":{\"account_id\":\"12345\",\"amount\":\"200.00\"}}}","modelName":"VS_LiveInvoke01","robot":0,"runName":null,"shortInfo":"INFO: Transaction Navigator","simulator":"local","stepName":"VS Image Response Selection","timestamp":1546158845036,"timestampStr":"2019-08-12T08:34:05.036+0000"},{"eventId":17,"instance":1,"longInfo":"A 1 entry response list.","modelName":"VS_LiveInvoke01","robot":0,"runName":null,"shortInfo":"VS Image Response Selection","simulator":"local","stepName":"VS Image Response Selection","timestamp":1546158845040,"timestampStr":"2019-08-12T08:34:05.040+0000"}],"stepName":"Virtual HTTPS Listener 8111"},{"events":[{"eventId":15,"instance":1,"longInfo":"","modelName":"VS_LiveInvoke01","robot":0,"runName":null,"shortInfo":"Virtual HTTPS Responder","simulator":"local","stepName":"Virtual HTTPS Responder","timestamp":1546158845040,"timestampStr":"2019-08-12T08:34:05.040+0000"},{"eventId":18,"instance":1,"longInfo":"10","modelName":"VS_LiveInvoke01","robot":0,"runName":null,"shortInfo":"Virtual HTTPS Responder","simulator":"local","stepName":"Virtual HTTPS Responder","timestamp":1546158845922,"timestampStr":"2019-08-12T08:34:05.922+0000"}],"stepName":"Virtual HTTPS Responder"}]}],"vsiNames":["Test_LiveInvoke01/VirtualServices/Images/VS_LiveInvoke01.vsi"]},"statusCode":"success"}

-Sankar

------------------------------
Sankar Natarajan
Service Virtualization Product Engineering Team
Broadcom
------------------------------

[Philippe Bernard]

Hi Sankar,

Yes, the json parsing error appears when refreshing:

Json response is in in attachment.


Philippe.

Attachment(s)

Response.zip   27 KB 1 version

[Sankar Natarajan]

Well that pretty much nails it. There were some unparseable characters in a TCP/IP listen step which has broken the rendering in inspection view. 

This need to be delved deeper, please report a support ticket.


------------------------------
Sankar Natarajan
Service Virtualization Product Engineering Team
Broadcom
------------------------------