Removing session/thread after client disconnect

Question

I'm using blazeDS to stream data in a push-only sort of fashion so I'm using a StreamingAMFChannel. This channel is configured as such:
<properties>
                <idle-timeout-minutes>1</idle-timeout-minutes>
                <max-streaming-clients>100</max-streaming-clients>
                <invalidate-session-on-disconnect>true</invalidate-session-on-disconnect>
                <user-agent-settings>      
                   <user-agent match-on="MSIE" kickstart-bytes="2048" max-streaming-connections-per-session="1"/>
                   <user-agent match-on="Firefox" kickstart-bytes="0" max-streaming-connections-per-session="4"/>
                   </user-agent-settings>
                <server-to-client-heartbeat-millis>500</server-to-client-heartbeat-millis>
</properties>
When a new client subscribes to the channel, a new thread is created. The problem is that when the client has disconnected, the thread remains and will remain not being used (as in a pooling sort of fashion) by future clients. I believe the problem is that, although the client was disconnected, the session never ends?
If this is the case, shouldn't invalidate-session-on-disconnect enable this? What steps are needed to make sure a thread/session dies when the client is disconnected (by idle or call)?
I understand the a session might have multiple channels it is subscribed to, so the idea that one channel can cause a session disconnect is a bit strange (and maybe this is where things fall apart).

Answer 1

The invalidate-session-on-disconnect property comes into effect only when you explicly send a disconnect message to the server. Consider calling channelset.disconnectAll() explicitly from your client. The documentation describes how it can be done.
Rohit