Hi Cheng,

The issue is that your JDBC connection is generating a version string that
has a character zero (0x0) in it, and postgresql doesn't allow that.

You get to specify the version string query as part of the job definition
-- can you look at that and see how you are getting this back?  It might be
due to the JDBC driver doing something funny, or it might be that your
supplied version query is querying for something that's really binary, and
you'll need to do something different to make it work.

Thanks,
Karl
On Wed, Mar 8, 2017 at 10:43 AM, Cheng Zeng <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB