Comment 3 for bug 1049537

My plan to fix this is: 1) get error messages right; 2) whenever possible, switch to use fixed version of jenkins.war (probably, as defined in config). The latter will require manual updates, but we will be sure that we're protected from other similar issues, like latest war broken/has incompatible changes, and will let all us to be sure we're on the same line with Jenkins version.