[Grinder-use] handshake_failure in Grinder 3.0-beta25 at very end of SSL handshake process

[Ryan W. <RWh...@sa...>]

All,
=20
I am able to use TCPProxy to record a two-way ssl session, but when I =
try to run the recorded session I am running into problems with a =
handshake failure after *** Finished step in handshake.   I am not an =
SSL guru, but have had this entire setup working under version 2.8.6 and =
for some reason the same general tactic is not working as we try to move =
to Grinder-3.0-beta25.  I am doing this with Weblogic 8.1.  Is this =
telling me their isn't a cipher match between the client and server???  =
The text immediately preceding the error is:
=20
=20
<Everything before this seems to be looking normal in the ssl debug =
log--the only thing that looks interesting, but I don't know if it is =
relevant is that after the "Client write key:" and "Server write key:" =
the text "... no IV for cipher" shows up>
=20
*** Finished
verify_data: <data here>
***
[write] MD5 and SHA1 hashes:   len =3D 16
0000: <data here>
Plaintext before ENCRYPTION:    len =3D 32
0000: <data here>
0010: <data here>
Grinder thread 0, WRITE: TLSv1 Handshake, length =3D 32
Grinder thread 0, READ: TLSv1 Alert, length =3D 2
Grinder thread -, RECV TLSv1 ALERT: fatal, handshake_failure
=20
=20
The error on the weblogic side is:
<BEA-090508> <Certificate chain received from 127.0.0.1 - 127.0.0.1 was =
incomplete.>
=20
This is really halting my progress and I REALLY want to upgrade to the =
3.x version--but this is a gaiting factor at this point.
=20
TIA,
Ryan Whitaker