56

Small update that improves platform error handling.

Major Changes

• Multiple improvements to the 'Error to XML transformer' to prevent error messages from growing too large in certain circumstances, which could negatively impact performance and stability:
  • Removed the 'omit stack trace' functionality: this option wasn't used in eMagiz (defaulted to 'true') and would significantly increase the size of errors by including full stack frame info (Java class names, method names, line numbers, etc).
  • Message history is now truncated to 100 entries max (keeping the first and last 50). Normally message history would never reach this limit, but when building (potentially infinite) loops in eMagiz flows it was possible to create humongous 'history' headers.
  • Message headers are now truncated to 40 entries max (keeping the first 40 headers alphabetically).
  • XML validation errors are now truncated to 40 entries max (keeping the first 40 validation errors reported by the underlying validation engine).
  • "Caused by" exception chains are now truncated to a maximum depth of 5 levels. In normal circumstances exceptions would not be expected to reach this limit, but flows with incorrectly configured custom (recursive) error handling could cause extremely long exception chains.

Minor Changes

• Updated bundle 'com.emagiz.components.error' from 7.0.0 to 7.1.0