These may be fixable by adding more time to the tests' pom.xml files (if 
it's a simple timeout due to network connectivity or some other process 
that takes longer on Jenkins than when you build locally) or else you 
might need to check for blocking UI or threads (in which case, no 
additional time will help as it's a flaw in the test).

Note that for jobs that fail due to overall job timeout (server, 
javaee), I've doubled the timeout to 6hrs (360 mins).

But really, should your component take more than 3hrs to build & run 
tests? Maybe some of those long-running tests should be moved to the 
integration tests project?