#38 Reply.getNextReply locks up the thread

[beep@tomoton]

After experimenting with the Bing profile, in a test
scenario charting the post-failure behaviour of the the
most recent Java BeepCore implementation, a thread
could be locked in a wait state without any opportunity
for other threads to notify it to continue.

The thread cannot be notified because it's the only
thread left 'running' inside the VM.

The problem occurs when during the EchoProfile session,
one of the peer's cables become unplugged.

The blocking wait is invoked inside the reply object in
the method getNextReply.

As this is a connection-oriented protocol, the Reply
object should be kept informed about the life-cycle of
the associated channel. Currently, it would appear it
doesn't.