Petals ESB 3.1.3 maintenance version was just released. It includes both 3.1.2 and 3.1.3  container fixes, and a SE-POJO maintenance version.

Download: Petals ESB 3.1.3 - Petals-SE-POJO 2.2.5

Release note :

Bug

• [PETALSESBCONT-18] - The container is always on State: UNKNOWN
• [PETALSESBCONT-28] - The MIME "application / zip" check is too restrictive when deploying a JBI artefact
• [PETALSESBCONT-70] - A META tag is added when a HTML message is set as output message content
• [PETALSESBCONT-83] - Lack of robustness if we play with JMX
• [PETALSESBCONT-92] - Error creating new org.ow2.petals.registry.core.repository.bo.Endpoint
• [PETALSESBCONT-93] - Two versions of petals-registry-api are packaged
• [PETALSESBCONT-98] - The JMX API InstallationServiceMBean.loadInstaller is not JBI compliant when the installer does not exist
• [PETALSESBCONT-100] - Successful creation of... 2 EPs with same name !
• [PETALSESBCONT-105] - WSDL are transmitted at each request
• [PETALSESBCONT-117] - Use of an unsynchronized DateFormat
• [PETALSESBCONT-127] - Error message when using the autoloader to install a component
• [PETALSESBCONT-131] - Error restart Petals ESB after to have installed a faulty component
• [PETALSESBCONT-136] - Unable to install a component from a readonly file-based JBI archive
• [PETALSESBCONT-141] - Some HQL requests of the registry don't use named parameter
• [PETALSESBCONT-142] - Unable to uninstall a component using Ant task after a failed installation
• [PETALSESBCONT-143] - The error message of Ant task 'jbi-uninstall-component' is not clear when the component is not installed
• [PETALSESBCONT-144] - The Ant task does not manage correctly configuration attributes when set by configuration file and nested element
• [PETALSESBCONT-145] - No error occurs stopping a component in state 'shutdown'
• [PETALSESBCONT-146] - A suite of life cycle changes results in end-point leak
• [PETALSESBCONT-147] - The error message of the Ant task 'jbi-install-...' or 'jbi-deploy-...' is not clear when the attribute 'file' is empty
• [PETALSESBCONT-149] - The error message of the Ant task 'petals-configure-...' is not clear when the attribute 'file' or 'outputFile' is empty
• [PETALSESBCONT-151] - The Ant task 'petals-configure-...' does not delete its temporary files
• [PETALSESBCONT-161] - Unable to re-install a component: "Component already registered"
• [PETALSESBCONT-164] - A NumberFormatException occurs when component configuration parameters are set with invalid values
• [PETALSSEPOJO-10] - Unable to configure the component attribute 'properties-file'
• [PETALSSEPOJO-11] - Unable to configure the component attribute 'processor-max-pool-size'

Improvement Request

• [PETALSESBCONT-45] - A trace MUST be logged about recovering of shared libraries
• [PETALSESBCONT-96] - In the server.properties, correct and improve comment about the parameter 'petals.repository.path'
• [PETALSESBCONT-103] - Error about opening zip file when loading a new installer from an HTTP URL associated to an HTML page
• [PETALSESBCONT-107] - Instanciation number of DOM document builder can be optimized
• [PETALSESBCONT-108] - Instanciation number of transformer factory can be optimized
• [PETALSESBCONT-109] - Fix and improve inheritance between JBIServiceEndpointImpl and ServiceEndpointImpl
• [PETALSESBCONT-112] - Exchange forker can be improved using an entry set instead of a key set
• [PETALSESBCONT-116] - Prefer to use ConcurrentHasMap instead of Collections.synchronizedMap(...)
• [PETALSESBCONT-118] - Incorrect error message when loading a new installer from a HTTP URL pointing on something that is not a ZIP file
• [PETALSESBCONT-119] - Incorrect error message when loading a new installer from an inexisting HTTP URL
• [PETALSESBCONT-120] - Don't use utility method of the registry implementation
• [PETALSESBCONT-125] - Use preparedStatement instead of simple statement to improve performance and security
• [PETALSESBCONT-128] - The recovering thread pool should be sizable
• [PETALSESBCONT-130] - Add default option -Djava.net.preferIPv4Stack=true when starting petals
• [PETALSESBCONT-132] - Use String Reader instead of StringBufferInputStream in XmlUtil
• [PETALSESBCONT-134] - The persistence service should use batch of SQL commands to insert array of the same data
• [PETALSESBCONT-135] - The persistence service should use fetch-array with ResultSet to retrieve data of a request returning several lines
• [PETALSESBCONT-138] - The logged trace about installer loading should be different in both installer loading methods
• [PETALSESBCONT-148] - The error message of Ant tasks managing component lifecycle is not clear when the component identifier is empty
• [PETALSESBCONT-150] - No error is thrown when using the Ant task 'petals-configure-...' with an output archive that already exists
• [PETALSESBCONT-155] - The error message of Ant tasks uninstalling a shared library is not clear when the shared library identifier is empty
• [PETALSESBCONT-158] - Add a MBean operation to synchronize the registry

 

These maintenance versions correct a few bugs, including a fix for notifications in SE-BPEL.

Downloads :

petals-se-bpel-1.0.6.zip

30-Nov-2010 09:00

11M

petals-webconsole-ui-2.0.5.war

Mon Nov 22 10:37:16 CET 2010

5715360

Compatible with Petals ESB 3.1.1+

Bug fixes:

• [PETALSSEBPEL-14] - Notifications are not sent on responses (fault or out message)
• [PETALSWEBC-31] - NumberFormatError when we refresh an empty domain
• [PETALSWEBC-33] - NPE during management server page displaying
• [PETALSWEBC-35] - NPE from webconsole service layer
• [PETALSWEBC-37] - Unable to correctly recover wsdl for endpoint

Improvements:

• [PETALSWEBC-7] - The package javax.activation is embedded twice
• [PETALSWEBC-36] - Avoid to load all endpoints for each node

Petals ESB 3.1.1 was released ! This version includes lots of corrections and a few new features: Message priority, selective message persistence, filtered monitoring in webconsole.
Petals ESB 3.0.6 was also released as maintenance version, to use latest components.
Warning: Please do not activate notification with both versions. Another maintenance version will come with stable notification.

Released

• Petals ESB-Container 3.1.1 (and 3.1)
• Petals ESB-Container 3.0.6
• Internal: CDK 5.1
• Internal: WS-Notification 1.2.1 (for Petals View)
• Webconsole 2.0.4 (and 2.0.3)
• BC-Filetransfer 2.4.3
• BC-FTP 3.3
• BC-Mail 3.1.3
• BC-SFTP 1.2
• BC-SOAP 4.0.3
• SE-BPEL 1.0.4 (and 1.0.3)
• SE-KPI 1.1
• SE-XSLT 2.4
• SE-Talend 1.0.1

New Features

• [PETALSCDK-11] - Persist and resend notifications when problem occurs
• [PETALSCDK-13] - Add client API for notifications
• [PETALSCDK-17] - Add asynchronous client API for notifications
• [PETALSBCSOAP-34] - Axis 1 webservice stack compatibility
• [PETALSBCSFTP-22] - Add overwrite parameter
• [PETALSBCFTP-11] - Add overwrite parameter
• Petals ESB Container 3.1 - Regulates message flow across Petals domain
• Petals ESB Container 3.1 - Handles message priorities across Petals domains
• Petals ESB Container 3.1 - Persist messages when memory usages reach a given value
• Petals ESB Container 3.1 - Persist messages that are monitored in Webconsole
• Petals Webconsole 2.0.3 - Technical monitoring is back, with changes in Petals ESB collection

Improvements

• [PETALSCDK-9] - Improve notification provider subscription process
• [PETALSCDK-12] - Improve notification subscriber support
• [PETALSCDK-28] - Format the JBI descriptor with indentation
• [PETALSCDK-29] - Enhance the Fault management from error raising during InOut MEP process
• [WSNOTIF-1] - Create Document Builders on each notification requests
• [WSNOTIF-2] - Create Unmarshaller on each notification requests
• [WSNOTIF-3] - Convert Dom document into JDom one on each notification request
• [PETALSSEXSLT-1] - Improve the log management
• [PETALSSEXSLT-3] - Improve log & xsl error detection accuracy
• [PETALSSEXSLT-4] - Remove process related information from the INFO log
• [PETALSSEXSLT-6] - (AS-014) Having specific jbi.xml fields that would be parameters sent to the XSL at runtime
• [PETALSSEXSLT-12] - Properties of the incoming message should be passed to the XSL stylesheet as parameter
• [PETALSSEXSLT-14] - The SE should respect the InOut MEP
• [PETALSSEXSLT-15] - Some libraries are duplicated into the component archive
• [PETALSSEKPI-2] - Provide more than one consumes into the same service unit
• [PETALSSEKPI-3] - Parameters In/Out/Fault
• [PETALSSEKPI-4] - Log4j configuration file
• [PETALSSEBPEL-2] - JDOM to DOM conversion generate double namespace in AXIOM at marshal time
• [PETALSBCSOAP-15] - Resolve the target operation and MEP in consume mode
• [PETALSBCSOAP-38] - Remove the SU parameters add-root and remove-root
• [PETALSBCSOAP-39] - JMS parameters should be settable from the configuration MBean
• [PETALSBCSOAP-41] - wrong log level when ctaching axis exception
• [PETALSBCSOAP-48] - The fault actor is not transmitted in the SOAP fault in the consumer mode
• [PETALSSETAL-8] - Log the bus messages in DEBUG
• [PETALSSETAL-7] - Add 'processor-max-pool-size' and 'properties-file' in the component's jbi.xml
• Petals SE-BPEL 1.0.3 - Performance optimizations, up to 4x faster
• Petals Webconsole 2.0.3 - Improved monitoring performances (by filtering selected monitoring monitoring)
• Petals SE-Talend 1.0.1 - Compatible with Talend Open Studio 4.1.0

Bugs fixed

• [PETALSESBCONT-19] - Leak on PriorityOrdererModule
• [PETALSESBCONT-21] - StackOverflowError dans la WebConsole
• [PETALSESBCONT-33] - java.lang.ArrayIndexOutOfBoundsException when registring an endpoint without interface
• [PETALSESBCONT-40] - Error stack trace when stopping an empty container
• [PETALSESBCONT-46] - Classloader isolation uncomplete
• [PETALSESBCONT-60] - Too many open Files when sending attachment to remote node
• [PETALSESBCONT-61] - Prevent a container to override it's own configuration when synchronizing its topology.
• [PETALSCDK-6] - [CDK] RejectedExcecutionException is not correclty catched in the JBI acceptor
• [PETALSCDK-22] - Error on JBI Worker during performance tests
• [PETALSCDK-23] - Unpredictable FileNotFoundException: /createCustomer.xsd (No such file or directory)
• [PETALSCDK-25] - The CDK activate notification endpoints even if notification is off
• [PETALSWEBC-2] - StackTrace cause by OpenSUIT handling
• [PETALSWEBC-27] - Same service assembly deployement
• [PETALSSEXSLT-2] - [SE-XSLT] Can't import properly XSL stylesheet with imports
• [PETALSSEXSLT-8] - Imports are not correctly handled
• [PETALSSEXSLT-9] - Unable to load the XSL using the classloader
• [PETALSSEXSLT-11] - Unable to start the component if SE Notif is not available
• [PETALSBCSOAP-2] - When handling SOAP faults, faultCode can have an unbounded prefix.
• [PETALSBCSOAP-16] - Some traces are not handled by the component logger and some others at a level too high
• [PETALSBCSOAP-17] - As consumer, the timeout of a sendSync is not properly logged
• [PETALSBCSOAP-19] - Modules are loaded even if they are not set in configuration
• [PETALSBCSOAP-24] - Can't create get an Axis service client from the pool
• [PETALSBCSOAP-26] - NPE in the Petals console
• [PETALSBCSOAP-28] - Propagate partner's SOAP Fault "as is"
• [PETALSBCSOAP-32] - Log that JMS is activated whereas the SU configuration specifies not.
• [PETALSBCSOAP-35] - SOAP over JMS - A queue is created on the JMS server when installing a SU even if the JMS transport parameter is disabled
• [PETALSBCSOAP-40] - Unable to start the component if SE Notif is not available
• [PETALSBCSOAP-42] - BC soap returns wrong WSDL.
• [PETALSBCSOAP-43] - Change the default host in the jbi.xml of the component to 0.0.0.0
• [PETALSBCSOAP-44] - Error when uninstalling a SU REST
• [PETALSBCSOAP-45] - 0.0.0.0, the default host, crashes the component under some OS
• [PETALSBCSFTP-3] - The SSH/SFTP connections are not properly handled.
• [PETALSBCSFTP-7] - Parameter "folder" is marked as optionnal
• [PETALSBCSFTP-18] - SFTP connection not reset
• [PETALSBCSFTP-26] - Unable to start the component if SE Notif is not available
• [PETALSBCMAIL-11] - Unable to start the component if SE Notif is not available
• [PETALSBCFTP-14] - Unable to start the component if SE Notif is not available
• [PETALSBCFTP-17] - <folder> attribute written as optionnal, but sends a fault when not specified in my case
• [PETALSBCFTP-19] - [FTP] No error returned when remote directory is unavailable
• [PETALSBCFTRANS-10] - Unable to start the component if SE Notif is not available
• [PETALSBCFTRANS-12] - Consume mode, error when polled directory is unreachable
• [PETALSSETAL-4] - Use the exceptions that are declared in the WSDL
• [PETALSSETAL-5] - Unable to start the component if SE Notif is not available
• [PETALSSETAL-9] - Input streams are not closed correctly

Petals ESB 3.0.6 was released. It adds minor corrections and compatibility with latest component version.
Note: notification should not be activated with this release. Next maintenance release will include stable notification.

Bugs fixed:

• [PETALSESBCONT-46] - Classloader isolation uncomplete
• [PETALSESBCONT-60] - Too many open Files when sending attachment to remote node
• [PETALSESBCONT-61] - Prevent a container to override it's own configuration when synchronizing its topology.

Lots of components were added in the new JBI component sandbox section. They include deprecated components which might need some adaptation before use, and newly created beta components. They could become useful with small corrections, so the source (and only the source) is provided. Contributions are very welcome.

Sandbox components :
Binding components : Channel client, HTTP, Rest Proxy, RMI, SMS, TCP-IP, XMPP, XQUARE
Service engines : Bonita, CSV, Drools, Edifact, EIP orchestration, Enveloptransformer, Orchestra, Script, transcoder

Funny fact, there is exactly 19 stable and 19 sandbox components :)

Petals ESB 3.0.3 is released, as a maintenance version. It includes bug fixes, and performance optimization, expecially in distributed context. See release note for more information.

Administration webconsole, and components were updated : BC-Filetransfer, BC-FTP, BC-JMS, BC-Mail, BC-SFTP, BC-SOAP, BC-SQL, SE-BPEL, SE-EIP, SE-JSR181, SE-KPI, SE-Notification, SE-Pojo, SE-Validation, SE-XSLT

The SE-RMI component was also pushed from "sandbox" to "stable and supported". This process goes into the quality improvement we started with Camelia edition, which will continue to improve.

Note about documentation : Petals documentation is going to top-priority, as part of quality improvement as well. It is being completely restructured, and will be available and up-to-date within a few weeks. For now, using the old documentation and the forum should work as well. Be patient... And welcome on the forum.