Sometimes we experience the following problem: the job, configured to use the remove trigger plugin, is polling the remove job correctly, then a network problem occurs and the polling stops (at least judging from the logs) and after that, the job cannot be aborted, neither by plugin, nor by hand.
What I've found, the the code sets the connection timeout but it does not set the read timeout, which is by default -1/0 meaning infinite.
|Field||Original Value||New Value|
|Workflow||JNJira [ 169164 ]||JNJira + In-Review [ 183382 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Assignee||Maurice W. [ morficus ]||KaiHsiang Chang [ cashlalala ]|
|Resolution||Fixed [ 1 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|