Skip to content
This repository has been archived by the owner on Oct 5, 2021. It is now read-only.

WSO2 ESB 5.0.0-RC1 Released

Pre-release
Pre-release
Compare
Choose a tag to compare
@jagathsisira jagathsisira released this 02 Aug 17:00
· 196 commits to master since this release

ESB Team is pleased to announce the WSO2 ESB 5.0.0 - RC1 Release. It contains following improvement and bug fixes.

Bug

  • [ESBJAVA-2142] - NPE thrown when send GET request to non existing resource uri - axis2Server specific
  • [ESBJAVA-2831] - Unable to specify proxy to use with specific backend
  • [ESBJAVA-3879] - If API resources are specified incorrectly, cannot edit or delete these resources
  • [ESBJAVA-3903] - NPE when invoking a producer proxy with rabbitmq.replyto.name property [RabbitMQ]
  • [ESBJAVA-4226] - Duplicate entry error when a CAR file is re-deployed after updating the source view
  • [ESBJAVA-4241] - Some channels are not getting closed after publishing data to the queue with RabbitMQ transport
  • [ESBJAVA-4242] - Performance Improvements to RabbitMQ
  • [ESBJAVA-4263] - Message processor always deactivate.
  • [ESBJAVA-4393] - Message Processor deployed via a capp can not be reactivated, once it is automatically deactivated after reaching the max delivery attempts
  • [ESBJAVA-4409] - [JMS2.0] Connection lost error prints continuously and may fill the error logs very quickly
  • [ESBJAVA-4423] - Custom status message descriptions in response, are not retained when using the passthrough transport
  • [ESBJAVA-4646] - Message consumption stops in rabbitmq inbound when an ill formed message come
  • [ESBJAVA-4700] - Enrich mediator related artifact is not working when deployed through dev studio
  • [ESBJAVA-4707] - ESB builds the message in the request path when there are no content-aware mediators before the call mediator
  • [ESBJAVA-4715] - Supporting registry based parameter values in all Inbound Endpoints with secure vault capability
  • [ESBJAVA-4724] - Client does not received the message return by the fault sequence
  • [ESBJAVA-4739] - [ IBM JDK 8 / MySql] Unable to start ESB with IBM JDK 8 when registry mounted and pointed to Mysql 5.7
  • [ESBJAVA-4740] - [IBM JDK 8 / MsSql ] An exception triggered when starting ESB pack with IBM JDK 8 and MSSql
  • [ESBJAVA-4741] - [ Proxy / CSRF ] When accessing the Proxy service in source view, a CSRF error is triggered in logs
  • [ESBJAVA-4744] - [Data Mapper] Handle the NullPointer when wrong input type and output type is used
  • [ESBJAVA-4758] - Add a global statistics enabling parameter
  • [ESBJAVA-4760] - When response has 204 status code with disable chunking false, the response gets dropped
  • [ESBJAVA-4762] - SAP adaptor missing in plugins directory of 4.9.0
  • [ESBJAVA-4764] - Deleting connector from management console gives an empty page
  • [ESBJAVA-4768] - When using full path in sftp with file locking enabled, files processing gets skipped
  • [ESBJAVA-4770] - When using keys with 2048 key strength, password encryption fails in synapse vfs transport
  • [ESBJAVA-4771] - No Error is shown in ESB Console when Referring to a non existing Sequence Template
  • [ESBJAVA-4772] - [IBM JDK] Unable to start ESB pack with IBM JDK
  • [ESBJAVA-4774] - Atrifacts name text doesn't prevent of performing an XSS attack
  • [ESBJAVA-4778] - CXF orbit bundle import conflicts
  • [ESBJAVA-4779] - [Data Mapper][Mediation Debugger] Property operator does not take updated value of property when value changed while debugging
  • [ESBJAVA-4782] - Improve logging for ESB
  • [ESBJAVA-4783] - JMS store UI directs to MB message store UI when editing message store
  • [ESBJAVA-4784] - Event publisher and CSRF warnings observed at server startup in Windows
  • [ESBJAVA-4786] - [Data Mapper]Provide a proper error in runtime when we provide a wrong message format to what we provided in the DM mediator's "inputType"
  • [ESBJAVA-4787] - [Mediation Debugger] Debug point doesn't get registered inside case statements in switch-case mediaor
  • [ESBJAVA-4791] - Improve ESB5 logging to isolate the reason for a given failure.
  • [ESBJAVA-4793] - [VFS] [Secure password] Exception occurred when "security.provider" parameter is used in axis2.xml
  • [ESBJAVA-4794] - ESB Statistics publishing in a high load scenario causes the server to go OOM
  • [ESBJAVA-4798] - [Data Mapper] When mapping tree is created manually CSV to XML conversion is not working
  • [ESBJAVA-4801] - CAR file deployment fails for tenant when deployed through dev studio connected as Remote Server
  • [ESBJAVA-4802] - Axis2 Client scope property is not cleared correctly
  • [ESBJAVA-4804] - [VFS] [Secure Password] Error occurred when smb credentials are encrypted.
  • [ESBJAVA-4805] - [Proxy Profile] Proxy service can be invoked from ip addresses that are not included in targetHosts tag

Improvement

  • [ESBJAVA-3421] - Appending the port 80 for https requests
  • [ESBJAVA-3993] - Handle the error gracefully when trying to create a duplicate sequence
  • [ESBJAVA-4656] - Adding functionality to register custom statistic observers to recive statistics events
  • [ESBJAVA-4673] - Follow consistent naming for ESB runtime, tooling and analytics
  • [ESBJAVA-4722] - Support transport.jms.ConcurrentConsumers in inbound endpoint
  • [ESBJAVA-4773] - WSO2 ESB 5.0.0 Beta2 - carbon version is not correct
  • [ESBJAVA-4777] - Support transport.jms.ConcurrentConsumers in inbound endpoint

Patch

  • [ESBJAVA-4327] - Skipping the own onError sequence and hit the parent onError sequence with load
  • [ESBJAVA-4780] - The Fault sequence doesn't get invoked when queue capacity exceeded in IMB MQ
  • [ESBJAVA-4792] - Aggregate mediator takes messages after aggregate timeout

How You Can Contribute

Mailing Lists

Join our mailing list and correspond with the developers directly.

Developer List : dev@wso2.org | Subscribe | Mail Archive

Reporting Issues

We encourage you to report issues, documentation faults and feature requests regarding WSO2 Enterprise Service Bus through the public JIRA. You can use the Carbon JIRA to report any issues related to the Carbon base framework or associated Carbon components.

Support

We are committed to ensuring that your enterprise middleware deployment is completely supported from evaluation to production. Our unique approach ensures that all support leverages our open development methodology and is provided by the very same engineers who build the technology.

For more details and to take advantage of this unique opportunity please visit http://wso2.com/support.

To learn more about WSO2 Enterprise Service Bus and WSO2 support offerings please visit http://wso2.com/products/enterprise-service-bus/

-- The WSO2 Enterprise Service Bus Team --