Unexpected Use of the Suppression Insertion of Timestamp into WS-Security Header Feature in the SOAP Adapter Causes an Unrelated Error Response

When creating a SOAP Adapter connection with Suppress insertion of timestamp into WS-Security header set to Yes on the Connections page and using a WSDL that requires a timestamp header, the connection fails during runtime with the following error instead of a message indicating that a valid timestamp is not present:

<errorCode>OSB-380001</errorCode>             
<reason>InvalidSecurityToken : The security token is not valid.</reason>