Daniel Glöckner

Hi, can someone from the core Calcite team please comment what is needed to have this PR merged? I'm happy to help. From my pov this bug hinders the adoption...

Let's see if I find time to support the project.

I've checked out how a JMX client can subscribe to JMX notifications. The subscriber needs to - know the name of the JMX bean wich he wants to subscribe to...

The listener interface contains only one method header: `public void handleNotification(Notification notification, Object handback);` AttributeChangeNotification is a sub class of Notification and it > Provides definitions of the attribute change...

Short example for a subscriber which dumps all AttributeChangeNotifications to stdout. ``` package com.example.notifications; import javax.management.*; import javax.management.remote.JMXConnector; import javax.management.remote.JMXConnectorFactory; import javax.management.remote.JMXServiceURL; public class Subscriber implements NotificationListener { private final...

Hi, I've just pushed a commit where I changed my design to use pushing instead of polling. Here's how it works: - when a new JMX connection is created for...

@gquintana @gehel I appreciate if you could have a look at my questions posted after the latest commit :)

@gehel I've just pushed a major change. There's now an explicit object pool which handles a notification processor per server-query tuple. A notification processor has a private JMX connection so...

I'm sure there are more reviews for "cosmetic" changes. I hope we get closer to the final design now and than the fine tuning can start.

Here's the gist of the re-design: ```Java public void subscribeToNotifications(final Server server) throws Exception { NotificationProcessor processor = null; ServerQuery serverQuery = new ServerQuery(server, this); try { processor = notificationProcessors.borrowObject(serverQuery);...