[erlang-questions] Patch Package OTP 17.5.6.7 Released

[Zandra Hird]

Patch Package:           OTP 17.5.6.7
Git Tag:                 OTP-17.5.6.7
Date:                    2015-12-21
Trouble Report Id:       OTP-12947, OTP-12969, OTP-13137
Seq num:
System:                  OTP
Release:                 17
Application:             diameter-1.9.2.2
Predecessor:             OTP 17.5.6.6

  Check out the git tag OTP-17.5.6.7, and build a full OTP system
  including documentation. Apply one or more applications from this
  build as patches to your installation using the 'otp_patch_apply'
  tool. For information on install requirements, see descriptions for
  each application version below.

  ---------------------------------------------------------------------
  --- diameter-1.9.2.2 ------------------------------------------------
  ---------------------------------------------------------------------

  The diameter-1.9.2.2 application can be applied independently of
  other applications on a full OTP 17 installation.

  --- Fixed Bugs and Malfunctions ---

   OTP-12969    Application(s): diameter

                Fix diameter_watchdog function clause.

                OTP-12912 introduced an error with accepting transports
                setting {restrict_connections, false}, causing
                processes to fail when peer connections were
                terminated.


   OTP-13137    Application(s): diameter

                Fix request table leaks

                The End-to-End and Hop-by-Hop identifiers of outgoing
                Diameter requests are stored in a table in order for
                the caller to be located when the corresponding answer
                message is received. Entries were orphaned if the
                handler was terminated by an exit signal as a
                consequence of actions taken by callback functions, or
                if callbacks modified identifiers in retransmission
                cases.


  --- Improvements and New Features ---

   OTP-12947    Application(s): diameter

                Add service_opt() strict_mbit.

                There are differing opinions on whether or not
                reception of an arbitrary AVP setting the M-bit is an
                error. The default interpretation is strict: if a
                command grammar doesn't explicitly allow an AVP setting
                the M-bit then reception of such an AVP is regarded as
                an error. Setting {strict_mbit, false} disables this
                check.


  Full runtime dependencies of diameter-1.9.2.2: erts-6.0, kernel-3.0,
  ssl-5.3.4, stdlib-2.0


  ---------------------------------------------------------------------
  ---------------------------------------------------------------------
  ---------------------------------------------------------------------