We have a backend webapp installed on tomcat 8 that has a GUI part written in Apache wicket MVC (version 1.4) - the wicket GUI fails to respond the moment the server starts doing heavy processing.
On average the CPU sits around 85% utilization. The page may refresh after a minute and may never return.
How can I give the wicket a higher priority, either in the code or the server settings to get it to respond under high load? I wouldn't mind it stealing CPU from the backend threads if needed.
Some clarification : the whole app is a single war, so the wicket and the "backend" threads run in the same jvm under the same webapp. The wicket page does not seem to need any important busy objects that the other threads uses.