I have a class that derives from Weborb.Messaging.Server.Adapter.ApplicationAdapter and uses the [ApplicationInstance] attribute (so it’s hosted as a singleton).

Our flash is able to connect over HTTP and invoke all methods successfully. If I attach the debugger to w3wp I can see breakpoints being hit on appConnect and on the methods being called: everything works perfectly.

When the flash is switched-over to using RTMP, I can also see the appConnect method being called (and Flash receives a Connect.Success NetStatus event), and appDisconnect when the connection is terminated. Where things start to break down is when I try and invoke a method on the handler. Using wireshark I have been able to observe RTMP/TCP packets that appear to constitute the request arriving at my machine. However, the method is never called. Flash certainly behaves as though the method was called correctly, although the Responder object passed with the method call never receives a callback. This causes Flash to “hang” as it waits for the call to complete (which of course it never will). At no time does Flash receive a Failed or Faulted event reporting failure.

This behaviour is observed more frequently when we use AMF0 than AMF3, although it occurs with both.

My question is: what am I doing wrong, and how do I diagnose and resolve these issues?