IBM MQ receivers cannot use extraMappingThreads with default maxBatchSize in BEST_EFFORT mode.

When using correlator-integrated JMS to receive from IBM MQ, extra mapping threads could not be used with BEST_EFFORT receivers using the default receiver maxBatchSize value. This issue has been resolved.

Recreating an HTTP client generic JSON chain instance fails due to status key already existing.

Previously, trying to recreate a destroyed HttpClientGenericJson chain with the same parameters used to throw an exception because of a duplicated status item (“Connectivity plug-ins: Exception creating user status item”). This has been fixed.

The underlying issue of not being able to reuse chainInstanceId when creating a dynamic chain using ConnectivityPlugins.createDynamicChain() if the previous chain instance has been destroyed has also been fixed.

Behavior of HTTP server with incomplete requests.

The behavior of the included HTTP server has been modified to discard requests where the message content is less than the defined Content-Length, to bring it more in line with the HTTP/1.1 specification. This does not currently include Content-Encoded requests, such as gzipped requests.

The behavior of the included HTTP server has been modified to discard the Content-Length header when the Transfer-Encoding header is also set, to bring it more in line with the HTTP/1.1 specification.