BAT Jobs Stuck in Pending

[refram]

I am using CUCM 7.1.5.  I started a simple BAT job to update a configuration on about 50 phones.  The job should have taken no more than 20 seconds to complete, but 15 minutes later it was still running.  I tried stopping the job and 30 minutes later it was still stopping.  Then I deleted the job.  Now when I start a job it gets stuck in the "Pending" state and never goes anywhere.  It behaves like there's a job still in queue, and I'm wondering if CUCM still thinks one is in there.

I restarted the AXL, Bulk, and TAPS services and it didn't help.  I also restarted the servers in the cluster.  Is there something I'm missing?  Is there a CLI command I can use to see what's going on?  A SQL command, maybe?

Thanks.

[ogencheva]

I had a similar issue when any new bat job will be stuck in “pending”. I had to restart tomcat service on publisher and it will run one job only and next job will be stuck in “pending” again. Rebooting publisher cleared this issue.