This fixes bug of not decrementing activityAcount to 0
whenb encountering 'daily_limit_reachede'.

The clock thread may not wake up during the daily pause
and daily resume minute, and when it does not, the corresponding
wall clock action will be missed.

The fix is in checkout the time of operations every time the
clock thread wakes up.

There is no longer need for the clock to wake up in the middle of
a wall clock minute.  So we improved the user experience by waking
up this thread at the beginning of every minute.

There is no meaningful processing of launch_record_id, which
is really just a pass through back to portal.

Reason is due to premature terminating postback threads because
the serviceActivityCount is decremented erreously when updating
intermediate job statuses with portal.
Fix is in classifying job status as final or non-final.
As it is, all JobStatus in CommEngine are final; however,
derived classes may have non-final JobStatus.

Fixed by decrementing serviceActivityCount only by postJobStatus method.
Also jobs being scheduled are taken into considering when deciding
to advance broadcast state COMPLETED to ALLDONE.

CSV logger name as it appears in log4j.properties is "csv".