Hi Rim
With ESB 1.7.1 and other previous releases, Endpoint will get inactive
only after detecting connection error between service and ESB. So, it
needs to be occurred connection refuse, close, timeout, etc...to be
inactive endpoint. By adding,
<suspendDurationOnFailure>x</suspendDurationOnFailure> {x integer is in
second}, you can specify inactive time period, after that, it should be
active.
Could you please attach the synapse.xml and also log messages after
enable DEBUG as follows (editing log4j.properties file) so that we can
diagnose if there any issues and also we can help you for possible
solutions.
log4j.category.org.apache.synapse =DEBUG
BTW, we have improved the error hading at endpoint level in finer grain,
making suspended, do retry for selected errors, etc...[1]. But this is
only available with the Synapse / ESB trunk.
Thanks
Indika
[1] https://issues.apache.org/jira/browse/SYNAPSE-466
Rimi Elizabeth wrote:
Hi All,
I am using load balencer endpoint for calling 2 business services in
round robin fashion. It is fine but end points are becoming inactive
if we are not accessing it for 5, 10 mins.
It seems like it is some problem with wso2 itself.
Please suggest some solution to overcome this issue.
Thanks in advance.
Rimi
------------------------------------------------------------------------
_______________________________________________
Esb-java-user mailing list
[email protected]
http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user
------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.173 / Virus Database: 270.7.6/1709 - Release Date: 10/5/2008 9:20 AM
_______________________________________________
Esb-java-user mailing list
[email protected]
http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user
