Release Notes - Petals CDK - Version 5.1.4 - HTML format

Bug

[PETALSCDK-48] - Problem when a notification producer crash : subscriptions are not persisted on producer and broker don't replay subcriptiond until restart
[PETALSCDK-53] - Notifications are sent before interceptors are processed
[PETALSCDK-54] - "Life cycle exception on START" caused by "PEtALSCDKException: The publisher reference MUST appear because the demand component has value "true""
[PETALSCDK-76] - Memory-leak because runtime configuration listeners are not unregistered
[PETALSCDK-77] - Memory-leak because utility singletons are not freed
[PETALSCDK-79] - ExceptionUtil.getExtendedMessage() prints incomplete stacktrace
[PETALSCDK-80] - Memory leak because resources of JBIBuilderDescriptor resources are not freed
[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-85] - Memory leak because the ThreadGroup of JBIAcceptor is not freed
[PETALSCDK-88] - StackOverflowError occurs when the JBI message processor thread pool is exhausted

Improvement Request

[PETALSCDK-91] - If no more message exchange processor thread is available, new incoming message exchange should be enqueued instead of to be rejected

Edit/Copy Release Notes

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

Release Notes - Petals CDK - Version 5.1.4
    
<h2>        Bug
</h2>
<ul>
<li>[<a href='https://jira.petalslink.com/browse/PETALSCDK-48'>PETALSCDK-48</a>] -         Problem when a notification producer crash : subscriptions are not persisted on producer and broker don&#39;t replay subcriptiond until restart
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSCDK-53'>PETALSCDK-53</a>] -         Notifications are sent before interceptors are processed
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSCDK-54'>PETALSCDK-54</a>] -         &quot;Life cycle exception on START&quot; caused by &quot;PEtALSCDKException: The publisher reference MUST appear because the demand component has value &quot;true&quot;&quot;
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSCDK-76'>PETALSCDK-76</a>] -         Memory-leak because runtime configuration listeners are not unregistered
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSCDK-77'>PETALSCDK-77</a>] -         Memory-leak because utility singletons are not freed
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSCDK-79'>PETALSCDK-79</a>] -         ExceptionUtil.getExtendedMessage() prints incomplete stacktrace
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSCDK-80'>PETALSCDK-80</a>] -         Memory leak because resources of JBIBuilderDescriptor resources are not freed
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSCDK-82'>PETALSCDK-82</a>] -         Memory leak because of not static inner classes into the JBIProcessorManager
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSCDK-83'>PETALSCDK-83</a>] -         Memory leak because the JBIAcceptorManager.acceptorPool is not freed
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSCDK-85'>PETALSCDK-85</a>] -         Memory leak because the ThreadGroup of JBIAcceptor is not freed
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSCDK-88'>PETALSCDK-88</a>] -         StackOverflowError occurs when the JBI message processor thread pool is exhausted
</li>
</ul>
                
<h2>        Improvement Request
</h2>
<ul>
<li>[<a href='https://jira.petalslink.com/browse/PETALSCDK-91'>PETALSCDK-91</a>] -         If no more message exchange processor thread is available, new incoming message exchange should be enqueued instead of to be rejected
</li>
</ul>