[
https://wso2.org/jira/browse/ESBJAVA-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evanthika Amarasiri closed ESBJAVA-427.
---------------------------------------
Tested on wso2esb-1.7. The loadbalancing scenario works fine with using
endpoints that are defined under 'Manage Endpoints'. The issue can be closed.
> Failover sending fails when endpoints defined in the local/integrated
> resgistry are used inside the sequence
> ------------------------------------------------------------------------------------------------------------
>
> Key: ESBJAVA-427
> URL: https://wso2.org/jira/browse/ESBJAVA-427
> Project: WSO2 ESB
> Issue Type: Bug
> Components: Endpoints Management
> Affects Versions: 1.6
> Environment: Ubuntu7.04, JDK1.5.0_12
> Reporter: Evanthika Amarasiri
> Assignee: indika kumara
> Fix For: 1.7
>
>
> Below is the configuration which I tried out.
> *******************************************************************************************************************************
> <syn:endpoint name="port_9001">
> <syn:address uri="http://localhost:9001/soap/LBService1";
> statistics="enable">
> <syn:enableAddressing/>
> <syn:suspendDurationOnFailure>5</syn:suspendDurationOnFailure>
> </syn:address>
> </syn:endpoint>
> <syn:endpoint name="port_9002">
> <syn:address uri="http://localhost:9002/soap/LBService1";
> statistics="enable">
> <syn:enableAddressing/>
> <syn:suspendDurationOnFailure>5</syn:suspendDurationOnFailure>
> </syn:address>
> </syn:endpoint>
> <syn:endpoint name="port_9003">
> <syn:address uri="http://localhost:9003/soap/LBService1";
> statistics="enable">
> <syn:enableAddressing/>
> <syn:suspendDurationOnFailure>5</syn:suspendDurationOnFailure>
> </syn:address>
> </syn:endpoint>
> <syn:sequence name="errorHandler">
> <syn:makefault version="soap12">
> <syn:code xmlns:sf12="http://www.w3.org/2003/05/soap-envelope";
> value="sf12:Receiver"/>
> <syn:reason value="COULDN'T SEND THE MESSAGE TO THE SERVER."/>
> </syn:makefault>
> <syn:header name="To" action="remove"/>
> <syn:property name="RESPONSE" value="true"/>
> <syn:send/>
> </syn:sequence>
> <syn:sequence statistics="enable" name="sample" onError="errorHandler">
> <syn:in>
> <syn:send>
> <syn:endpoint>
> <syn:failover>
> <syn:endpoint key="port_9001"/>
> <syn:endpoint key="port_9002"/>
> <syn:endpoint key="port_9003"/>
> </syn:failover>
> </syn:endpoint>
> </syn:send>
> <syn:drop/>
> </syn:in>
> <syn:out>
> <syn:send/>
> </syn:out>
> </syn:sequence>
> *****************************************************************************************************************
> Once the request is sent, when the server 1 is shut down, it does not direct
> the requests to server 2 and just displays the message "COULDN'T SEND THE
> MESSAGE TO THE SERVER" and terminates the process.
> When the same scenario is tried out using address endpoints without accessing
> the endpoints defined in the local registry or the integrated registry is
> works as expected. (When server 1 is down the requests are directed to server
> 2 and so on.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
