[CRITICAL] uninitialized response field can sometimes cause crashes

[CRITICAL] uninitialized response field can sometimes cause crashes

The response message in the transaction structure was not properly
initialised at session initialisation. In theory it cannot cause any
trouble since the affected field os expected to always remain NULL.
However, in some circumstances, such as building on 64-bit platforms
with certain options, the struct session can be exactly 1024 bytes,
the same size of the requri field, so the pools are merged and the
uninitialised field may contain non-null data, causing crashes if
an invalid response is encountered and archived.

The fix simply consists in correctly initialising the missing fields.
This bug cannot affect architectures where the session pool is not
shared (32-bit architectures), but this is only by pure luck.
(cherry-picked from commit 79e998919660b2ec6d5dc11be9d820c5c1965460)
(cherry picked from commit c0e4eb7d1dc3636757232ce730cbc9a8f6ac34d8)