In the dmcc-trace.log we see the route request:
2018-10-22 09.18.30,988 :T-63: com.avaya.mvcs.proxy.CstaMarshallerNode$CstaMarshallerThread run
FINEST: Marshalled session[null] ch.ecma.csta.binding.RouteRequest@1ca0bee to <?xml version="1.0" encoding="UTF-8"?>
<RouteRequest xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"><crossRefIdentifier>300837</crossRefIdentifier><routeRegisterReqID>80141</routeRegisterReqID>....
In our application, however, this request is delayed by over 30 sec: (our log)
2018-10-22 09:19:13.0411308 -05:00
<RouteRequest xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
<crossRefIdentifier>300837</crossRefIdentifier>
<routeRegisterReqID>80141</routeRegisterReqID>....
This exceeds the delay step and results in a closed request so we get invalid cross ref id on the response
here is our response:
2018-10-22 09:19:12.3548144 -05:00
<RouteSelect xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
<crossRefIdentifier>300837</crossRefIdentifier>
<routeRegisterReqID>80141</routeRegisterReqID>....
and the log from AES:
2018-10-22 09.19.12,967 :T-66: com.avaya.mvcs.proxy.CstaUnmarshallerNode$CstaUnmarshallerProcessorThread run
FINEST: Unmarshalled xml=<?xml version="1.0" encoding="utf-8"?>
<RouteSelect xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
<crossRefIdentifier>300837</crossRefIdentifier>
<routeRegisterReqID>80141</routeRegisterReqID>....
The application ran fine for about 2 hours, then started seeing these timeouts on some, but not all route requests.
any thoughts? is there a buffer or queue that is getting filled and creating the delay?
