[Jenkins ver. 1.420]
If a jobs tries to archive an inexisting artifact, the jenkins process uses 100% CPU forever, until we do a '/etc/init.d/jenkins stop'
The web interface can not anymore be used
The problem is not new in 1.420, but exists for a long time, already in hudson (I did actually never see any linux version not having this problem).
A significant information is that we have a huge workspace (up to 45G - we build distros with OpenEmbedded) shared between the jobs