Technical Guide Reference Guide Frequently Asked Questions Tutorials
Show menu

5.0.0

Release Notes 5.0.0

Customer Release Notes

NOTES

  • In the connectplaza-jvm-process.properties remove the entry 
    connectplaza.process.jvm.arg.nashornwarning = -Dnashorn.args=--no-deprecation-warning
    By adding a # before the line or remove the line in total. This parameter is depricated and can issue a crash of the agent using Java 17, which is the default Java for Release 5.0.0.
  • This version of the ConnectPlaza Agent downloads a JDK from Eclipse. If you have problems downloading the JDK from the internet, follow the next procedure:

    Download the following JRE ONLY THIS ONE!!!! (Or equivalent for Linux)
    https://github.com/adoptium/temurin17-binaries/releases/download/jdk-17.0.9%2B9.1/OpenJDK17U-jre_x64_windows_hotspot_17.0.9_9.zip
    Put this in the installation directory where your agent is installed (your probably see a symlink to agent in this directory!)

Fixes

  • Fixed ClassNotFoundException when invoking a class loaded by the interface classloader via the Header Enricher V2 script operation.
  • Fixed custom connect.message-part.payload-size-in-bytes-threshold-warning property value being ignored.
  • The default poll size of polling consumers has been changed from unlimited to 1. This change only applies to new configurations. Existing configurations will not be affected.
  • The agent properties and their default values have been split into separate files. Note that this should not impact the configuration of properties via Deploy.
  • Fixed ErrorIrresolvableConflictError in the Microsoft Mail Listener.
  • A large number of agent dependencies have been updated to more recent versions, which include various security fixes.
  • The cleanup process for Analyze messages and business entities has been revised to use smaller transactions, and make use of cascading delete to remove all related records.
  • Linux update could be very slow due to the setting of file rights. Fixed by setting only file rights of new files.
  • Duplicate ids in a flow are no longer allowed, and an informative exception is thrown at deploy-time when a duplicate id is found.
  • Fixed a bug where error-handling routing was not removed when un-deploying an interface.
  • Fixed a bug in the MyESBJmsOutboundGatewayParser where the topic name was not properly set.
  • Fixed logging of requests in HTTP Gateway missing the Cookie header.

New features

  • The XPath Splitter now has a namespace-aware option. Disabling the namespace-aware option is useful when the XML elements have a namespace, but the XPath expression does not include the namespace.
  • The ConnectPlaza Agent 5.0 uses JRE 17 as runtime. Adoptium OpenJDK 17 is automatically downloaded and installed during new installations and during the update from 4.4.x to 5.0
  • ConnectPlaza Control metrics now come from MicroMeter defined metrics in all components, flows and interfaces. Extra metrics are added for ConnectPlaza analyze.
  • Due to the switch to MicroMeter metrics, the ConnectPlaza Control metrics endpoint for Prometheus has renamed metric names and extra metrics. This document describes the changes. [link]
  • The Header Enricher V2 now supports fixed value templates. This allows you to quickly combine header values and part values into a single header value. For example,
  • Added property connect.activemq.broker.persistenceAdapter.ignoreMissingJournalFiles to connect-agent.properties to ignore missing ActiveMQ journal files.
  • Added extra attribute to DbGateway to set result-escaping to NO_ADDED_ESCAPING
  • Added attribute http-method-specification-type in HttpGateway component to choose the setting of the http method. 
    Content-Type: :header[<name-of-header>]
    Please see the Header Enricher V2 documentation for more information.
  • The REST Listener now supports mapping JWT claims to a separate message part. You can use JSONPath expressions to extract separate claims.
  • The OAuth2 Gateway now propagates error messages and error codes to the REST Listener. This means that if you receive an error response from the OAuth2 Gateway, the REST Listener will return the same error response.
  • New agents by default support TLSv1.3 in the REST, HTTP, Webservice, and AS2 Listener.
    To add TLSv1.3 support to existing agents, you must update the Accepted TLS Protocols agent property to include TLSv1.3 in the comma-separated list, and restart the agent.
  • The HTTP and OAuth2 Gateway now support TLSv1.3. No further action is necessary.
  • The MapForce service now supports file message parts as input, allowing the service to process larger inputs.
  • The Webservice Gateway can now log requests and responses by enabling the corresponding attributes in Constructor.