[gatein-issues] [JBoss JIRA] (GTNWSRP-363) WSRP load-balancing & failover embedded into WSRP itself, without httpd in front of the cluster

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/GTNWSRP-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923202#comment-12923202 ] 

RH Bugzilla Integration commented on GTNWSRP-363:
-------------------------------------------------

Jiri Pallich <jpallich at redhat.com> changed the Status of [bug 961242|https://bugzilla.redhat.com/show_bug.cgi?id=961242] from NEW to CLOSED
                
> WSRP load-balancing & failover embedded into WSRP itself, without httpd in front of the cluster
> -----------------------------------------------------------------------------------------------
>
>                 Key: GTNWSRP-363
>                 URL: https://issues.jboss.org/browse/GTNWSRP-363
>             Project: GateIn WSRP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Producer, Specification Support
>         Environment: - JBoss EPP
>   - 5
>   - 6
>            Reporter: Adam Kovari
>            Assignee: Chris Laprun
>            Priority: Minor
>
> This is a feature request for having an ability of WSRP to handle clustering on it's own, e.g. without an external load-balancer such as httpd.
> The reason for this is an extra weight that external load balancer adds, in environments with 100s-1000s of virtual deployment this is a considerable issue.
> It should work like this:
> {code}
> <wsrp-producer id="business" expiration-cache="500" ws-timeout="10000">
>             <!--*@
>             The endpoint-wsdl-url of the wsrp-producer with the id business.
>             Usually something like http://127.0.0.1:17110/wsrp-producer/v2/MarkupService?wsdl
>             @*-->
>             <endpoint-wsdl-url>https://xxx:17111/wsrp-producer/v2/MarkupService?wsdl</endpoint-wsdl-url>
>             <endpoint-wsdl-url>https://xxx2:17111/wsrp-producer/v2/MarkupService?wsdl</endpoint-wsdl-url>
>             <registration-data/>
>         </wsrp-producer>
> {code}
> So that there would be a possibility to define multiple endpoints of which the WSRP implementation itself would choose based on failover/load-balancing policies.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira