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-ALPHA Released

Pre-release
Pre-release
Compare
Choose a tag to compare
@virajsenevirathne virajsenevirathne released this 08 Apr 16:45
· 391 commits to master since this release
v5.0.0-ALPHA
d90f79f

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

Bug

  • [ESBJAVA-4269] - SSL Error : server certificate change is restrictedduring renegotiation with SSL tunneling
  • [ESBJAVA-4284] - Message building fails at high concurrency, when the out sequence is content aware
  • [ESBJAVA-4329] - Deploying a proxy with startOnLoad="false" using a CAR file deploys the proxy as inactive gives a SynapseException when calling certain Proxies.
  • [ESBJAVA-4394] - Error response created via makefault is never sent to the client when the error 101508 occurs by closing the TCP mon connection
  • [ESBJAVA-4423] - Custom status message descriptions in response, are not retained when using the passthrough transport
  • [ESBJAVA-4433] - When a json string is staring with space or newline, payload factory mediator escaping the quotes
  • [ESBJAVA-4452] - Error performing callout operation when endpoint returns empty response
  • [ESBJAVA-4458] - Inbound vfs transport streaming
  • [ESBJAVA-4461] - Subprotocol support for Websocket inbound
  • [ESBJAVA-4469] - FORCE_SC_ACCEPTED not working when OUT_ONLY and call are used in the flow.
  • [ESBJAVA-4490] - Message processor throws NumberFormatException when it fails to receive a response from endpoint
  • [ESBJAVA-4504] - [ESB500][UI]- When adding new sequence, name of exisiting dynamic sequence appears and can not add a new sequence.
  • [ESBJAVA-4507] - Memory Leak in Rule Mediator
  • [ESBJAVA-4512] - Response Body is missing When Invoking a REST API In tenant mode
  • [ESBJAVA-4518] - Pinned server support for file inbound
  • [ESBJAVA-4519] - Duplicate resource definition get thrown when editing already deployed API
  • [ESBJAVA-4540] - Proxy Service deployment failed when pinnedService parameter value does not contain current instance name
  • [ESBJAVA-4544] - Error handling in HL7 Inbound should trigger the fault sequence if auto ack is false in both decoder level and parser level

Improvement

  • [ESBJAVA-4372] - Mediation debugging support for mediators which have inlined sequences.
  • [ESBJAVA-4415] - SSL support for MQTT inbound
  • [ESBJAVA-4425] - ESB - Inbound MQTT endpoint - How to get topic in mediation

New Feature

Patch

  • [ESBJAVA-4251] - ESB Message Building Failure when a Data Service Returns 202

Task

Known Issues

All the open issues pertaining to WSO2 Enterprise Service Bus are reported at the following location:

Known Issues

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 --

Assets 3
Loading