[ 
https://issues.apache.org/jira/browse/IGNITE-7335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16407815#comment-16407815
 ] 

ASF GitHub Bot commented on IGNITE-7335:
----------------------------------------

Github user tledkov-gridgain closed the pull request at:

    https://github.com/apache/ignite/pull/3339


> DatabaseMetaData getTables error
> --------------------------------
>
>                 Key: IGNITE-7335
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7335
>             Project: Ignite
>          Issue Type: Bug
>          Components: jdbc, sql
>    Affects Versions: 2.3
>         Environment: Default ignite cluster with a table created via SQL from 
> the JDBC driver
>            Reporter: Maxwell Pettit
>            Assignee: Taras Ledkov
>            Priority: Major
>             Fix For: 2.5
>
>
> Exception when calling the java.sql.DatabaseMetaData.getTables(String 
> catalog, String schemaPattern, String tableNamePattern, String[] types) 
> method.  Exception is listed below:
> Caused by: java.sql.SQLException: Failed to communicate with Ignite cluster.
>       at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:681)
>       at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinDatabaseMetadata.getTables(JdbcThinDatabaseMetadata.java:740)
>       at 
> org.apache.commons.dbcp.DelegatingDatabaseMetaData.getTables(DelegatingDatabaseMetaData.java:604)
>       ... 20 more
> Caused by: java.io.IOException: Failed to read incoming message (not enough 
> data).
>       at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.read(JdbcThinTcpIo.java:406)
>       at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.read(JdbcThinTcpIo.java:384)
>       at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinTcpIo.sendRequest(JdbcThinTcpIo.java:327)
>       at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:668)
>       ... 26 more



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to