Mailing-List: contact jmeter-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "JMeter Users List" <jmeter-user@jakarta.apache.org>
Received-SPF: pass (herse.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7C7CC.D63D1EFA"
Subject: Empty assertion results failure message
Date: Mon, 16 Jul 2007 12:15:00 -0500
Message-ID: 
 <1A1531E6D16EBB46BF479B6169D3D6DFBA7CF8@INFMAIL.core.coremetrics.com>
Thread-Topic: Empty assertion results failure message
Thread-Index: AcfHzNWckQCMWFpQRLSVoqw/FzREng==
From: "Kathy Mitchell" <KMitchell@coremetrics.com>
To: <jmeter-user@jakarta.apache.org>

------_=_NextPart_001_01C7C7CC.D63D1EFA
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I have a very simple jmeter acceptance test script that writes errors to
an Aggregate Report listener.  When I have 'Save As XML' turned OFF I
sometimes don't get anything in the Assertion Results Failure Message.
If I turn on 'Save As XML' I see all the failure messages.  See sample
output below with XML off.  The first line shows the failure message but
the rest don't.
=20
Is this a know jmeter bug?  Is there anyway to work around it other than
saving as XML?
=20
=20
timeStamp,elapsed,label,responseCode,responseMessage,threadName,success,
failureMessage,bytes
1184605247229,121,Login Failed Test (client 2),302,Moved
Temporarily,Main thread 1-3,false,Test failed, code expected to match
/200/,0
1184605276707,281,Report (client 9),200,OK,Main thread 1-2,false,,1437
1184605334228,632,Key 3 (client 9),200,OK,Main thread 1-2,false,,1437
1184605334860,562,Key 4 (client 9),200,OK,Main thread 1-2,false,,1437
1184605335422,583,Key 5 (client 9),200,OK,Main thread 1-2,false,,1437
1184605336005,763,Key 6 (client 9),200,OK,Main thread 1-2,false,,1437

Thanks,
=20
Kathy

=20

------_=_NextPart_001_01C7C7CC.D63D1EFA--