Also, if it’s easy to produce or available, having a small Java test program that triggers the failure would be very helpful.

On Dec 3, 2014, at 9:47 AM, Serge Monkewitz <[log in to unmask]> wrote:

Tatiana: forwarding to qserv-l, since I am taking today off to deal with family matters. I’ll take a look tomorrow if no-one else has any ideas.

For context - connecting to qserv via JDBC still fails, even after Jacek’s show variables fix (and fix for the fix).

Begin forwarded message:

From: Tatiana Goldina <[log in to unmask]>
Subject: Re: rebuilding QSERV
Date: December 2, 2014 at 4:02:08 PM PST
To: Serge Monkewitz <[log in to unmask]>

I am out of clues. I am still getting the same error when connecting through the JDBC driver.

jdbc:mysql://lsst-db1.ipac.caltech.edu:4040/LSST?user=qsmaster&dumpQueriesOnException=true&traceProtocol=true

trace is attached. I don't know how to debug it further.



Use REPLY-ALL to reply to list

To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1

<trace.txt>


The query works, if I enter it directly into mysql command line client…



Use REPLY-ALL to reply to list

To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1




Use REPLY-ALL to reply to list

To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1