Cause

The JRocket VM seems to load classes differently than the Sun JVM by more eagerly loading classes that aren't meant to be loaded. Velocity-related classes, such as the one used by the VelocityManager class that is the ultimate cause of this exception, should only be loaded lazily, as Velocity is officially an optional dependency for Struts. JRocket seems to trigger the loading earlier on startup.

Workaround

Add the Velocity jars in your application's classpath and the problem will go away. If you are using Maven 2, insert the following XML into your POM: