WSO2 Elastic Load Balancer (ELB) 2.1.0 Released! 24th October, 2013 The WSO2 ELB team is pleased to announce the release of version 2.1.0 of the Open Source Elastic Load Balancer (ELB).
WSO2 ELB is a fast, lightweight and user friendly open source Elastic Load Balancer (ELB) distributed under the Apache Software License v2.0<http://www.apache.org/licenses/LICENSE-2.0.html>. WSO2 ELB allows system administrators and developers to easily configure fail over routing, load balancing, service aware load balancing, tenant aware load balancing and dynamic load balancing with auto scaling.The ELB runtime is designed to be completely asynchronous, non-blocking and streaming based on the Apache Synapse <http://synapse.apache.org/>mediation engine. WSO2 ELB 2.1.0 is developed on top of the revolutionary WSO2 Carbon platform<http://wso2.org/projects/carbon>, an OSGi based framework that provides seamless modularity to your SOA via componentization. This release also contains many new features and a range of optional components (add-ons) that can be installed to customize the behavior of the ELB. Further, any existing features of the ELB which are not required to your environment can be easily removed using the underlying provisioning framework of Carbon. In brief, WSO2 ELB can be fully customized and tailored to meet your exact SOA needs. You can download this distribution from http://wso2.com/products/elastic-load-balancer/ our product page and give it a try. How to Run 1. Extract the downloaded zip 2. Go to the bin directory in the extracted folder 3. Run the wso2server.sh or wso2server.bat as appropriate 4. Configure the load balancer to manage the load across the instances to be balanced. 5. If you need to start the OSGi console with the server use the property -DosgiConsole when starting the server. The INSTALL.txt file found on the installation directory will give you a comprehensive set of options and properties that can be passed into the startup script Key Features of WSO2 ELB - Non-blocking HTTP/S transports based on Apache HttpCore-NIO for ultra-fast execution and support for thousands of connections at high concurrency with constant memory usage. Integrated high performing, Passthrough Transport. - Load-balancing (with or without sticky sessions)/Fail-over, and clustered Throttling and Caching support - Lightweight, XML and Web services centric messaging model - Automatically scaling the system according to the number of requests in-flight for a particular service cluster - "Scale up early, scale down slowly" - Service aware dynamic load balancing - A single load balancer can centrally manage the load across the nodes of different service clusters. - Tenant aware load balancing - Tenants can be loaded and unloaded dynamically. Tenants can be partitioned to different service clusters. - Clustering and Distributed Caching implementation based on Hazelcast. New Feature - [LB-110 <https://wso2.org/jira/browse/LB-110>] - Need a property to enable domain mapping in loadbalancer.conf Improvements - [LB-68 <https://wso2.org/jira/browse/LB-68>] - TenantAwareLoadBalanceEndpoint should made configurable via loadbalancer.conf - [LB-113 <https://wso2.org/jira/browse/LB-113>] - Adding support to drop faulty members which cannot be reached via tribes port Tasks - [LB-91 <https://wso2.org/jira/browse/LB-91>] - Merge the fix for ELB session replication issue with trunk - [LB-98 <https://wso2.org/jira/browse/LB-98>] - ELB 2.1.0 licence doc Bugs Fixed - [LB-72 <https://wso2.org/jira/browse/LB-72>] - Default Linux JVM settings required 64-bit - [LB-73 <https://wso2.org/jira/browse/LB-73>] - ELB removes sessions and it causes SSO scenarios to fail on certain instances. - [LB-74 <https://wso2.org/jira/browse/LB-74>] - Following error occurs when launching application from appfactory. - [LB-75 <https://wso2.org/jira/browse/LB-75>] - ELB becomes unresponsive. CPU Usage goes 100%. Load average is high. - PT hits JDK bug - [LB-78 <https://wso2.org/jira/browse/LB-78>] - [Chrome] Cannot access Mgt Node in cluster setup with Chrome: Gets a http 324 error code - [LB-79 <https://wso2.org/jira/browse/LB-79>] - WSDLs are not shown in ESB cluster setup - [LB-80 <https://wso2.org/jira/browse/LB-80>] - dead page and the IP of the management node is shown when user is signed out from the cluster setup - [LB-83 <https://wso2.org/jira/browse/LB-83>] - Message relay component has caching dependencies. - [LB-85 <https://wso2.org/jira/browse/LB-85>] - [Intermittent] NPE - ERROR {org.apache.synapse.transport.passthru.TargetHandler} - Unexpected error: null - [LB-87 <https://wso2.org/jira/browse/LB-87>] - Carbondump scripts are not included in the ELB - [LB-88 <https://wso2.org/jira/browse/LB-88>] - https requests are getting hang intermittently in the clustered setup - [LB-90 <https://wso2.org/jira/browse/LB-90>] - [Intermittent] HTTPS requests gets hanged after sometime when continuesly invoked - [LB-94 <https://wso2.org/jira/browse/LB-94>] - Load Balancer send back all HTTP responses in TEXT/HTML format - [LB-96 <https://wso2.org/jira/browse/LB-96>] - SSLException: bad record MAC, when accessing an LB fronted AS cluster via Google chrome - [LB-97 <https://wso2.org/jira/browse/LB-97>] - Cannot access Management Console of the Worker/Mgr separated setup. Throws "System may be unstable: HTTPS ListeningIOReactor encountered a runtime exception : Null action" - [LB-99 <https://wso2.org/jira/browse/LB-99>] - ./wso2server.sh start creates a nohup.out - [LB-100 <https://wso2.org/jira/browse/LB-100>] - Accessing a wsdl from tenant mode not working in Registry based Dep Sync - [LB-102 <https://wso2.org/jira/browse/LB-102>] - Exception in INFO log in ELB - [LB-103 <https://wso2.org/jira/browse/LB-103>] - "HTTP/1.1 401 OK" instead of "HTTP/1.1 401 Unauthorized" returned when invoking a secured (with UT) SOAP service with a non-secured client when fronted by an ELB - [LB-104 <https://wso2.org/jira/browse/LB-104>] - OpenID login fails in Loadbalanced cluster with ELB - [LB-105 <https://wso2.org/jira/browse/LB-105>] - java.lang.NullPointerException observed on ELB - [LB-106 <https://wso2.org/jira/browse/LB-106>] - The first time you try to enable security for a service for a tenant/super tenant in a worker/manager separated setup, it takes ~3 minutes & then the ELB spins - [LB-108 <https://wso2.org/jira/browse/LB-108>] - EOFException[Could not read protocol type!] - [LB-111 <https://wso2.org/jira/browse/LB-111>] - "Tenant domain has not been set in CarbonContext" thrown when sending requests to ELB from a non-existing domain - [LB-112 <https://wso2.org/jira/browse/LB-112>] - When AuthManager is set to an external Key Manager cluster through an ELB, loggin in to publisher fails - [LB-115 <https://wso2.org/jira/browse/LB-115>] - Spinning issue from HTTP Core - [LB-117 <https://wso2.org/jira/browse/LB-117>] - Dynamically adding cluster domains not getting initialized - [LB-118 <https://wso2.org/jira/browse/LB-118>] - log4j error at ELB startup Known Issues All the open issues pertaining to WSO2 ELB 2.1.0 are reported at following locations: - Open ELB issues <https://wso2.org/jira/browse/LB-77?filter=11578&jql=project%20%3D%20LB%20AND%20issuetype%20%3D%20Bug%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20FUTURE%20ORDER%20BY%20priority%20DESC> How You Can Contribute Mailing Lists Join our mailing list and correspond with the developers directly. - Developer List : [email protected] | Subscribe<[email protected]?subject=subscribe>| Mail Archive <http://wso2.org/mailarchive/carbon-dev/> Reporting Issues We encourage you to report issues, documentation faults and feature requests regarding WSO2 ELB through the public ELB JIRA<https://wso2.org/jira/browse/LB>. You can use the Carbon JIRA <https://wso2.org/jira/browse/CARBON> to report any issues related to the Carbon base framework or associated Carbon components. Discussion Forums Alternatively, questions could be raised using StackOverflow<http://stackoverflow.com/questions/tagged/wso2>website. 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. *-- The WSO2 ELB Team --* -- Thanks and Regards, Isuru H. Software Engineer, WSO2 Inc. +94 716 358 048* <http://wso2.com/>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
