DialogTimeout problem. Now we just ignore any DialogTimeout and keep a Dialog active. We have a risk that if a peer (SSF, SRF) part has been dead without CAMEL GW announsing than this activity will be alive forever (-> resourses will be overloaded).
The regular solution is - using of "activityTest" operation. Now CAP stack supports serializing for it and a CAMEL application. Also we have now "No activity call to HTTP Application" (https://telestax.atlassian.net/browse/CAMELGW-22) when Dialog is active too much time without messageflow
We need to make:
1) add support for sending of activityTest request / receiving of activityTest response
2) send InvokeTimeout announsements for any InvokeTimeout (including activityTest) to a CAMEL application
DialogTimeout problem. Now we just ignore any DialogTimeout and keep a Dialog active. We have a risk that if a peer (SSF, SRF) part has been dead without CAMEL GW announsing than this activity will be alive forever (-> resourses will be overloaded).
The regular solution is - using of "activityTest" operation. Now CAP stack supports serializing for it and a CAMEL application. Also we have now "No activity call to HTTP Application" (https://telestax.atlassian.net/browse/CAMELGW-22) when Dialog is active too much time without messageflow
We need to make: 1) add support for sending of activityTest request / receiving of activityTest response 2) send InvokeTimeout announsements for any InvokeTimeout (including activityTest) to a CAMEL application