session termination bug for sessions with multiple streams.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Add a stream to session and keep sending messages through this stream.
2. Try to add another stream to the above session which is invalid.
3. Send a stream terminate request from the client for the above invalid stream

What is the expected output? What do you see instead?
The expected output is that the session should continue. However, the session 
is getting terminated.  

Please use labels and text to provide additional information.

Original issue reported on code.google.com by anup.kal...@gmail.com on 11 Nov 2011 at 5:20

[GoogleCodeExporter]

Just to make it more clear. The step 2 to reproduce the problem can be read as:

2. Try to add another (invalid) stream to the above session. This can be done 
by adding another account on the same session with invalid credentials. 

Original comment by anup.kal...@gmail.com on 11 Nov 2011 at 6:09

[GoogleCodeExporter]

Is this fixed for good?

Original comment by dhruvb...@gmail.com on 21 Nov 2011 at 1:00

[GoogleCodeExporter]

Yes.

Original comment by anup.kal...@gmail.com on 21 Nov 2011 at 3:29

[GoogleCodeExporter]

Original comment by dhruvb...@gmail.com on 21 Nov 2011 at 4:27

• Changed state: Fixed