TruClient IE producing erratic response times and random "network timeout" failures (635 Views)
Reply
Frequent Advisor
Andrew Nightingale
Posts: 33
Registered: ‎10-07-2008
Message 1 of 2 (635 Views)

TruClient IE producing erratic response times and random "network timeout" failures

We are trying to use TruClient IE protocol for testing of a new business application built on the IBM Lombardi BPM platform. We chose the TruClient due to the very high complexity of correlation that would be required if we were to use the traditional Web(HTTP/HTML) protocol.

While TruClient IE seems easy to learn and use, we are getting unpredictable results in our initial scripts. It is such that we do not have much faith in any test results that might be obtained using TruClient IE.

Scripts will show erratic response times just running in VuGen, and will also randomly fail during execution on reported network timeout.

Here is a sample of script execution VuGen output log using TruClientIE protocol. This shows an extremely high response time on login that we have never noticed in manual testing, and then in this example the very next transaction fails the iteration due to a reported network timeout:

Starting iteration 1.
Starting action Action.
t=00006004ms: ** 1: Navigate to "https://bpm.service...ortal/login.jsp" ** started [MsgId: MMSG-204251]
Notify: Transaction "ValuationsBPM_Nuisance_01_LoadProcessPortal" started.
t=00007780ms: ** 1: Navigate to "https://bpm.service...ortal/login.jsp" ** successfully completed [MsgId: MMSG-204250]
Notify: Transaction "ValuationsBPM_Nuisance_01_LoadProcessPortal" ended with "Pass" status (Duration: 1.5597).
t=00007795ms: ** 2: Login ** started [MsgId: MMSG-204251]
t=00008481ms: ** 2.1: Click on User ID textbox ** started [MsgId: MMSG-204251]
Notify: Transaction "ValuationsBPM_Nuisance_02_Login" started.
t=00008872ms: ** 2.1: Click on User ID textbox ** successfully completed [MsgId: MMSG-204250]
t=00009384ms: ** 2.2: Type "pst023" in User ID textbox ** started [MsgId: MMSG-204251]
t=00010888ms: ** 2.2: Type "pst023" in User ID textbox ** successfully completed [MsgId: MMSG-204250]
t=00011400ms: ** 2.3: Type ********* in Password passwordbox ** started [MsgId: MMSG-204251]
t=00013134ms: ** 2.3: Type ********* in Password passwordbox ** successfully completed [MsgId: MMSG-204250]
t=00013645ms: ** 2.4: Click on Login button ** started [MsgId: MMSG-204251]
t=00193685ms: ** 2.4: Click on Login button ** successfully completed [MsgId: MMSG-204250]
Notify: Transaction "ValuationsBPM_Nuisance_02_Login" ended with "Pass" status (Duration: 185.1937 Think Time: 1.5220).
t=00193718ms: ** 2: Login ** successfully completed [MsgId: MMSG-204250]
t=00194231ms: ** 3: Click on Order Search link ** started [MsgId: MMSG-204251]
Notify: Transaction "ValuationsBPM_Nuisance_03_ClickOrderSearch" started.
t=00234760ms: Error -203252: ** 3: Click on Order Search link ** failed - end event error due to network timeout Snapshot Info [MSH 1 1] [MsgId: MERR-203252]
Notify: Transaction "ValuationsBPM_Nuisance_03_ClickOrderSearch" ended with "Fail" status (Duration: 40.6189).
Error: Failed to end Transaction "ValuationsBPM_Nuisance_03_ClickOrderSearch" (by name). Please check that you made a call to start transaction operation.
Ending action Action.
Ending iteration 1.


I have recorded login action using Web(HTTP/HTML) protocol, and do not ever see the massive inconsistencies that are present in TruClient. Below are a couple samples of Web protocol response time. Interestingly, manual testing never shows any response time higher than 1-2 seconds for login, and yet even the Web script returns 13-16 seconds consistently:

Login.c(450): Notify: Transaction "Login" ended with "Pass" status (Duration: 14.7413 Wasted Time: 11.8269).
Login.c(450): Notify: Transaction "Login" ended with "Pass" status (Duration: 16.5117 Wasted Time: 12.7917).
Login.c(450): Notify: Transaction "Login" ended with "Pass" status (Duration: 13.4435 Wasted Time: 11.0772).

Esteemed Contributor
James Leatherman
Posts: 538
Registered: ‎06-05-2008
Message 2 of 2 (583 Views)

Re: TruClient IE producing erratic response times and random "network timeout" failures

Understand that TruClient can be configured to measure transaction times with several permutations of start/end events. It is conceivable that your end event is taking into account non-HTML resources that are taking much longer to load than the page body itself. Try differnet end events to see if there is a difference in transaction times.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.