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

Bug

• [PETALSESBCONT-124] - Incorrect name for configuration properties of the persistence service
• [PETALSESBCONT-133] - Persistence service does not support Oracle database
• [PETALSESBCONT-153] - Directories are not correctly detected by the URLFactory
• [PETALSESBCONT-203] - Bad version returns by the command 'petals-esb.sh --version'
• [PETALSESBCONT-355] - Container attachments are incomplete if launched concurrently
• [PETALSESBCONT-356] - Containers are not completely detached if launched concurrently
• [PETALSESBCONT-357] - Unable to detach a container previously attached without restarting it
• [PETALSESBCONT-358] - OOM in PermGen space when attaching or detaching a container to/from a topology
• [PETALSESBCONT-359] - JBI artifact lifecycle not linked to their associated Fractal components
• [PETALSESBCONT-360] - Error not clear on container attachment when the given passphrase is invalid
• [PETALSESBCONT-361] - Sometimes a NPE occurs at container start-up recovering components
• [PETALSESBCONT-362] - A container moved from a topology to another is always known by the remaining containers of its initial topology
• [PETALSESBCONT-363] - Endpoint not found when attaching a container
• [PETALSESBCONT-364] - "No endpoint(s) matching the target service" when attaching a container
• [PETALSESBCONT-377] - DeliveryChannel's accept(long) should wait undefinitely with a timeout of 0
• [PETALSESBCONT-380] - DeliveryChannel's close() should deactivate all endpoints of the component
• [PETALSESBCONT-382] - The ZIP archives must contain the right license file
• [PETALSESBCONT-383] - The ZIP archives must contain the list of third party products with their licenses
• [PETALSESBCONT-386] - The ZIP archives must contain the right copyright file
• [PETALSESBCONT-388] - ComponentContext's method to query endpoints should return an empty array in case of errors.
• [PETALSESBCONT-389] - ComponentContext.getEndpoint(QName, String) should only return internal endpoints
• [PETALSESBCONT-392] - SA deployment fail if more than one file/directory inside META-INF
• [PETALSESBCONT-394] - Mismatch between consumer and provider with sendSync
• [PETALSESBCONT-404] - The Container shouldn't try to revert deployment in case of failure
• [PETALSESBCONT-406] - On recovery, the container should also restore SHUTDOWN state for SAs/SUs
• [PETALSESBCONT-410] - petals.container.name is missing in the server properties retrievable by JMX
• [PETALSESBCONT-411] - The debian package should not silently replace configuration files
• [PETALSESBCONT-413] - The RMI JMX Stub should register itself based on the declared host

Improvement Request

• [PETALSESBCONT-54] - The file-based repository should not contain absolute paths
• [PETALSESBCONT-90] - System state and repository components are mixed
• [PETALSESBCONT-129] - The connection pool of the persistence service must be customizable
• [PETALSESBCONT-165] - Update starting up script for the debug mode with Java 6 API for debugging
• [PETALSESBCONT-199] - Message Persistance Service should be asynchronous
• [PETALSESBCONT-200] - Rename org.ow2.petals.system.persistence.PersistenceServiceImpl to org.ow2.petals.system.persistence.JDBCPersistenceServiceImpl
• [PETALSESBCONT-208] - Add technical monitoring metrics
• [PETALSESBCONT-350] - Make InstallationExtension mechanism explicit
• [PETALSESBCONT-353] - Uniformise directories for extensions and mutable implementations
• [PETALSESBCONT-365] - The timeout used to stop the traffic at router level must be customizable
• [PETALSESBCONT-366] - The container configuration must be logged at level CONFIG instead of FINE
• [PETALSESBCONT-367] - The NIO Transporter does not send back exception if an error happens while delivering the message on the receiving side
• [PETALSESBCONT-368] - A sendSync should be blocked at router level instead of transporter level
• [PETALSESBCONT-369] - Reduce the acceptor core size of NIO transporter when no request incomes
• [PETALSESBCONT-371] - The listening IP of the NIO transporter and the WS-API are not configurable and default to the configured container host
• [PETALSESBCONT-376] - Make all implementations of MessageExchange serializable
• [PETALSESBCONT-379] - After/During component shutdown, reinject the exchanges left in the DeliveryChannel into the NMR
• [PETALSESBCONT-381] - When receiving an answer to a timed out exchange, send an error back to the sender if possible
• [PETALSESBCONT-384] - Better coherence between endpoint, service and interfaceName in MEX after endpoint selection
• [PETALSESBCONT-385] - MessageExchangeFactory should fail if its DeliveryChannel is closed
• [PETALSESBCONT-390] - ComponentContext.resolveEndpointReference(DocumentFragment) should resolve NMR generated endpoints
• [PETALSESBCONT-395] - Add statistics about connection established at NIO transporter level
• [PETALSESBCONT-397] - Add metrics about messages delivered by the NIO transporter
• [PETALSESBCONT-398] - When resolving endpoint, consider endpoint without interfaces at all as suitable for any interface
• [PETALSESBCONT-399] - MessageExchangeFactory.createExchange(QName, QName) should fails to create exchange in case of incoherence
• [PETALSESBCONT-403] - Rework the monitoring metric about delivered messages by the local transporter
• [PETALSESBCONT-407] - Return ownership on send failure
• [PETALSESBCONT-408] - Service Assembly lifecycle should mirror as much as possible SU lifecycle
• [PETALSESBCONT-412] - Isolate classloaders by default (set petals.classloaders.isolated to true)
• [PETALSESBCONT-417] - During container shutdown, keep endpoints in registry and container in topology

Task

• [PETALSESBCONT-213] - The method PetalsServer.browseJNDI() seems to be no more needed
• [PETALSESBCONT-252] - The HTTP server Jetty embedded into the Petals ESB container should be an extension
• [PETALSESBCONT-309] - The ClassLoaderObjectInputStream instances should be created when creating PipedDeserializerImpl
• [PETALSESBCONT-348] - Upgrade CXF to latest version (3.1.2) and only use needed artifacts
• [PETALSESBCONT-351] - Deprecate the old domain/subdomain style of topology
• [PETALSESBCONT-373] - Uniformise the JMX RMI naming
• [PETALSESBCONT-375] - Petals ESB container should be runnable easily after their compilation
• [PETALSESBCONT-396] - Remove processor object pool metrics
• [PETALSESBCONT-400] - Remove Router Monitor facilities as well as corresponding JMX API
• [PETALSESBCONT-401] - Remove undocumented non-working Router's rate control, filter control and prority queues modules
• [PETALSESBCONT-402] - Remove the Persistence subsystem
• [PETALSESBCONT-405] - Remove the UNKNOWN state for SAs and SUs
• [PETALSESBCONT-409] - Upgrade to Apache Commons CLI 1.3.1
• [PETALSESBCONT-415] - Remove Petals WS-API Extension from distribution
• [PETALSESBCONT-445] - Explain how to disable log file hierarchy
• [PETALSESBCONT-446] - Remove MX4J dependency

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