This is not error, that is why it is printed as DEBUG. There is job heartbeat thread that runs regularly trying to pick up jobs from each VM queue. When there is already a currently active job running for that queue, this message will be printed.
Thanks -min On 10/15/14 12:58 PM, "Mo" <m...@daoenix.com> wrote: >My management log is being flooded with errors: > >2014-10-15 15:57:47,790 DEBUG [o.a.c.f.j.i.SyncQueueManagerImpl] >(AsyncJobMgr-Heartbeat-1:ctx-257021c2) Queue (queue id, sync type, sync >id) - (1,VmWorkJobQueue, 1) is reaching concurrency limit 1 >2014-10-15 15:57:47,792 DEBUG [o.a.c.f.j.i.SyncQueueManagerImpl] >(AsyncJobMgr-Heartbeat-1:ctx-257021c2) Queue (queue id, sync type, sync >id) - (43,VmWorkJobQueue, 11) is reaching concurrency limit 1 >2014-10-15 15:57:49,790 DEBUG [o.a.c.f.j.i.SyncQueueManagerImpl] >(AsyncJobMgr-Heartbeat-1:ctx-eaf952ad) Queue (queue id, sync type, sync >id) - (1,VmWorkJobQueue, 1) is reaching concurrency limit 1 >2014-10-15 15:57:49,792 DEBUG [o.a.c.f.j.i.SyncQueueManagerImpl] >(AsyncJobMgr-Heartbeat-1:ctx-eaf952ad) Queue (queue id, sync type, sync >id) - (43,VmWorkJobQueue, 11) is reaching concurrency limit 1 >2014-10-15 15:57:51,789 DEBUG [o.a.c.f.j.i.SyncQueueManagerImpl] >(AsyncJobMgr-Heartbeat-1:ctx-e5444b6a) Queue (queue id, sync type, sync >id) - (1,VmWorkJobQueue, 1) is reaching concurrency limit 1 >2014-10-15 15:57:51,790 DEBUG [o.a.c.f.j.i.SyncQueueManagerImpl] >(AsyncJobMgr-Heartbeat-1:ctx-e5444b6a) Queue (queue id, sync type, sync >id) - (43,VmWorkJobQueue, 11) is reaching concurrency limit 1 >2014-10-15 15:57:53,538 DEBUG >[c.c.n.r.VirtualNetworkApplianceManagerImpl] >(RouterStatusMonitor-1:ctx-3e5c7227) Found 0 routers to update status. >2014-10-15 15:57:53,540 DEBUG >[c.c.n.r.VirtualNetworkApplianceManagerImpl] >(RouterStatusMonitor-1:ctx-3e5c7227) Found 0 networks to update RvR >status. >2014-10-15 15:57:53,789 DEBUG [o.a.c.f.j.i.SyncQueueManagerImpl] >(AsyncJobMgr-Heartbeat-1:ctx-e2b67d52) Queue (queue id, sync type, sync >id) - (1,VmWorkJobQueue, 1) is reaching concurrency limit 1 >2014-10-15 15:57:53,791 DEBUG [o.a.c.f.j.i.SyncQueueManagerImpl] >(AsyncJobMgr-Heartbeat-1:ctx-e2b67d52) Queue (queue id, sync type, sync >id) - (43,VmWorkJobQueue, 11) is reaching concurrency limit 1 >2014-10-15 15:57:55,790 DEBUG [o.a.c.f.j.i.SyncQueueManagerImpl] >(AsyncJobMgr-Heartbeat-1:ctx-237104ea) Queue (queue id, sync type, sync >id) - (1,VmWorkJobQueue, 1) is reaching concurrency limit 1 >2014-10-15 15:57:55,792 DEBUG [o.a.c.f.j.i.SyncQueueManagerImpl] >(AsyncJobMgr-Heartbeat-1:ctx-237104ea) Queue (queue id, sync type, sync >id) - (43,VmWorkJobQueue, 11) is reaching concurrency limit 1 >2014-10-15 15:57:57,605 DEBUG [c.c.a.m.AgentManagerImpl] >(AgentManager-Handler-9:null) Ping from 1 >2014-10-15 15:57:57,606 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl] >(AgentManager-Handler-9:null) Process host VM state report from ping >process. host: 1 >2014-10-15 15:57:57,606 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl] >(AgentManager-Handler-9:null) Process VM state report. host: 1, number of >records in report: 0 >2014-10-15 15:57:57,607 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl] >(AgentManager-Handler-9:null) Done with process of VM state report. host: >1 >2014-10-15 15:57:57,789 DEBUG [o.a.c.f.j.i.SyncQueueManagerImpl] >(AsyncJobMgr-Heartbeat-1:ctx-7eec8962) Queue (queue id, sync type, sync >id) - (1,VmWorkJobQueue, 1) is reaching concurrency limit 1 >2014-10-15 15:57:57,791 DEBUG [o.a.c.f.j.i.SyncQueueManagerImpl] >(AsyncJobMgr-Heartbeat-1:ctx-7eec8962) Queue (queue id, sync type, sync >id) - (43,VmWorkJobQueue, 11) is reaching concurrency limit 1 >2014-10-15 15:57:59,790 DEBUG [o.a.c.f.j.i.SyncQueueManagerImpl] >(AsyncJobMgr-Heartbeat-1:ctx-51b59d97) Queue (queue id, sync type, sync >id) - (1,VmWorkJobQueue, 1) is reaching concurrency limit 1 >2014-10-15 15:57:59,791 DEBUG [o.a.c.f.j.i.SyncQueueManagerImpl] >(AsyncJobMgr-Heartbeat-1:ctx-51b59d97) Queue (queue id, sync type, sync >id) - (43,VmWorkJobQueue, 11) is reaching concurrency limit 1 > > >What exactly is it trying to tell me? From what I gather, it seems there >is a queue it¹s unable to process? > >// mo
