Skip to main content
H
htran-2115-Moonstone
15-Moonstone
December 4, 2019
Question

Why TransferExecutor rejected a FileCopyTask sometimes?

  • December 4, 2019
  • 1 reply
  • 795 views

Hi,

 

I wonder why the TransferExecutor sometimes rejected a FileCopyTask when active threads are still less than pool size

 

 

JavaException: java.util.concurrent.RejectedExecutionException: Task com.thingworx.system.subsystems.filetransfer.engine.FileCopyTask@659cadf7 rejected from com.thingworx.system.subsystems.filetransfer.engine.TransferExecutor@1d58682b[Running, pool size = 50, active threads = 16, queued tasks = 1, completed tasks = 100193]

...

JavaException: java.util.concurrent.RejectedExecutionException: Task com.thingworx.system.subsystems.filetransfer.engine.FileCopyTask@75ec5668 rejected from com.thingworx.system.subsystems.filetransfer.engine.TransferExecutor@1d58682b[Running, pool size = 50, active threads = 0, queued tasks = 0, completed tasks = 101136]

 

 

 

 

{
 "async": false,
 "sourceRepo": "DEVICE_225016",
 "targetRepo": "ABCD",
 "targetFile": "test225016.txt",
 "targetPath": "/",
 "sourceFile": "test.txt",
 "sourcePath": "/ABCD",
 "timeout": 600
}

 

 

Any comment would be highly appreciated.

My Bests,

Hung Tran

1 reply

H
htran-2115-MoonstoneAuthor
15-Moonstone
December 9, 2019

Hi,

 

There were 188 such errors, transfer tasks were rejected when active threads was just 3

 

 

JavaException: java.util.concurrent.RejectedExecutionException: Task com.thingworx.system.subsystems.filetransfer.engine.FileCopyTask@45c855fc rejected from com.thingworx.system.subsystems.filetransfer.engine.TransferExecutor@11865eb9[Running, pool size = 100, active threads = 3, queued tasks = 1, completed tasks = 691071]

 

 

My Bests,

Hung Tran

Terms & ConditionsAccessibility statement