AMB Connect Requests Client ID - Loadrunner

[forsh75]

Hi,

I'm currently scripting the Create Incident process using LoadRunner for performance testing purposes. Throughout the script I see the following requests:

web_custom_request("connect_4",

  "URL=https://linklatersesmdev.service-now.com/amb/connect",

  "Method=POST",

  "TargetFrame=",

  "Resource=0",

  "RecContentType=application/json",

  "Referer=https://linklatersesmdev.service-now.com/incident.do?sys_id=-1&sysparm_query=active=true&sysparm_sta...",

  "Snapshot=t174.inf",

  "Mode=HTML",

  "EncType=application/json;charset=UTF-8",

  "Body=[{\"channel\":\"/meta/connect\",\"connectionType\":\"long-polling\",\"id\":\"4\",\"clientId\":\"3co1d7epq59s8she19sprd00ikafs\"}]",

  LAST);

Midway through the script the client id changes value after a second handshake, however even though I capture this new value and plug it in to future connect requests I'm getting the following response from the server:

HTTP/1.1 200 OK
Content-Type: application/json;charset=UTF-8
Content-Length: 135
Date: Thu, 21 Dec 2017 15:42:17 GMT
Server: ServiceNow
Strict-Transport-Security: max-age=63072000; includeSubDomains

[{"advice":{"interval":0,"reconnect":"handshake"},"channel":"/meta/connect","id":"7","error":"402::Unknown client","successful":false}]

It's obviously complaining that the client id is incorrect but I'm definitely capturing the value that's returned from the handshake and passing it back in.

I'd be very grateful for any suggestions as to why it's moaning about the Client Id.

Thanks.

[yevgeniypro]

Hi Forsh, 

any luck on that problem?

I am quite interested now how the AMB works and how to write to it.

Found your thread while poking around for info.

Cheers,

Yev