This error usually means that the player has received an Externalizable type via AMF but there's not an Externalizable object registered for that alias. I am having trouble coming up with a way that would happen only on an HTTP based AMF channel since RTMP also encodes its data using AMF, it should see this error too. Probably sending the output from <mx:TraceTarget> (in flashlog.txt on the client) and enabling the level="Debug" for the Endpoint.* target in services-config.xml would contain enough info to track this down. Feel free to send it to me offlist as that can be a big file ([EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>).
The other things I'd check are that your rpc.swc and fds.swc are of the right version and match your server version. We added a "small messages" feature in LCDS2.6 which uses Externalizable for messages to make the wrapper smaller. That should be turned off by default for 2.5.1 clients but maybe something is getting messed up there. You can turn this off via the "enable-small-messages=false" flag in the channel's serialization properties (see resources/config/services-config.xml for an example). Jeff From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of taze170171 Sent: Tuesday, October 28, 2008 3:39 AM To: [email protected] Subject: [flexcoders] Secure AMF - Error #2004: One of the parameters is invalid Hello! We are using AIR together with LCDS. Until now we were using an RTMPS channel for communication. There everything works fine. For fallback handling we configured now an Secure AMF Channel. When using this channel the following error occurs when calling fill methods: ArgumentError: Error #2004: One of the parameters is invalid. Sync methods work fine!! The fill methods return type is Collection<...>. We also tried List<...> - same error. At the client we use mx.collections.ArrayCollection. The config files look like: Client config.xml: ... <channel id="my-secure-amf"> <type>secure-amf-polling</type> <endpoint>https://localhost:8443/messagebroker/amfsecure</endpoint> <interval>8000</interval> </channel> ... services-config: ... <channel-definition id="my-secure-amf" class="mx.messaging.channels.SecureAMFChannel"> <endpoint url="https:// {server.name}:8443/messagebroker/amfsecure" class="flex.messaging.endpoints.SecureAMFEndpoint"/> <properties> <!--HTTPS requests on some browsers do not work when pragma "no-cache" are set --> <add-no-cache-headers>false</add-no-cache-headers> </properties> </channel-definition> ... Thanks in advance, Taze
<<inline: image001.jpg>>
<<inline: image002.jpg>>
