timing issue with asynch results procssing

If the first results are sent to the client before the nonblockingrowprocessor is attached as a completionlistener, then the client may effectively drop results and throw an AsynchPositioningException. This was seen with TestAsynch.testAsynchContinuousEmpty since effectively no processing is performed.