CPU usage too high while running Ruta Script

around this issue The problem seems to lie in the fact that you're adding an ActionListener every time you switch scenes. The previous ActionListener is never going away, but you're stacking more on top of it that do the same thing. Each one performs the same action, so when you press to switch scene, all the ActionListners that it now has will also go to switch scene. Your CPU will go up because there's now 2^n ActionListeners waiting for input and there's that many sitting in memory.

it should still fix some issue This problem is most likely caused by the fact that the JCas classes are overwritten. UIMA Ruta provides a few JCas classes of the types defined for seeding, inference and additional analysis engines. One of them (at least, but most important) contains additional methods for storing information about annotations and more: RutaBasic. These JCas classes must not be overwritten.
There is a mention in the README for users that apply JCasGenPomFriendly:

If you use the uimaFIT JCasGenPomFriendly in Maven and want to use UIMA Ruta 
as a standalone annotator you have to exclude the generated UIMA Ruta basic 
type files from the build, e.g., by adding:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-compiler-plugin</artifactId>
  <version>3.0</version>
  <configuration>
     <excludes>
         <exclude>org/apache/uima/ruta/type/*.java</exclude>
     </excludes>
  </configuration>
</plugin> 

will help you I've solve the problem. The problem was my antivirus program. I uninstalled it and the usage is the whole day 0-1%.

Does that help As it turned out, my issue was that several jobs had thousands of old builds. This was fine in Jenkins 1.6 but it's a problem in 2.5 (I guess maybe Jenkins tries to load all the builds into memory when you view the job overview page). To fix it, I just deleted most of the old builds from the problem jobs using this strategy and then reloaded jenkins. Worked like a charm!
I also set the "discard old builds" plugin to keep only the 50 most recent builds, to prevent this from happening again.

should help you out The TreeTaggerPosLemmaTT4J was renamed to TreeTaggerPosTagger.
See also the DKPro Core 1.7.0 component list.