-
Bug
-
Resolution: Fixed
-
Major
-
Jenkins 1.473
JDK 1.6.0_26
The following thread dump (from one stuck slave) shows a deadlock between
pool-635-thread-1 and pool-635-thread-2
Looks like it is due to commons-logging used by maven wagon.
- is duplicated by
-
JENKINS-16757 Commons Logging 1.1.1 creates Deadlocks
-
- Resolved
-
the linked commons-logging issues has been resolved - https://issues.apache.org/jira/browse/LOGGING-119
also, apache have released version 1.2.1 of commons logging that includes this fix - http://commons.apache.org/proper/commons-logging/download_logging.cgi
so, in theory, nothing now stands in the way of upgrading jenkins' version of commons logging and resolving this issue?