The autoDJ should never be "kicked" using ShoutCast's "kick source" feature.  Doing so causes the ShoutCast server to forcibly disconnect the streaming source, which in turn causes the streaming source to exit when it cannot reconnect.

This has a number of negative side-effects:

1. This is interpreted by Centova Cast's monitoring as an unexpected source outage (which is correct, because it is indistinguishable from a crash), so the administrator and the stream owner will be notified via E-mail of a stream outage.
2. Centova Cast will only periodically attempt to restart the autoDJ to recover from the perceived outage.  These attempts will fail during the live broadcast and be interpreted as further problems with the server.
3. Note that this autoDJ restart feature is NOT intended to be relied upon to reconnect the autoDJ after a live broadcast -- it is intended to ensure that the stream doesn't stay offline for an extended period of time if the autoDJ software crashes.  The reconnection period cannot be fine-tuned with a granularity suitable for reconnection after a live broadcast.
4. Because the source will repeatedly and unsuccessfully attempt to reconnect to the server, your logs will be polluted with error messages from the streaming source.
5. In some cases, the the kicked source will remain running in the background, and prevent proper control of the autoDJ.  See the heading regarding "Source status: Remote" below for more information

Your DJs should always stop the autoDJ before broadcasting live, and restart the autoDJ when their broadcast is complete.  This is explained in the following article:
Stopping/starting the autoDJ before/after streaming live

Find the original article at https://secure.centova.com/pages/faqs/display/kicking_the_autodj_103