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

Bug

• [PETALSESBCONT-127] - Error message when using the autoloader to install a component
• [PETALSESBCONT-161] - Unable to re-install a component: "Component already registered"
• [PETALSESBCONT-166] - Error message "Cannot open connection" thrown by the registry when starting Petals
• [PETALSESBCONT-176] - Unable to start Petals ESB under Cygwin
• [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
• [PETALSESBCONT-180] - No script to stop a Petals ESB container
• [PETALSESBCONT-181] - The boostrap configuration Mbean is not unregistered if component installation is cancelled
• [PETALSESBCONT-182] - NPE if directories used by the autoloader are deleted when it runs
• [PETALSESBCONT-183] - Error when installing a component that was just uninstalled
• [PETALSESBCONT-193] - Property 'petals.transport.tcp.send.evictable.delay' is not taken into account
• [PETALSESBCONT-194] - The property 'petals.transport.tcp.send.evictor.delay' is not taken into account

Improvement Request

• [PETALSESBCONT-107] - Instanciation number of DOM document builder can be optimized
• [PETALSESBCONT-132] - Use String Reader instead of StringBufferInputStream in XmlUtil
• [PETALSESBCONT-158] - Add a MBean operation to synchronize the registry
• [PETALSESBCONT-184] - Add a script to launch a JVisualVM instance connected to the local Petals node
• [PETALSESBCONT-185] - The delay between two directory scans of the autoloader should be customizable
• [PETALSESBCONT-186] - Reduce the number of threads needed by the autoloader
• [PETALSESBCONT-187] - The thread of the timer used by the persistence service should be correctly named.
• [PETALSESBCONT-188] - The threads of the timers used by the flow control module of the message router should be correctly named.
• [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.

Task

• [PETALSESBCONT-174] - Improve the initialization of the registry factory instance
• [PETALSESBCONT-175] - Improve the initialization of the registry context factory instance

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