Demonstration of method caching bub

Here is a test case that demonstrates an error in JmxClient.lookupParamTypes. The error is in the code shown at the end of this comment. The assumption is that "operations" pertains to the method being invoked. It may not. 

The test case shows that each of the two method invocations tested, when invoked seperately work. When invoked together, the second invocation fails because it assumes the method operations of the first. 

Thank you for taking this into consideration. I really like your package, I just need to get around this issue. 


-------------------------- Error code shown below -------------------

private String[] lookupParamTypes(ObjectName objectName, String operName, Object[] params) throws JMException {
		checkClientConnected();
		if (operations == null) {
			try {
				operations = mbeanConn.getMBeanInfo(objectName).getOperations();
			} catch (Exception e) {
				throw createJmException("Cannot get attribute info from " + objectName, e);
			}
		}