Re: How do I determine a library mismatch between jdbc client and server?

2016-09-28 Thread Stephen Sprague
you might just end up using your own heuristics.  if the port is "alive"
(ie. you can list it via netstat or telnet to it) but you can't connect...
then you got yourself a problem.

kinda like a bootstrapping problem, eh? you need to connect to get the
version but you can't connect if you don't have the right version.

my 2 cents.

On Wed, Sep 28, 2016 at 4:13 PM, Bear Giles  wrote:

> Hi, I'm trying to do development in an environment where we have a mixed
> bag of clusters. Some Cloudera, some Hortonworks, different versions of
> each, etc.
>
> (I don't know if we'll see this mix in the field but we need the variety
> for testing our software.)
>
> Sometimes the poor overworked developer (cough) grabs the wrong jars for
> the server. In at least one case there was no indication of what the
> problem was - all I saw was a connection timeout. That caused some
> confusion since mismatched jars was pretty far down my list of likely
> causes for that error.
>
> Is there a standard way to query for the remote version before trying to
> establish a JDBC connection? I know that I can check the Connection's
> DatabaseMetaData information once I've established a connection but that
> doesn't help me when I'm getting nothing but a timeout exception.
>
>
>
> Bear Giles
>
> Sr. Java Application Engineer
> bgi...@snaplogic.com
> Mobile: 720-354-0766
> SnapLogic.com  | We're Hiring
> !
> 
> 
>   
>   
> 
>
>
>
> 
>
> SnapLogic Inc | 929 Pearl St #200 | Boulder | 80302 | Colorado
>
> SnapLogic Inc | 2 W Fifth Avenue Fourth Floor | San Mateo | 94402 |
> California
>
> This message is confidential. It may also be privileged or otherwise
> protected by work product immunity or other legal rules. If you have
> received it by mistake, please let us know by e-mail reply and delete it
> from your system; you may not copy this message or disclose its contents to
> anyone. The integrity and security of this message cannot be guaranteed on
> the Internet.
>


How do I determine a library mismatch between jdbc client and server?

2016-09-28 Thread Bear Giles
Hi, I'm trying to do development in an environment where we have a mixed
bag of clusters. Some Cloudera, some Hortonworks, different versions of
each, etc.

(I don't know if we'll see this mix in the field but we need the variety
for testing our software.)

Sometimes the poor overworked developer (cough) grabs the wrong jars for
the server. In at least one case there was no indication of what the
problem was - all I saw was a connection timeout. That caused some
confusion since mismatched jars was pretty far down my list of likely
causes for that error.

Is there a standard way to query for the remote version before trying to
establish a JDBC connection? I know that I can check the Connection's
DatabaseMetaData information once I've established a connection but that
doesn't help me when I'm getting nothing but a timeout exception.



Bear Giles

Sr. Java Application Engineer
bgi...@snaplogic.com
Mobile: 720-354-0766
SnapLogic.com  | We're Hiring
!


  
  






SnapLogic Inc | 929 Pearl St #200 | Boulder | 80302 | Colorado

SnapLogic Inc | 2 W Fifth Avenue Fourth Floor | San Mateo | 94402 |
California

This message is confidential. It may also be privileged or otherwise
protected by work product immunity or other legal rules. If you have
received it by mistake, please let us know by e-mail reply and delete it
from your system; you may not copy this message or disclose its contents to
anyone. The integrity and security of this message cannot be guaranteed on
the Internet.