Certificates are not getting set/sent correctly

[subbu05]

Below is the code I used and always ac.pem is getting used for second request.
After first request I have configured to use tc.pem but still uses ac.pem.

When I run first request goes fine, for the second request I see 403 forbidden due to cert issue.

OS Centos7 64 bit
Tsung version Tsung version 1.6.0
erl -v
Erlang R16B03-1 (erts-5.10.4) [source] [64-bit] [async-threads:10] [hipe] [kernel-poll:false]
Eshell V5.10.4

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE tsung SYSTEM "/usr/share/tsung/tsung-1.0.dtd" []>
<tsung loglevel="debug" dumptraffic="true">

  <clients>
    <client host="localhost" cpu="1"   use_controller_vm="true"/>
  </clients>

<servers>
 <server host="hero.com" port="443" type="ssl"/>
  </servers>

  <load>
    <arrivalphase phase="1" duration="120" unit="second">
      <users arrivalrate="0.1" unit="second"/>
    </arrivalphase>
  </load>



  <sessions>

 <session name="es_load" weight="1" type="ts_http">

     <set_option name="certificate">
    <certificate keyfile="certs/ac.key" certfile="certs/ac.pem"/>
  </set_option>

<transaction name="portals">
      <request >
      <dyn_variable name="id" jsonpath="Resources[0].id"/>
      <http url="/v2/Portals" method="GET" content_type="application/json"       >
      <http_header  name="HOST" value="hero.com"/>
      <http_header name="Accept" value="application/json"/>
      </http>
      </request>
</transaction>


 <set_option name="certificate">
    <certificate keyfile="certs/tc.key" certfile="certs/tc.pem"/>
  </set_option>

<transaction name="s2">
<request subst="true">
<http url="/v2/jwt/access" method="POST" content_type="application/json" contents="{&quot;Names&quot;:{&quot;Id&quot;:&quot;%%_id%%&quot;}, &quot;expiry&quot;:6000}">
      <http_header  name="HOST" value="hero.com"/>
      </http>
      </request>
</transaction>



    </session>



  </sessions>
</tsung>

[nniclausse]

yes, the connection is not reopen when the second certificate is set, so the first one is still used, it's a bug.