An endpoint in ESB can have an optional timeout value. This value
indicates that the particular endpoint will wait this much of time until
the response arrive. If the response fails to arrive within the given
time limit the ESB will then discard any future responses or perform the
action (like sending a SOAP fault) specified in the timeout configuration.

Once a message is sent out a callback is registered inside the ESB. The
responsibility of the TimeoutHandler is to clean these callbacks based
on there timeout value. This way each endpoint can have their own
timeout values (Note: this value is different from socket timeout
value). You may even set that a particular endpoint will never timeout.

Note: The TimeoutHandler runs every 15 seconds, thus actual timeouts for
callbacks will be triggered within 0-15 seconds after the given timeout
value.

The 86400 seconds that you see (i.e. the time duration = 1 day) is a
global timeout value meaning that irrespective of the timeout values set
for endpoints, the ESB will by force timeout the callbacks after this
much of time. So in other words, even though you set that a particular
endpoint has an infinite timeout value, practically it will get only one
day to survive.

Thanks,
Saliya



Schmilinsky, Remsy wrote:
> Hi. What does it mean ? Can I increase this timeaout ?
>  
> 2008-09-24 15:29:54,103 [127.0.1.1-ubuntu] [SimpleThreadPoolWorker-1]  
> INFO TimeoutHandler This engine will expire all callbacks after : 
> 86400 seconds, irrespective of the timeout action, after the specified 
> or optional timeout
>  
> thanks
>  
> Remsy
> ------------------------------------------------------------------------
>
> _______________________________________________
> Esb-java-user mailing list
> [email protected]
> http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>   


_______________________________________________
Esb-java-user mailing list
[email protected]
http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user

Reply via email to