check JMX bean registration through platformMBeanServer
check JMX bean registration through platformMBeanServer
add external initialization to concurrency test to validate problem of missing JMX Bean after multi thread initialization of InApplicationMonitor
report with more details, if handler is HandlerMethod
default initialization does not initialize JMX stuff any more, as handling creation of JMX Bean multithreaded would be a mess, thus we do not allow more than one JMX Bean in the vm.
add some synchronization to prevent multithreading issues
add spring webflow to allow reporting of more details in MonitoringHandlerInterceptor
throw an exception if JMXConnector is allready initialized, as otherwise this may lead to crazy multithreading problems
fix test to work correctly with new stricter JMX Bean Handling
less logging
test to verify that explicit initialization will keep allready registered values
expose putIfAbsent method for use in syncing
change explicit initialization from creating a new instance to replacing core plugin and KeyHandler in existing instance