192 symposiums and 29,850 attendees since 2001

Vladimir Vivien

Software Engineer / Consultant

Vladimir Vivien
Vladimir Vivien is a software engineer living in the United States. Past and current experiences include development in Java and C#.Net for industries including publishing, financial, and healthcare. Vladimir enjoys taking part in open source projects. He is a contributor on Groovy project (he is the creator of JmxBuilder) and author of other project such as JmxLogger (http://code.google.com/p/jmx-logger/). Vladimir runs the Tampa Java User Group (Tampa, FL).

He has a wide range of technology interests including Java, OSGi, Groovy/Grails, JavaFX, SunSPOT, BugLabs, and anything else that runs on the JVM. He thinks the future direction of the Java platform is hidden in languages such as Groovy and Scala.

Blog

Google Buys On2. JavaFX Gains?

Posted Wednesday, August 5, 2009

When Google purchased YouTube back in 2006, the Flash video (FLV) format got an astronomical boots almost overnight. The media format became even more popular, the Flash/Flex pair gained notoriety as a viable platform, Adobe fortified its arsenals in th more »

NetBeans 6.7.1 + Mac OS = Sweetness

Posted Thursday, July 30, 2009

I just updated my netbeans to 6.7.x on the Mac and the difference is vivid more »

Introducing JmxLogger - Real-time Application Log Monitoring with JMX

Posted Sunday, April 12, 2009

For past month, I have been working (on/off) on JmxLogger, a logging API which lets you monitor your Java Logging or Log4J application log events in real-time using JMX. I have had the idea for a while, but decided to finally capture it as project. So, more »
Read More Blog Entries »

Presentations

Scripting Your Way to Management with JMX and Groovy

This presentation is about JMX and Groovy. It shows how easy it is to insert runtime manageability into your application when you combine the JMX API with the flexibility of the Groovy scripting language. The Java Management Extension (JMX) provides the i more »

Scripting Your Way to Management with JMX and Groovy

close

Vladimir Vivien By Vladimir Vivien

This presentation is about JMX and Groovy. It shows how easy it is to insert runtime manageability into your application when you combine the JMX API with the flexibility of the Groovy scripting language. The Java Management Extension (JMX) provides the infrastructural layer for runtime management while Groovy provides the syntactical substrate in which you can readily express class instrumentation for management. The presentation takes an exploratory look at how Groovy can help script JMX and its constituencies including interacting with the MBean Server, exposing MBeans, using the Server Connector API, and sending JMX events to registered listeners.



Starting with the Java 5 programming language, it has gotten easier to incorporate monitoring and manageability into any application running on a standard VM. Developers now have access to a wealth of runtime profiling information exposed through Java Management Extensions (JMX), including memory consumption, garbage collection, and thread activities (and JSR77-compliant app servers expose standard enterprise management components). Using JMX API and the scripting power of Groovy, developer can easily inject runtime management and control capabilities into their own applications.

This presentation is about JMX and Groovy. It shows how easy it is to insert runtime manageability into your application when you combine the JMX API with the flexibility of the Groovy scripting language. The Java Management Extension (JMX) provides the infrastructural layer for runtime management while Groovy provides the syntactical substrate in which you can readily express class instrumentation for management. The presentation takes an exploratory look at how Groovy can help script the different JMX constituencies including interacting with the MBean Server, exposing MBeans, using the Server Connector API, and sending JMX events to registered listeners. The presentation includes several examples including applications that can react to JMX events. Of course, wherever there's Groovy, there must be Grails. You will see a practical application of management scripting applied to a demo Grails application.