Skip to content

Releases: th2-net/th2-conn-sailfish

Release 3.11.2

13 Oct 06:53
5c60ad3
Compare
Choose a tag to compare
Release 3.11.2 Pre-release
Pre-release

3.11.2

  • Sailfish updated from 3.3.132 to 3.3.144
  • Added maxMessageFlushTime option
  • Use temporal directory for last layer in sailfish's workspace

3.11.1

  • Updated sailfish-core version from 3.3.54 to 3.3.132

3.11.0

  • Updated sailfish-core version from 3.2.1741 to 3.3.54
  • Updated common from 3.33.0 to 3.44.0
  • Updated kotlin form 1.5.30 to 1.6.21
  • Renamed project to conn-sailfish

3.10.2

  • Events are made more convenient. Added event names and error logs. Error message moved from the name to the body of the event.

Release 3.10.1

04 Mar 16:07
bf518b0
Compare
Choose a tag to compare

This release contains important fixes and improvements of th2-conn integration with Sailfish services

Changed:

Library version was updated

  • th2-common version is updated to 3.33.0. You can find changes here

  • kotlin version is updated to 1.5.30

  • sailfish-core version is updated to 3.2.1741

    • Sailfish service based on MINA decodes the message as sender during sending.
      This approach is important for protocols in which a pair of messages have the same protocol message type and different structures depending on the direction

Added:

  • Message sending failure reporting (creates events when an exception was thrown during sending message)

  • th2_conn_incoming_msg_quantity and th2_conn_outgoing_msg_quantity metrics are produced by conn

  • Option for disabling generation of an event for sent message if it has parent_event_id

  • Option for configuring maxMessageBatchSize for th2 message sending to mstore (other components)

  • Check for missing sequences in a batch (the error will be written in the log)

Fixed:

  • Fix problem with trying to send EvolutionBatch message. Unwraps the EvolutionBatch when sending raw message

  • Problem with dropped messages when the significant load was directed to conn box. The synchronization on message publication was added.

  • Problem when conn was frozen during shutdown when the connection to rabbit MQ was not connected.
    We don’t wait for connection recovery in this case anymore