Rule Definition
It is wise to avoid creating lengthy and complex Action classes. If you start to embed too much logic in the Action class itself, you will begin to find the Action class hard to understand, maintain, and impossible to reuse. Rather than creating overly complex Action classes, it is generally a good practice to move most of the persistence, and "business logic" to a separate application layer. Cyclomatic Complexity equals the minimum number of tests to check the Action Class's behavior. High CC means more testing and higher risk of errors.

Remediation
Refactor your application architecture and move some of this logic to another conceptual layer; otherwise, you may be left with an inflexible application which can only be accessed in a web-application environment.

http://struts.apache.org/1.x/userGuide/building_controller.html