I knew I should have sat on that email a little longer! In case someone else is making the same mistake, no notification is sent to the remote side when a connection is closed, which is exactly why I needed to send the "quit" message to get it working (on both sides).
On Wed, Jun 1, 2011 at 7:33 PM, Shaun Senecal <[email protected]> wrote: > Is there some obvious reason why I wouldnt be able to close a UDP > connection on the server side? I have a small server that is streaming > audio, and when it finishes sending out the stream, I call > session.close(false). No exceptions are thrown, but the connection with the > client persists somehow. I've stepped through the close() call and I dont > notice anything out of place happening. If I send a "quit" message to the > client and have the client call session.close(false), then everything shuts > down as expected. Originally I thought that somehow a delayed message was > arriving somewhere and reopening the connection, but I have set breakpoints > in the sessionCreated() on both sides and it appears that no new session is > ever created. > > MINA v2.0.2 >
