jakarta-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 50097] New: Failed Transaction does not show up in JTL file when Action is Stop thread
Date Fri, 15 Oct 2010 09:11:51 GMT

           Summary: Failed Transaction does not show up in JTL file when
                    Action is Stop thread
           Product: JMeter
           Version: 2.4
          Platform: PC
        OS/Version: Windows Server 2003
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTTP
        AssignedTo: notifications@jakarta.apache.org
        ReportedBy: sander@performancearchitecten.nl

When a transaction controller contains a HTTP request that fails, for example
when an embedded resource is missing, the failed transaction does not show up
in the listeners when the action to be taken is set to Stop Thread.

Steps to Reproduce:
1. In thread group set Action to be taken on Stop Thread
2. Add a transaction controller with in it a HTTP Request that will fail (e.g.
because a embedded resource is not avaiable).
3. Run the test (both GUI and non-gui)

Expected result:
The failed transaction is shown in the listeners (e.g. Summary Report, Results

Actual Result:
The failed transaction is not shown in any log (except a 404 warning message in
jmeter.log). If the HTTP Request is outside the transaction then it does show
up in the listeners.

Build & Platform:
Apache JMeter version 2.4 r961953
Tested on Windows XP SP 3 & Windows Server 2003 x64 SP2

Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail: notifications-unsubscribe@jakarta.apache.org
For additional commands, e-mail: notifications-help@jakarta.apache.org

View raw message