You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Aniket Bhoi <an...@gmail.com> on 2015/01/30 16:01:52 UTC

JDBC Fails to connect to SQL Server

Hi,

I have Apache Solr hosted on Tomcat 6.

There have been no changes to the code on Tomcat whatsoever.However for the
last few days I now see this error in the Log files:

SEVERE: Full Import failed
Throwable occurred:
org.apache.solr.handler.dataimport.DataImportHandlerException: Unable to
execute query: SELECT ID, ENTRY_TYPE_REF, PROFILE_REF, ITEM_REF, TITLE,
ABSTRACT, SOLUTION, SOLUTION_HTML, FREE_TEXT, DATE_UPDATED, ENTRY_TYPE,
PROFILE_TYPE, SERVICE_TYPE FROM INFRA_KO_V Processing Document # 1
at
org.apache.solr.handler.dataimport.DataImportHandlerException.wrapAndThrow(DataImportHandlerException.java:72)
at
org.apache.solr.handler.dataimport.JdbcDataSource$ResultSetIterator.<init>(JdbcDataSource.java:251)
at
org.apache.solr.handler.dataimport.JdbcDataSource.getData(JdbcDataSource.java:208)
at
org.apache.solr.handler.dataimport.JdbcDataSource.getData(JdbcDataSource.java:39)
at
org.apache.solr.handler.dataimport.SqlEntityProcessor.initQuery(SqlEntityProcessor.java:58)
at
org.apache.solr.handler.dataimport.SqlEntityProcessor.nextRow(SqlEntityProcessor.java:71)
at
org.apache.solr.handler.dataimport.EntityProcessorWrapper.nextRow(EntityProcessorWrapper.java:233)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:579)
at
org.apache.solr.handler.dataimport.DocBuilder.doFullDump(DocBuilder.java:260)
at
org.apache.solr.handler.dataimport.DocBuilder.execute(DocBuilder.java:184)
at
org.apache.solr.handler.dataimport.DataImporter.doFullImport(DataImporter.java:334)
at
org.apache.solr.handler.dataimport.DataImporter.runCmd(DataImporter.java:392)
at
org.apache.solr.handler.dataimport.DataImporter$1.run(DataImporter.java:373)
*Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The driver
could not establish a secure connection to SQL Server by using Secure
Sockets Layer (SSL) encryption. Error: "SQL Server did not return a
response. The connection has been closed.".*
at
com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1368)
at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1412)
at
com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1058)
at
com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:833)
at
com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:716)
at
com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:841)
at
org.apache.solr.handler.dataimport.JdbcDataSource$1.call(JdbcDataSource.java:160)
at
org.apache.solr.handler.dataimport.JdbcDataSource$1.call(JdbcDataSource.java:127)
at
org.apache.solr.handler.dataimport.JdbcDataSource.getConnection(JdbcDataSource.java:361)
at
org.apache.solr.handler.dataimport.JdbcDataSource.access$200(JdbcDataSource.java:39)
at
org.apache.solr.handler.dataimport.JdbcDataSource$ResultSetIterator.<init>(JdbcDataSource.java:238)
... 11 more
*Caused by: java.io.IOException: SQL Server did not return a response. The
connection has been closed.*
at
com.microsoft.sqlserver.jdbc.TDSChannel$SSLHandshakeInputStream.ensureSSLPayload(IOBuffer.java:513)
at
com.microsoft.sqlserver.jdbc.TDSChannel$SSLHandshakeInputStream.readInternal(IOBuffer.java:570)
at
com.microsoft.sqlserver.jdbc.TDSChannel$SSLHandshakeInputStream.read(IOBuffer.java:562)
at
com.microsoft.sqlserver.jdbc.TDSChannel$ProxyInputStream.readInternal(IOBuffer.java:757)
at
com.microsoft.sqlserver.jdbc.TDSChannel$ProxyInputStream.read(IOBuffer.java:745)
at com.ibm.jsse2.b.a(b.java:286)
at com.ibm.jsse2.b.a(b.java:67)
at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:313)
at com.ibm.jsse2.SSLSocketImpl.h(SSLSocketImpl.java:63)
at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:316)
at com.ibm.jsse2.SSLSocketImpl.startHandshake(SSLSocketImpl.java:220)
at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1379)
... 20 more

I can confirmthat there has been no change to firewall settings etc .

Need help on this.

Regards
Aniket

Re: JDBC Fails to connect to SQL Server

Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Aniket,

On 2/2/15 3:09 AM, Aniket Bhoi wrote:
> On Fri, Jan 30, 2015 at 10:37 PM, Christopher Schultz < 
> chris@christopherschultz.net> wrote:
> 
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
>> 
>> Aniket,
>> 
>> On 1/30/15 10:01 AM, Aniket Bhoi wrote:
>>> I have Apache Solr hosted on Tomcat 6.
>>> 
>>> There have been no changes to the code on Tomcat
>>> whatsoever.However for the last few days I now see this error
>>> in the Log files:
>>> 
>>> SEVERE: Full Import failed Throwable occurred: 
>>> org.apache.solr.handler.dataimport.DataImportHandlerException: 
>>> Unable to execute query: SELECT ID, ENTRY_TYPE_REF,
>>> PROFILE_REF, ITEM_REF, TITLE, ABSTRACT, SOLUTION,
>>> SOLUTION_HTML, FREE_TEXT, DATE_UPDATED, ENTRY_TYPE,
>>> PROFILE_TYPE, SERVICE_TYPE FROM INFRA_KO_V Processing Document
>>> # 1
>>> 
>>> [snip]
>>> 
>>> *Caused by: com.microsoft.sqlserver.jdbc.SQLServerException:
>>> The driver could not establish a secure connection to SQL
>>> Server by using Secure Sockets Layer (SSL) encryption. Error:
>>> "SQL Server did not return a response. The connection has been
>>> closed.".* at
>>> 
>> com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1368)
>>>
>>>
>>
>> 
at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1412)
>> 
>> 
>> What does your <Resource> definition look like in either
>> server.xml or (better) context.xml?
>> 
>> - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment:
>> GPGTools - http://gpgtools.org
> 
> 
> 
> Thanks Jeff,
> 
> Let me check if there has been any such problem.
> 
> Hi Chris,
> 
> I do not have the resource configured in either context.xml or in 
> server.xml,its in Solr's data-config.xml,its picked up from there
> during data import.
> 
> <dataSource type="JdbcDataSource" 
> driver="com.microsoft.sqlserver.jdbc.SQLServerDriver" 
> url="jdbc:sqlserver://xxx-xxx:1433;databaseName=xxx" user="xxx" 
> password="xxx"/>

Then this has nothing to do with Tomcat: you are using Solr's
configuration with Microsoft's JDBC driver. You might get some help
here due to the general nature of connection pools, firewalls, etc.,
but this isn't a Tomcat problem.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJUz5PQAAoJEBzwKT+lPKRYd4UP/2Vajfe7n8bFGGWsIDTC0J5O
8o+xgf5Hfcp8oPVYcV0vXy1M1Ugb5cBSvDBOHpkCvCShR9wJXXyh/KFjA9amiM7A
D3Fn/LSumTDkjM/U/rOmiPBQfe5p+EBeDh8xEK7DV0O55cvJ2cgKWuNiRpU6uQ3a
elAxnPOyl4Ekv/pzrykFnKMsqQbzAyO7j+4EDwfAD9//bpM0QWeUHJwyA3h/r4aE
5zfasvfwa/ZnKx5teQeUy9bpYmIFwPshS+VH85Gc+D8x4yQ+Oq8U1cp9H3tKctDo
HBUqs/Of7UsqqWD8Jvkl3t/T7QZgJLbx56f6VCCykUYBerivpSI9oK/MZFtlK6Nv
TQPMs5u6TnDfFRLoogRER6C+xIJWXmJukb2WpoyDkhVZWEwnzvGnVyarXP7TNa9m
C0Wm/2xozTkziDWpkS1oJ1/nT4zWTqX6uR8415leQ0mU4V9g1gQUouap7Ja1WrRN
0FArAC+XcT3estl/nIIAT9P3zHVYq2TKs9FNMTJBCaHCfxu4SV/ZaZzJOEZiTe0d
wnTXIu4Vw6cdGGjpZjQPP3sDrCAX6pvukQX6IwOLmhjr0Kvo/OUoZslQdSLt48nL
r26yEA+7iLybqZvJ3SDB8XnpnQyvcuJXmpfQjqqy1blEKfXGhsaItdWP+5/ZBxDH
MUr2jmJ2WajRD+EhmROo
=yyhZ
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org

Re: JDBC Fails to connect to SQL Server

Posted by Aniket Bhoi <an...@gmail.com>.
On Fri, Jan 30, 2015 at 10:37 PM, Christopher Schultz <
chris@christopherschultz.net> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Aniket,
>
> On 1/30/15 10:01 AM, Aniket Bhoi wrote:
> > I have Apache Solr hosted on Tomcat 6.
> >
> > There have been no changes to the code on Tomcat whatsoever.However
> > for the last few days I now see this error in the Log files:
> >
> > SEVERE: Full Import failed Throwable occurred:
> > org.apache.solr.handler.dataimport.DataImportHandlerException:
> > Unable to execute query: SELECT ID, ENTRY_TYPE_REF, PROFILE_REF,
> > ITEM_REF, TITLE, ABSTRACT, SOLUTION, SOLUTION_HTML, FREE_TEXT,
> > DATE_UPDATED, ENTRY_TYPE, PROFILE_TYPE, SERVICE_TYPE FROM
> > INFRA_KO_V Processing Document # 1
> >
> > [snip]
> >
> > *Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The
> > driver could not establish a secure connection to SQL Server by
> > using Secure Sockets Layer (SSL) encryption. Error: "SQL Server did
> > not return a response. The connection has been closed.".* at
> >
> com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1368)
> >
> >
> at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1412)
>
>
> What does your <Resource> definition look like in either server.xml or
> (better) context.xml?
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> Comment: GPGTools - http://gpgtools.org



Thanks Jeff,

Let me check if there has been any such problem.

Hi Chris,

I do not have the resource configured in either context.xml or in
server.xml,its in Solr's data-config.xml,its picked up from there during
data import.

<dataSource type="JdbcDataSource"
driver="com.microsoft.sqlserver.jdbc.SQLServerDriver"
url="jdbc:sqlserver://xxx-xxx:1433;databaseName=xxx" user="xxx"
password="xxx"/>



-Aniket


>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

Re: JDBC Fails to connect to SQL Server

Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Aniket,

On 1/30/15 10:01 AM, Aniket Bhoi wrote:
> I have Apache Solr hosted on Tomcat 6.
> 
> There have been no changes to the code on Tomcat whatsoever.However
> for the last few days I now see this error in the Log files:
> 
> SEVERE: Full Import failed Throwable occurred: 
> org.apache.solr.handler.dataimport.DataImportHandlerException:
> Unable to execute query: SELECT ID, ENTRY_TYPE_REF, PROFILE_REF,
> ITEM_REF, TITLE, ABSTRACT, SOLUTION, SOLUTION_HTML, FREE_TEXT,
> DATE_UPDATED, ENTRY_TYPE, PROFILE_TYPE, SERVICE_TYPE FROM
> INFRA_KO_V Processing Document # 1
> 
> [snip]
> 
> *Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The
> driver could not establish a secure connection to SQL Server by
> using Secure Sockets Layer (SSL) encryption. Error: "SQL Server did
> not return a response. The connection has been closed.".* at 
> com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1368)
>
> 
at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1412)


What does your <Resource> definition look like in either server.xml or
(better) context.xml?

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJUy7o3AAoJEBzwKT+lPKRYYuIP/jxc0viCEoNKl+rXg5i7FrnZ
1LSYOevInM8aWB8Fm5gnzTJ0zv/VFAcNGUaqwrAcVNNy2P2o5J+Jb2RrODF3JvXP
HuCdwyOkSQLfEtFN4jtkhcjPL+54NVDFybVsDDY1/030X4wHgI7vB2upsdeAD5/H
Sa73iHE5K3sM6aUmoxrzQLcB3riokCDzuA1tqxcYDEugcJ+wcmvULd8oc2DNKh0V
hAa4S9vVR4Uy+x+C81gUVFYr62jghpHPajOdbF88Yryko8lhfASSvawMk0qKWLQ4
Tf0FY72Hcp7aW/bgVD44CUtvhjpY6j70QJCWE4rHq9/5T04fFPkYOZgxExj0GInX
6NfNb6JUDW88AkbpS3NXlxa6YZuyquQu42yyFZsze/jbpUrUfBXOjWD0JRQ9kHpe
XfjTNMOeeMmYLDLR86nMKuamUukwexFgpTLvdr/iCf0qtJUViBitVL5U8ALoAJdb
b0u/Wq93TXKP8TKh8gP1vWN0Sa29d7e/8W88cGWnHerugJRamGSGmFcbClOL/S77
+CMpzLsPo6w9lBMNp8i0nUkJYc+4VkkrVziS0rv6etUsCfaZw6k9W6hFW6QIq3vo
FcWpa5r5zFaTG+7NhIyvJmBykPUSBycHE5tDqGIMRHzNRsSWXCyRkTb9DMr0JJSy
IdXis+j60OPCTlFbBCkC
=+aqL
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org

Re: JDBC Fails to connect to SQL Server

Posted by Jeff Kohut <je...@gmail.com>.
On Fri, Jan 30, 2015 at 9:01 AM, Aniket Bhoi <an...@gmail.com> wrote:

> Hi,
>
> I have Apache Solr hosted on Tomcat 6.
>
> There have been no changes to the code on Tomcat whatsoever.However for the
> last few days I now see this error in the Log files:
>
> SEVERE: Full Import failed
> Throwable occurred:
> org.apache.solr.handler.dataimport.DataImportHandlerException: Unable to
> execute query: SELECT ID, ENTRY_TYPE_REF, PROFILE_REF, ITEM_REF, TITLE,
> ABSTRACT, SOLUTION, SOLUTION_HTML, FREE_TEXT, DATE_UPDATED, ENTRY_TYPE,
> PROFILE_TYPE, SERVICE_TYPE FROM INFRA_KO_V Processing Document # 1
> at
>
> org.apache.solr.handler.dataimport.DataImportHandlerException.wrapAndThrow(DataImportHandlerException.java:72)
> at
>
> org.apache.solr.handler.dataimport.JdbcDataSource$ResultSetIterator.<init>(JdbcDataSource.java:251)
> at
>
> org.apache.solr.handler.dataimport.JdbcDataSource.getData(JdbcDataSource.java:208)
> at
>
> org.apache.solr.handler.dataimport.JdbcDataSource.getData(JdbcDataSource.java:39)
> at
>
> org.apache.solr.handler.dataimport.SqlEntityProcessor.initQuery(SqlEntityProcessor.java:58)
> at
>
> org.apache.solr.handler.dataimport.SqlEntityProcessor.nextRow(SqlEntityProcessor.java:71)
> at
>
> org.apache.solr.handler.dataimport.EntityProcessorWrapper.nextRow(EntityProcessorWrapper.java:233)
> at
>
> org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:579)
> at
>
> org.apache.solr.handler.dataimport.DocBuilder.doFullDump(DocBuilder.java:260)
> at
> org.apache.solr.handler.dataimport.DocBuilder.execute(DocBuilder.java:184)
> at
>
> org.apache.solr.handler.dataimport.DataImporter.doFullImport(DataImporter.java:334)
> at
>
> org.apache.solr.handler.dataimport.DataImporter.runCmd(DataImporter.java:392)
> at
>
> org.apache.solr.handler.dataimport.DataImporter$1.run(DataImporter.java:373)
> *Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The driver
> could not establish a secure connection to SQL Server by using Secure
> Sockets Layer (SSL) encryption. Error: "SQL Server did not return a
> response. The connection has been closed.".*
> at
>
> com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1368)
> at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1412)
> at
>
> com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1058)
> at
>
> com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:833)
> at
>
> com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:716)
> at
>
> com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:841)
> at
>
> org.apache.solr.handler.dataimport.JdbcDataSource$1.call(JdbcDataSource.java:160)
> at
>
> org.apache.solr.handler.dataimport.JdbcDataSource$1.call(JdbcDataSource.java:127)
> at
>
> org.apache.solr.handler.dataimport.JdbcDataSource.getConnection(JdbcDataSource.java:361)
> at
>
> org.apache.solr.handler.dataimport.JdbcDataSource.access$200(JdbcDataSource.java:39)
> at
>
> org.apache.solr.handler.dataimport.JdbcDataSource$ResultSetIterator.<init>(JdbcDataSource.java:238)
> ... 11 more
> *Caused by: java.io.IOException: SQL Server did not return a response. The
> connection has been closed.*
> at
>
> com.microsoft.sqlserver.jdbc.TDSChannel$SSLHandshakeInputStream.ensureSSLPayload(IOBuffer.java:513)
> at
>
> com.microsoft.sqlserver.jdbc.TDSChannel$SSLHandshakeInputStream.readInternal(IOBuffer.java:570)
> at
>
> com.microsoft.sqlserver.jdbc.TDSChannel$SSLHandshakeInputStream.read(IOBuffer.java:562)
> at
>
> com.microsoft.sqlserver.jdbc.TDSChannel$ProxyInputStream.readInternal(IOBuffer.java:757)
> at
>
> com.microsoft.sqlserver.jdbc.TDSChannel$ProxyInputStream.read(IOBuffer.java:745)
> at com.ibm.jsse2.b.a(b.java:286)
> at com.ibm.jsse2.b.a(b.java:67)
> at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:313)
> at com.ibm.jsse2.SSLSocketImpl.h(SSLSocketImpl.java:63)
> at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:316)
> at com.ibm.jsse2.SSLSocketImpl.startHandshake(SSLSocketImpl.java:220)
> at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1379)
> ... 20 more
>
> I can confirmthat there has been no change to firewall settings etc .
>
> Need help on this.
>
> Regards
> Aniket
>

Assuming no changes on the calling side (Application/OS), is it possible
that the Windows MS SQL server has been recently patched and restarted.
There are periodic OS, security updates to Windows and sometimes they
involve Certificates (i.e. SSL). It could be that a previously allowed
Certificate is no longer working due to expiration, encryption length no
longer being sufficient, etc...