Known issues with the Gateway for Message Bus

This section explains some known issues with the Gateway for Message Bus.

  • The gateway repeats a reconnection attempt even when the retry countdown reaches zero until the transport connection is established.
  • In Windows the gateway cannot shut down gracefully after Ctrl-C.

MultiChannelHTTP transport writes an error message when flushing the event buffer

The MultiChannelHTTP transport periodically flushes the event buffer as per the bufferFlushTime interval. Before flushing the buffer and sending out the events, the transport verifies that the HTTP connection to the endpoint is active. The following error message indicates that the HTTP connection is inactive and the events cannot be sent out: 

XMLGateway: Failed Send request while flushing buffer: HTTP channel is inactive.

The transport will wait for the next interval to retry flushing the event buffer.

Gateway fails to start on Windows when specifying the JMS transport

On Windows platforms, when using the gateway with latest transport module, the gateway cannot start when specifying the JMS transport.

If you want to use the JMS transport, you must use the previous version of the transport module.

Gateway not able to run on Transport Module version 40.0.6 on Windows platforms

There is currently a known issue whereby the gateway cannot run on the latest versions of the Transport Module (version 40.0.6) on Windows platforms.

If you have the gateway installed on Windows, do not upgrade to Transport Module v40.