WSO2 ESB 5.0.0-RC2 Released
Pre-releaseESB Team is pleased to announce the WSO2 ESB 5.0.0 - RC2 Release. It contains following improvement and bug fixes.
Bug
- [ESBJAVA-4140] - NullPointerException seen when server is kept idle (Ghost Deployer is enabled).
- [ESBJAVA-4176] - API invocation sends "202 Accepted" as the response if the HTTP method is not allowed
- [ESBJAVA-4254] - NPE when shutting down server.
- [ESBJAVA-4288] - [MQTT] Exception when editing inbound EP, eventually the server crashes
- [ESBJAVA-4333] - IllegalStateException when accessing APIs of tenants
- [ESBJAVA-4356] - Inbound endpoint interval shows null in editInbound.jsp although source configuration have interval specified
- [ESBJAVA-4428] - XML to XML transformation results in error, expected output is not given
- [ESBJAVA-4429] - When trying to use xpath expression with xml to text using csv parser in smooks, error is thrown
- [ESBJAVA-4472] - [ESB500M2][LongRun][Intermittent] WSSecurityException occurred when invoking WS Secured Proxy with correct Credentials
- [ESBJAVA-4696] - Given sample in documentation for XSLT mediator resources is not working
- [ESBJAVA-4708] - ESB Message building needs to be improved with the Call mediator introduction to synapse mediation engine
- [ESBJAVA-4729] - [ESB / Properties] When HTTP_SC property is set in super tenant mode HTTP Status message is not updated as per the http status code in super tenant
- [ESBJAVA-4747] - Unable to use sftpPathFromRoot parameter in File Inbound.
- [ESBJAVA-4785] - [RabbitMQ] Exclusive queue pool is created even when RPC scenarios are not used
- [ESBJAVA-4813] - Remove transport headers from axis2 scope property variables in mediation debugger
- [ESBJAVA-4816] - Endpoint Connection refused error '101503' doesn't go to Error sequence of the respective sequence but hit parents fault sequence
- [ESBJAVA-4820] - Error observed at ESB console when the debug connection is skipped by dev studio side
- [ESBJAVA-4821] - ESB server wait for WSDL URI till backend server close the connection when deploying a proxy service.
- [ESBJAVA-4823] - [Mediation Debugger] Tenant breakpoints were not hit while invocation
- [ESBJAVA-4824] - [Mediation Debugger] Server is started in debug mode even if -Desb.debug=false
- [ESBJAVA-4826] - Observing a warn message when performing a load test on ESB
- [ESBJAVA-4829] - Proxy services are shown as if they deploy with capp when there is a faulty capp and proxy services are hot deployed
How You Can Contribute
Mailing Lists
Join our mailing list and correspond with the developers directly.
Developer List : [email protected] | 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 --