Why is there a separate spring context for each action (what have I configured wrong)?
AbstractSpringAction extends AbstractActionLifecycle and there will be a single instance processing all messages. There will be one instance for every action definition you have. But if you specify multiple comma separated process methods like in your example they will be processed by the same instance.
How to enable a single spring context for all of the actions (or one context per service)?
This is currently not possible but you can always create a feature request for something like this.
Ok, so for every action definition, there is a spring context.
My hibernate and c3p0 connection pool is defined in that same spring context configuration file, does this mean, that there is a separate connection pool and hibernate session for every action definition?