Projects tagged ‘jdbc’ and ‘jmx’

The PoolMan library and JDBC2.0 Driver and DataSource provide a JMX-based, XML-configurable means of pooling and caching Java objects, as well as extensions for caching SQL queries and results across multiple databases.

Scriptella is an ETL (Extract-Transform-Load) and script execution tool. Its primary focus is simplicity. It doesn't require the user to learn another complex XML-based language to use it, but allows ... [More] the use of SQL or another scripting language suitable for the data source to perform required transformations. Main features: * Simple and minimalistic XML syntax for ETL scripts. * Built-in providers for JDBC, CSV, Text, XML, LDAP, Lucene and Velocity. * Support for many useful JDBC features, e.g. parameters in SQL including file blobs and JDBC escaping. * Easy-to-Use as a standalone tool or Ant task. No deployment/installation required. Easy-To-Run ETL files directly from Java code. * Seamless integration with Java/Java EE and Spring [Less]

Java Simon - Simple Monitoring API Java Simon is a simple monitoring API that allows you to follow and better understand your application. Monitors (familiarly called Simons) are placed directly ... [More] into your code and you can choose whether you want to count something or measure time/duration. Current version 2 provides basic monitor functionality, extensibility via Callbacks, JMX and Spring integration tools and also easy to use JDBC proxy driver that measures JDBC performance and can log all statements too. Version 2.1 was released on July 23rd, 2009. [Less]

JDBCSpy ObjectiveJDBCSpy aims to provide a lightweight means to obtain statistics at the JDBC driver level. StatusIt currently provides minimal statistics around JDBC Statements and ... [More] PreparedStatements but functionality is expected to improve over time. JDBCSpy has been tested using PostgreSQL and hsqldb but should more or less work with any configurable JDBC data source. The code is a work in progress (and likely will continue to be for the foreseeable future). It's an interesting little side project that has actually shown some utility in a couple of situations. DependenciesThere are no run-time dependencies. JDBCSpy (jdbcspy-core) has test-time dependencies on TestNG and hsqldb. See the installation instructions for information on getting started. Future PlansSupport for more Statement/PreparedStatement methods (currently only tracks executeQuery()) Provide a nice UI for statistics visualization (Currently in development) Recent Commits03/14/08Significant refactors around the viewing components (there have been a few commits over the last few month that haven't been accurately recorded on the project page). What: Introduced a common interface between GUI panels and the QueryStatistics they're displaying. Replaying a session from a JDBCSpy logfile should now work a little better. 01/03/08The result of some work performed during my pre-Christmas hack day. What: Updated to Surefire 2.4 and TestNG 5.7 Two new JDBCSpyMBean interface methods: mark() and getSQLExecutionTime(). mark() allows you to explicitly have a message logged getSQLExecutionTime() provides the number of milliseconds spent executing SQL since the last reset. Introduced new module: jdbcspy-testutil JDBCSpyListener provides framework hooks to track SQL execution during TestNG test cases. Provided an example callback implementation that generates an HTML report with test statistics. Updated UI panel to provide a mechanism to explicitly connect to a JDBCSpyMBean (host/port). mplemented a table panel that will display statistics about recently executed SQL. HACK QueriesPerSecondPanel now supports basic replay from a log file. 11/30/07Quick implementation of a properties object. The properties object should (fairly) generically handle JDBCSpy properties that have either been specified as System properties or as members of a 'jdbcspy.properties' file. See modules/jdbcspy-core/examples for jdbcspy.properties examples What: Added support for reading properties from a jdbcspy.properties file on the classpath Changed JDBCSpyDriver.class to JDBCSpyDriver.wrappedDriver 11/12/07Implemented automatic resets and file-based logging. What: Initial support for enabling / disabling statistics gathering. JDBCSpy can now optionally write queries to a file. New JDBCSpyDriver.logFile connection url parameter QueriesPerSecondPanel now periodically clears itself. [Less]

Java Simon - Simple Monitoring APIJava Simon is a simple monitoring API that allows you to follow and better understand your application. Monitors (familiarly called Simons) are placed directly into ... [More] your code and you can choose whether you want to count something or measure time/duration. NewsJuly 23rd, 2009 - Version 2.1This is a minor update of version 2 based on some user's input: added methods reset and two versions of sampleAndReset to SimonMXBean; you can now use [, ], and _ in Simon names; timestamps for 0 are formated as undef in toString methods. Download on the right side of the page, we also updated Javadoc for a few JMX classes - see JavaDoc for v2.1. We thank our users for their support and feedback! June 19th, 2009 - Version 2 out!After few more fixes, some simplifications (ever used StatProcessor? it's gone!), more Javadocs and some Wiki updates (with some more ahead) we have finally released version 2 of Java Simon library. You can choose the big package with precompiled JARs, Javadocs (here online) and working Ant build - or if you're Maven user, you can go for smaller sources-only ZIP with Maven build (Maven 2.1 is required). Check the right side of the page for both downloads. Enjoy - and tell us what you think! May 20th, 2009 - Version 2, Beta 2Yup, we're slower than we anticipated - especially because we really wanted to wrap it up faster for our own sake as well. This time the whole source structure is Maven 2 compliant and you should be able to compile the project and install all Java Simon artifacts into your repository. We still have to finish deployment to online repository and besides that there are some documentation tasks pending as well. May 6th, 2009 - Fighting with Maven 2 ;-)We are finishing second beta (check trunk if you're adventurous) with Maven 2 build. As the core developers are not familiar with Maven we have a problem to build the project properly with all dependencies (especially half of the JARs need JDK 5, the other JDK 6 ;-)). If you don't need Maven, simply download the first beta - final version is going to be very similar except for the project structure. API, JARs, features... we will not change this unless some vis major occasion. Older news: All news can be found here. News on this page (Google code) might be rephrased or shortened. ;-) DocumentationCheck out the list of our Wiki pages where you may also find: Introduction - where Java Simon API is positioned and the motivation for it GettingStarted - how to start with Java Simon along with some examples Callbacks - new important feature of v2 to extend Java Simon functions with your own code MavenSupport - for Maven 2 users Other resources: Javadocs for v2 About Java Simon - on javasimon.org Visit and join our mailing list on Google Groups: http://groups.google.com/group/javasimon Some part of the documentation relates to v1 which is not officially supported anymore (sounds strange but there are reasons for that). MotivationWe wanted to use something like JAMon for our products originally, but we lacked two important features: better way (or any way for that matter) to organize all those monitors; nanosecond resolution. Monitor hierarchySimon API gives you a better control over all those monitors in your big - possibly Java EE - application. Simons are organized in a hierarchy similar to what you can see in java.util.logging API. Simons can be disabled which minimizes their overhead influencing your application. These operations can be performed on the whole subtrees of Simons which makes partial application monitoring easier. See SimonHierarchy for more. The time for nanos is hereSimon measures times in nanos - and believe it or not it can make the difference on current very fast machines. Although not all platforms provide timers precise enough this design decision is future proof. Of course this decision comes with a price - you can use Java Simon only with JDK 1.5 or higher (platform Java SE 5). See SystemTimersGranularity page for more. Future plansOur future goals include (the later goals are in a more distant future): Sampling, collecting, agregating with persistence backend (file/DB). VisualVM plugin. Dynamic profiling integration. Currently the project is rather on hold - but this depends on other free-time activities of the authors and also on public demand and feedback. We're not preparing v3 right now, we're ready to tweak version 2 though. Do you have something to tell us?So tell us! Visit our Google Group (preferably) or file an issue, whatever. We can't promise to fulfill all your dreams but we want to produce the library YOU like (and so do we - of course ;-)). So if you know how to make Simon better, without making it something it is not, let us know! We want to know. [Less]