[NiLuJe]

As for the RAM/CPU usage, Java has a pretty specific memory handling, and, IIRC, on the PW, it sits nicely between 60 and 70MB, which is roughly 30% of the 250MB of RAM available, so that also looks okay.

And, by default, ps reports the average total CPU usage over the complete lifetime of a process (ie. it's not a snapshot on the cpu usage at the exact moment you ran ps), so, depending on how early after boot/framework boot you launch ps, since the framework pretty much sits at 100% CPU during boot, that might not be completely extraordinary either.

That said, the most common reason for the framework *really* looping at 100% cpu is an indexing loop. Check the logs to see if it's looping on a book (beside the usual compacting/cleanup tasks).