When a datasource that targets a JDBC server is executing, it may be cancelled manually by a user or it may time out. In both scenarios, the job appears cancelled in the UI, but the job remains running in the background. Even a MID server restart does not free up the connection.

Steps to Reproduce


  1. Set up a data source that is targeting a JDBC server with a large data set and is using a MID server (SCCM 2012 Software as an example).
  2. From the data source record, perform a Load All Records query.
  3. Wait for the connection to be made and records begin to populate the import set table.
  4. Cancel the job.

From Progress Worker, the completion code on the job is be Cancelled, but tail the agent log of the MID server being used. Note that the JBDCProbe.<syd_id of data source> is still executing.

Restart the MID server and the job will restart from the beginning.

Go to ecc_queue.list and search for a record where: 

  • Agent = mid.server.<MID name>
  • Topic = JDBCProbe
  • Queue = output
  • State = processing

Set the State to processed and restart the MID. The job no longer executes.




  1. Stop the MID Server.
  2. Perform the following query on the ecc_queue table:


    • Agent = mid.server.<name of MID Server>
    • Topic = JDBCProbe
    • Queue = output
    • State != processed
    • Optional: Source = <sys_id of data source>

From this list view, right click on the column header and select Update All from the context menu.

  1. Set State = processed
  2. Click Update.
  3. Start up the MID Server.

If these steps do not resolve the issue, repeat the steps again and delete the files within the agent\work\monitors\ECCSender\output folder on the MID Server before starting it back up.

Related Problem: PRB607053

Seen In

Calgary Patch 1 Hot Fix 8
Calgary Patch 2 Hot Fix 5
Fuji Patch 7 Hot Fix 5

Fixed In


Associated Community Threads

There is no data to report.

Article Information

Last Updated:2017-04-17 17:59:50