Hi,
We are using both Remoting and HttpService calls for our business application.
We were able to communicate with the LCDS server till this point with whatever default settings provided for AMFChannel configuration in services-config.xml through a flex client. Also we have a clustered environment for this servers which works out fine till now.
Now for performance enhancement improvements, we started using Caching Mechanism for our HttpService urls (through some third party service), which will now be cached on the network instead of accessing every time from our clustered servers. But all our AMF calls through Remoting services are still the same.
So after migrating to this Caching environment, we started encountering intermittent issues where some of our AMF calls were failing with falling exception trace :
16:03:40,576 INFO [STDOUT] [Flex] [ERROR] Error handling message: flex.messaging.MessageException: No destination with id '' is registered with any service.
incomingMessage: Flex Message (flex.messaging.messages.CommandMessage)
operation = invalid.12
clientId = D7855C44-810B-64AB-C176-7C38F83DEB2C
correlationId =
destination =
messageId = 2DA6BDB8-859E-8AE1-03A4-57743DE03188
timestamp = 1247007820561
timeToLive = 0
body = {}
hdr(DSId) = D77C6BD2-3808-1512-3984-CCF397428E35
hdr(DSEndpoint) = my-amf
errorReply: Flex Message (flex.messaging.messages.ErrorMessage)
clientId = D7855C44-810B-64AB-C176-7C38F83DEB2C
correlationId = 2DA6BDB8-859E-8AE1-03A4-57743DE03188
destination =
messageId = D7855C64-3E08-466B-96F8-5BAE7D385129
timestamp = 1247007820574
timeToLive = 0
body = null
code = Server.Processing
message = No destination with id '' is registered with any service.
details = null
rootCause = null
body = null
extendedData = null
So i do not understand, most of the times the AMF calls works correctly and some times it fails with above fail trace.
Any suggestions would be appreciated.
Thanks,
FlexPirate
