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".

Achieved by adding the isBroadcastFatal method to Job class.

Thie allows for removal of entries from the original enum JobStatus that more
appropriately belong to derivation of CommEngine.  Such data complicates
the management of the original JobStateus when adding new CommEngines.
These entries can be declared in a new enums implementing
the JobStatus interface, for each derived CommEngine.

Use reason field in Broadcast to record reason for pause, cancel etc.

Improved reponse text to pause and resume commands.

The service threads do not terminate immediately, but, instead
each service thread picks up one more job before terminating,
causing servicing more jobs which are not reported back to portal.

This happens when all remaining jobs are being serviced by
service threads when PAUSE is initiated.  Similarly fixed
for CANCEL.

before progressing to COMPLETED state and issue state change
notification to portal.

Also make state change report to be a single line for ease
of grep'ing log file.

in broadcast status message from CommEngine to portal.

rather than periodically on schedule.  This change has
no impact on user experience, and has improved logic,
and slight improvement in performance.

Also made all changes to the broadcasts structure under
synchronized control.

The common portion of the CommEngine properties file, are made
available to Broadcasts.

Broadcast state ALLDONE added to mark the event of completing postback,
and when all threads are to be terminated.

CommEngine report of a broadcast adds service times,
and number of transactions.

Broadcasts should determine their own service thread pool size.

This would lead to memory leak when SMSEngine is shutdown.