BlazeDS and Flex Client Deployed on Different Servers

Question

Hi, I setup a BlazeDS AMF endpoint on a different server from the server where my Flex app is deployed. I get the following error from my Flex app when trying to use this endpoint:
   faultCode: Client.Error.MessageSend
   faultDetail: Channel.Security.Error error Error #2048 url: 'http://cafrfd1y5css50.itsdo.abc.com:7000/sfaflexservice/amf'
   faultString: Send failed
   rootCause:
       [ChannelFaultEvent
        faultCode="Channel.Security.Error"
        faultString="error"
        faultDetail="Error #2048 url: 'http://cafrfd1y5css50.itsdo.abc.com:7000/sfaflexservice/amf'"
        channelId="my-amf"
        type="channelFault"
        bubbles=false
        cancelable=false
        eventPhase=2]
Btw, this setup works fine when my Flex app runs on AIR or as a Flex app (in a browser) from Flex Builder.
This looks like a crossdomain policy issue, so I setup a crossdomain.xml file on the BlazeDS server. When I point my browser to http://cafrfd1y5css50.itsdo.abc.com:7000/crossdomain.xml, I see the following:
    <?xml version="1.0" encoding="UTF-8" ?>
    <cross-domain-policy>
       <allow-access-from domain="*.abc.com" />
    </cross-domain-policy>
Looks good, but I get the same error...
So I monitored the interaction with Fiddler to see if the crossdomain.xml file is loaded. It is. When the service is activated, I see the following GET command in Fiddler:
     GET /crossdomain.xml HTTP/1.1
     Host: cafrfd1y5css50.itsdo.abc.com:7000
And the response contains the contents of the crossdomain.xml file, so I don't know what's going on.
My configuration is:
-- Browser: IE7 or FireFox v3.5 with Flash Player v10.
-- Flex app uses the 3.4 SDK and is deployed on a Tomcat v6 server.
-- BlazeDS server is WebLogic v9.
-- Endpoint definition from services-config.xml on the BlazeDS server is:
   <channel-definition id="my-amf" class="mx.messaging.channels.AMFChannel">
     <endpoint url="http://{server.name}:{server.port}/{context.root}/messagebroker/amf" class="flex.messaging.endpoints.AMFEndpoint"/>
   </channel-definition>
-- Endpoint in the Flex app is defined as follows:
   <channel alias="FlexBean">
      <channel_def>my-amf</channel_def>
      <endpoint>http://cafrfd1y5css50.itsdo.abc.com:7000/sfaflexservice/amf</endpoint>
      <destination>FlexService</destination>
   </channel>
Any ideas would be much appreciated...
thanks,
matt

Answer 1

Thanks for the reply, Alex.
I tried setting the domain in the crossdomain policy file to "*", but I got the same error, so I turned on client side logging. The error in the log was:
Error: [strict] Ignoring policy file at http://cafrfd1y5css50.itsdo.abc.com:7000/crossdomain.xml due to missing Content-Type.
See http://www.adobe.com/go/strict_policy_files to fix this problem.
Using Fiddler, I checked the content-type that WebLogic was using for crossdomain.xml. Much to my surprise, there wasn't a content-type in the response, only content-length. So in the web.xml file for this application, I added the following:
<mime-mapping>
    <extension>xml</extension>
    <mime-type>text/xml</mime-type>
</mime-mapping>
Now, the crossdomain.xml file is served with a content-type of "text/xml", and the call to the BlazeDS endpoint works.
Thanks for steering me in the right direction, Alex.
cheers!
matt