Hi Jeff,
You are rigth. When moving jars's configuration and resources have to
move, too. But as others pointed out analysation of the mem usage is by
far more important. Maybe buying some mem for a couple of dollars and
forget about the shared class loader at all is a better and less hair
definitely a thread dump is required (see jstack.exe).
a) in case one CPU core is running at 100% and all others are
considerably more or less idle it might be a garbage collection issue,
too (enable GC logging or attach from JConsole to your process)
b) a long time ago we had an issue with
