Fix ordering of state change in server

It was possible for an entire noop-grab_job-job_assign cycle to
happen between before the wakeConnections method set the connection
state to AWAKE.  Set it first before sending the NOOP packet.

Change-Id: I0d2170b6c583d95a44e289eca19611d11f93c6fd
Merge "Fix ordering of state change in server"