No-one replied to my earlier post, is an Adobean available to look at this?
The testdrive-datapush sample program uses AMF as the primary channel,so AMFStreaming was probably never used. I should have previously mentioned that I had changedmessaging-config.xml as follows so streaming is used exclusively for messaging: <default-channels> <channel ref="my-streaming-amf"/> </default-channels> I modified services-config.xml so my-streaming-amf is now defined as follows: <channel-definition id="my-streaming-amf" class="mx.messaging.channels.StreamingAMFChannel"> <endpoint url="http://{server.name}:{server.port}/{context.root}/messagebroker/str\ eamingamf" class="flex.messaging.endpoints.StreamingAMFEndpoint"> <properties> <idle-timeout-minutes>0</idle-timeout-minutes> <max-streaming-clients>10</max-streaming-clients> <server-to-client-heartbeat-millis>5000</server-to-client-heartbeat-mill\ is> <user-agent-settings> <!-- MSIE 5, 6, 7 limit is 2. --> <user-agent match-on="MSIE" max-streaming-connections-per-session="1" kickstart-bytes="2048"/> <!-- MSIE 8 limit is 6. --> <user-agent match-on="MSIE 8" max-streaming-connections-per-session="5" kickstart-bytes="2048"/> <!-- Firefox 1, 2 limit is 2. --> <user-agent match-on="Firefox" max-streaming-connections-per-session="1"/> <!-- Firefox 3 limit is 6. --> <user-agent match-on="Firefox/3" max-streaming-connections-per-session="5"/> <!-- Safari 3, 4 limit is 4. --> <user-agent match-on="Safari" max-streaming-connections-per-session="3"/> <!-- Chrome 0, 1, 2 limit is 6. --> <user-agent match-on="Chrome" max-streaming-connections-per-session="5"/> <!-- Opera 7, 9 limit is 4.--> <user-agent match-on="Opera" max-streaming-connections-per-session="3"/> <!-- Opera 8 limit is 8. --> <user-agent match-on="Opera 8" max-streaming-connections-per-session="7"/> <!-- Opera 10 limit is 8. --> <user-agent match-on="Opera 10" max-streaming-connections-per-session="7" /> </user-agent-settings> </properties> </endpoint> </channel-definition>The log messages have now changed to: my-streaming-amf' channel endpoint set to http://localhost:8400/samples/messagebroker/amfstreaming 'B48F00D0-58FC-D64F-8F15-7F561D53C000' consumer set destination to 'feed'. 'B48F00D0-58FC-D64F-8F15-7F561D53C000' consumer subscribe. 'my-streaming-amf' pinging endpoint. 'my-streaming-amf' channel got status. (Object)#0 code = "NetConnection.Call.Failed" description = "HTTP: Failed" details = "http://localhost:8400/samples/messagebroker/amfstreaming" level = "error" 'my-streaming-amf' channel polling stopped. 'my-streaming-amf' channel connect failed. 'B48F00D0-58FC-D64F-8F15-7F561D53C000' consumer channel faulted with Channel.Connect.Failed NetConnection.Call.Failed: HTTP: Failed: url: 'http://localhost:8400/samples/messagebroker/amfstreaming' Suggestions? Mike --- In flexcoders@yahoogroups.com, "Michael Slinn" <msl...@...> wrote: > > > I am able to programmatically create a RemoteObject to call RPCs > against, and now I am trying to programmatically create a messaging > Consumer that listens on a streaming AMF channel. > > I have cranked up logging verbosity. I note the 404 (not found) message: > [SWF] /samples/testdrive-datapush/ProgMsg.swf - 883,736 bytes after > decompression > 'my-streaming-amf' channel endpoint set to > http://localhost:8400/samples/messagebroker/amfstreaming > 'A9D9B478-E4BB-6C26-196F-7B082707F804' consumer set destination to > 'feed'. > 'A9D9B478-E4BB-6C26-196F-7B082707F804' consumer subscribe. > 'my-streaming-amf' pinging endpoint. > 'my-streaming-amf' channel got status. (Object)#0 > code = "NetConnection.Call.Failed" > description = "HTTP: Status 404" > details = "http://localhost:8400/samples/messagebroker/amfstreaming" > level = "error" > 'my-streaming-amf' channel polling stopped. > 'my-streaming-amf' channel connect failed. > The streaming AMF endpoint looks right to me. What am I missing? > > Here is the (small) test project source code: > http://www.mslinn.com/sites/flex/progMsg.zip > > For convenience, the SWF and HTML files built by this test project drop > into the {BlazeDsTurnkey}/tomcat/webapps/samples/testdrive-datapush > directory and the project can be run from > http://localhost:8400/samples/testdrive-datapush/ProgMsg.html >