Release Notes - Petals ESB Container - Version 3.1.4 - HTML format

Bug

[PETALSESBCONT-166] - Error message "Cannot open connection" thrown by the registry when starting Petals
[PETALSESBCONT-178] - The RuntimeConfigurationNotifier mbean is not freed when stopping/shutdowning/uninstalling a component, if JVisualVM is connected to the container
[PETALSESBCONT-179] - No error is loggued during the undeployment of a SA using the autoloader

Improvement Request

[PETALSESBCONT-190] - The size of the message queue of the transporter should be customizable
[PETALSESBCONT-191] - When the message queue of transporter is full, the enqueuing should wait a moment before to fail.

Edit/Copy Release Notes

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

Release Notes - Petals ESB Container - Version 3.1.4
    
<h2>        Bug
</h2>
<ul>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCONT-166'>PETALSESBCONT-166</a>] -         Error message &quot;Cannot open connection&quot; thrown by the registry when starting Petals
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCONT-178'>PETALSESBCONT-178</a>] -         The RuntimeConfigurationNotifier mbean is not freed when stopping/shutdowning/uninstalling a component, if JVisualVM is connected to the container
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCONT-179'>PETALSESBCONT-179</a>] -         No error is loggued during the undeployment of a SA using the autoloader
</li>
</ul>
                
<h2>        Improvement Request
</h2>
<ul>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCONT-190'>PETALSESBCONT-190</a>] -         The size of the message queue of the transporter should be customizable
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCONT-191'>PETALSESBCONT-191</a>] -         When the message queue of transporter is full, the enqueuing should wait a moment before to fail.
</li>
</ul>