Release Notes - Petals CDK - Version 5.3.0 - HTML format

Bug

• [PETALSCDK-66] - The private method 'AbstractListener.setEndpoint' does not manage correctly unknown endpoint
• [PETALSCDK-72] - Unable to compute dynamically the provider service name
• [PETALSCDK-73] - NPE when hot-setting the value of the parameter 'processor-pool-size'
• [PETALSCDK-75] - NPE when setting the value of the parameter 'processor-pool-size' through the installation configuration MBean
• [PETALSCDK-76] - Memory-leak because runtime configuration listeners are not unregistered
• [PETALSCDK-79] - ExceptionUtil.getExtendedMessage() prints incomplete stacktrace
• [PETALSCDK-80] - Memory leak because resources of JBIBuilderDescriptor resources are not freed
• [PETALSCDK-81] - Unable to hot-update the configuration of the processor pool of a component
• [PETALSCDK-82] - Memory leak because of not static inner classes into the JBIProcessorManager
• [PETALSCDK-83] - Memory leak because the JBIAcceptorManager.acceptorPool is not freed
• [PETALSCDK-84] - Negative and null values are accepted by the parameter 'processor-stop-max-wait'
• [PETALSCDK-85] - Memory leak because the ThreadGroup of JBIAcceptor is not freed
• [PETALSCDK-86] - Validator used in the JBIDescriptorBuilder is not thread-safe
• [PETALSCDK-88] - StackOverflowError occurs when the JBI message processor thread pool is exhausted
• [PETALSCDK-89] - If all JBI message exchange processors are running, additional requests are rejected
• [PETALSCDK-92] - The size of the pool of message exchange processor does not decrease after a burst of requests
• [PETALSCDK-93] - The message exchange processor pools are not correctly reconfigured on hot-configuration
• [PETALSCDK-96] - Memory leak because of a not static inner classe into the AsyncMessageManager

Improvement Request

• [PETALSCDK-63] - Improve configuration of the JBI message worker pool
• [PETALSCDK-74] - IllegalArgumentException when starting a component
• [PETALSCDK-91] - If no more message exchange processor thread is available, new incoming message exchange should be enqueued instead of to be rejected
• [PETALSCDK-97] - The thread of the async message cleaner should be correctly named.
• [PETALSCDK-98] - Only the async message cleaner task should be stopped
• [PETALSCDK-99] - The period of the async message cleaner should be customizable

Task

• [PETALSCDK-100] - Utility of 2 maps of AsyncMessageManager must be reviewed.

The text area below allows the project release notes to be edited and copied to another document.