When a @Service is exposed through a @Management interface and the management interface has overloaded methods, then there are chances of invoking an incorrect method. See the forum reference thread for details.

The ServiceMBeanDelegate maintains a Map of signature --> Method, but looks it up incorrectly

private Method getOperation(String actionName, String[] signature) throws ReflectionException
{
String opSig = getOperationSignature(actionName, signature);
Method operation = operations.get(actionName); // Incorrect lookup : should be looking up using opSig