The ChannelSet should send a disconnected event when the client detects from the server that it has been disconnected. You should get immediate notification for RTMP channels since we deliver this even when the server closes the client's connection.
I don't see how a firewall would affect this unless the RTMP connection itself failed to be made through the firewall. You might be falling back to RTMPT which is a polling implementation using the same port but I think that RTMPT though would also deliver the disconnected event in the same way as RTMP. If you have an AMF/HTTP channel defined as a fallback, it might be that you are using that channel now instead. For those channels, we rely on the app server's session to track the connected state of the user. The session will typically not timeout though on a polling channel because the poll requests keep it alive. Instead, you have to set a subscription-timeout on the destinations you are subscribing to. Once your subscriptions timeout, your consumer's "subscribed" property will get set to false and polling will stop so your session can eventually timeout. You can watch that "subscribed" property to detect that case. Jeff ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of nhid Sent: Tuesday, December 18, 2007 1:55 PM To: [email protected] Subject: [flexcoders] Configuring message channels - RTMP Hi, Our system has a messaging broadcasting feature for timeout. When it times out an alert pops up to the user. It seems to be after we have installed a firewall in the network, this feature stopped working, the alert doesn't pop up anymore. What properties should be used or what should be added to fix this problem? This is what we have: <channel-definition id="my-rtmp" class="mx.messaging.channels.RTMPChannel"> <endpoint uri="http://{server.name}:2296/"; class="flex.messaging.endpoints.RTMPEndpoint "/> <properties> <idle-timeout-minutes>20</idle-timeout-minutes> <websphere-workmanager-jndi-name>java:comp/env/wm/MessagingWorkManager</ websphere-workmanager-jndi-name> <client-to-server-maxbps>100K</client-to-server-maxbps> <server-to-client-maxbps>100K</server-to-client-maxbps> </properties> </channel-definition> Thank you.
