You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "Bomma, Nithun" <Ni...@amtrak.com> on 2016/02/01 17:55:04 UTC
com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset -
Errors
Hello,
We are using Tomcat 6.x for one of our application. It was working fine until today morning and all of sudden we tomcat application was not responding and was throwing below errors:
Feb 1, 2016 9:00:16 AM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
WARNING: ConnectionID:96869 Prelogin error: host MSSENTCLUSQL01P.amtrak.ad.nrpc port 1433 Error sending prelogin request: Connection reset
Caught exception com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
Feb 1, 2016 9:00:22 AM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
WARNING: ConnectionID:96899 Prelogin error: host MSSENTCLUSQL01P.amtrak.ad.nrpc port 1433 Error sending prelogin request: Connection reset
Caught exception com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
Feb 1, 2016 9:00:29 AM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
Caught exception com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
Caught exception com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
Caught exception com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
Caught exception com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
Caught exception com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
Feb 1, 2016 9:04:25 AM com.microsoft.sqlserver.jdbc.TDSChannel enableSSL
INFO: java.security path: /usr/java/jdk1.6.0_17/jre/lib/security
Security providers: [SUN version 1.6, SunRsaSign version 1.5, SunJSSE version 1.6, SunJCE version 1.6, SunJGSS version 1.0, SunSASL version 1.5, XMLDSig version 1.0, SunPCSC version 1.6]
SSLContext provider info: Sun JSSE provider(PKCS12, SunX509 key/trust factories, SSLv3, TLSv1)
SSLContext provider services:
[SunJSSE: KeyFactory.RSA -> sun.security.rsa.RSAKeyFactory
aliases: [1.2.840.113549.1.1, OID.1.2.840.113549.1.1]
, SunJSSE: KeyPairGenerator.RSA -> sun.security.rsa.RSAKeyPairGenerator
aliases: [1.2.840.113549.1.1, OID.1.2.840.113549.1.1]
, SunJSSE: Signature.MD2withRSA -> sun.security.rsa.RSASignature$MD2withRSA
aliases: [1.2.840.113549.1.1.2, OID.1.2.840.113549.1.1.2]
, SunJSSE: Signature.MD5withRSA -> sun.security.rsa.RSASignature$MD5withRSA
aliases: [1.2.840.113549.1.1.4, OID.1.2.840.113549.1.1.4]
, SunJSSE: Signature.SHA1withRSA -> sun.security.rsa.RSASignature$SHA1withRSA
aliases: [1.2.840.113549.1.1.5, OID.1.2.840.113549.1.1.5, 1.3.14.3.2.29, OID.1.3.14.3.2.29]
, SunJSSE: Signature.MD5andSHA1withRSA -> com.sun.net.ssl.internal.ssl.RSASignature
, SunJSSE: KeyManagerFactory.SunX509 -> com.sun.net.ssl.internal.ssl.KeyManagerFactoryImpl$SunX509
, SunJSSE: KeyManagerFactory.NewSunX509 -> com.sun.net.ssl.internal.ssl.KeyManagerFactoryImpl$X509
, SunJSSE: TrustManagerFactory.SunX509 -> com.sun.net.ssl.internal.ssl.TrustManagerFactoryImpl$SimpleFactory
, SunJSSE: TrustManagerFactory.PKIX -> com.sun.net.ssl.internal.ssl.TrustManagerFactoryImpl$PKIXFactory
aliases: [SunPKIX, X509, X.509]
, SunJSSE: SSLContext.SSL -> com.sun.net.ssl.internal.ssl.SSLContextImpl
, SunJSSE: SSLContext.SSLv3 -> com.sun.net.ssl.internal.ssl.SSLContextImpl
, SunJSSE: SSLContext.TLS -> com.sun.net.ssl.internal.ssl.SSLContextImpl
, SunJSSE: SSLContext.TLSv1 -> com.sun.net.ssl.internal.ssl.SSLContextImpl
, SunJSSE: SSLContext.Default -> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl
, SunJSSE: KeyStore.PKCS12 -> com.sun.net.ssl.internal.pkcs12.PKCS12KeyStore
]
java.ext.dirs: /usr/java/jdk1.6.0_17/jre/lib/ext:/usr/java/packages/lib/ext
Caught exception com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "Connection reset".
Feb 1, 2016 9:04:38 AM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
After 6 Minutes, we started getting OutOfmemory Errors.
SEVERE: Caught exception (java.lang.OutOfMemoryError: GC overhead limit exceeded) executing org.apache.jk.common.ChannelSocket$SocketAcceptor@a03fd6a, terminating thread
Caught exception org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object
Caught exception org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object
Caught exception org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object
Caught exception com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
Feb 1, 2016 9:11:29 AM com.microsoft.sqlserver.jdbc.TDSChannel enableSSL
Can you please me understand what caused this issue?
Thanks,
Nithun Bomma
Sr WebSphere Administrator
Amtrak - Information Technology (Operations)
Desk: 770-604-3514; Cell: 215-704-4981
Re: com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
- Errors
Posted by "André Warnier (tomcat)" <aw...@ice-sa.com>.
On 01.02.2016 18:16, Christopher Schultz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Nithin,
>
> On 2/1/16 11:55 AM, Bomma, Nithun wrote:
>> We are using Tomcat 6.x for one of our application. It was working
>> fine until today morning and all of sudden we tomcat application
>> was not responding and was throwing below errors:
>>
>>
>> Feb 1, 2016 9:00:16 AM
>> com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin WARNING:
>> ConnectionID:96869 Prelogin error: host
>> MSSENTCLUSQL01P.amtrak.ad.nrpc port 1433 Error sending prelogin
>> request: Connection reset Caught exception
>> com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
>> Feb 1, 2016 9:00:22 AM
>> com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin WARNING:
>> ConnectionID:96899 Prelogin error: host
>> MSSENTCLUSQL01P.amtrak.ad.nrpc port 1433 Error sending prelogin
>> request: Connection reset Caught exception
>> com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
>> Feb 1, 2016 9:00:29 AM org.apache.jk.common.ChannelSocket
>> processConnection WARNING: processCallbacks status 2
>>
>> Caught exception com.microsoft.sqlserver.jdbc.SQLServerException:
>> Connection reset Caught exception
>> com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
>> Caught exception com.microsoft.sqlserver.jdbc.SQLServerException:
>> Connection reset Caught exception
>> com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
>> Caught exception com.microsoft.sqlserver.jdbc.SQLServerException:
>> Connection reset Feb 1, 2016 9:04:25 AM
>> com.microsoft.sqlserver.jdbc.TDSChannel enableSSL INFO:
>> java.security path: /usr/java/jdk1.6.0_17/jre/lib/security Security
>> providers: [SUN version 1.6, SunRsaSign version 1.5, SunJSSE
>> version 1.6, SunJCE version 1.6, SunJGSS version 1.0, SunSASL
>> version 1.5, XMLDSig version 1.0, SunPCSC version 1.6] SSLContext
>> provider info: Sun JSSE provider(PKCS12, SunX509 key/trust
>> factories, SSLv3, TLSv1) SSLContext provider services: [SunJSSE:
>> KeyFactory.RSA -> sun.security.rsa.RSAKeyFactory aliases:
>> [1.2.840.113549.1.1, OID.1.2.840.113549.1.1] , SunJSSE:
>> KeyPairGenerator.RSA -> sun.security.rsa.RSAKeyPairGenerator
>> aliases: [1.2.840.113549.1.1, OID.1.2.840.113549.1.1] , SunJSSE:
>> Signature.MD2withRSA -> sun.security.rsa.RSASignature$MD2withRSA
>> aliases: [1.2.840.113549.1.1.2, OID.1.2.840.113549.1.1.2] ,
>> SunJSSE: Signature.MD5withRSA ->
>> sun.security.rsa.RSASignature$MD5withRSA aliases:
>> [1.2.840.113549.1.1.4, OID.1.2.840.113549.1.1.4] , SunJSSE:
>> Signature.SHA1withRSA -> sun.security.rsa.RSASignature$SHA1withRSA
>> aliases: [1.2.840.113549.1.1.5, OID.1.2.840.113549.1.1.5,
>> 1.3.14.3.2.29, OID.1.3.14.3.2.29] , SunJSSE:
>> Signature.MD5andSHA1withRSA ->
>> com.sun.net.ssl.internal.ssl.RSASignature , SunJSSE:
>> KeyManagerFactory.SunX509 ->
>> com.sun.net.ssl.internal.ssl.KeyManagerFactoryImpl$SunX509 ,
>> SunJSSE: KeyManagerFactory.NewSunX509 ->
>> com.sun.net.ssl.internal.ssl.KeyManagerFactoryImpl$X509 , SunJSSE:
>> TrustManagerFactory.SunX509 ->
>> com.sun.net.ssl.internal.ssl.TrustManagerFactoryImpl$SimpleFactory
>> , SunJSSE: TrustManagerFactory.PKIX ->
>> com.sun.net.ssl.internal.ssl.TrustManagerFactoryImpl$PKIXFactory
>> aliases: [SunPKIX, X509, X.509] , SunJSSE: SSLContext.SSL ->
>> com.sun.net.ssl.internal.ssl.SSLContextImpl , SunJSSE:
>> SSLContext.SSLv3 -> com.sun.net.ssl.internal.ssl.SSLContextImpl ,
>> SunJSSE: SSLContext.TLS ->
>> com.sun.net.ssl.internal.ssl.SSLContextImpl , SunJSSE:
>> SSLContext.TLSv1 -> com.sun.net.ssl.internal.ssl.SSLContextImpl ,
>> SunJSSE: SSLContext.Default ->
>> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl , SunJSSE:
>> KeyStore.PKCS12 -> com.sun.net.ssl.internal.pkcs12.PKCS12KeyStore
>> ] java.ext.dirs:
>> /usr/java/jdk1.6.0_17/jre/lib/ext:/usr/java/packages/lib/ext Caught
>> exception com.microsoft.sqlserver.jdbc.SQLServerException: The
>> driver could not establish a secure connection to SQL Server by
>> using Secure Sockets Layer (SSL) encryption. Error: "Connection
>> reset". Feb 1, 2016 9:04:38 AM org.apache.jk.common.ChannelSocket
>> processConnection WARNING: processCallbacks status 2
>
> No description of the underlying error. :(
>
> I would imagine someone finally disabled SSLv3 on the database server,
> so you have to use a higher protocol to connect to it?
>
>> After 6 Minutes, we started getting OutOfmemory Errors. SEVERE:
>> Caught exception (java.lang.OutOfMemoryError: GC overhead limit
>> exceeded) executing
>> org.apache.jk.common.ChannelSocket$SocketAcceptor@a03fd6a,
>> terminating thread Caught exception
>> org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot get a
>> connection, pool error Timeout waiting for idle object Caught
>> exception org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot
>> get a connection, pool error Timeout waiting for idle object Caught
>> exception org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot
>> get a connection, pool error Timeout waiting for idle object Caught
>> exception com.microsoft.sqlserver.jdbc.SQLServerException:
>> Connection reset
>
> Perhaps the SQL Server driver doesn't clean-up its resources when it
> gets a fatal connection error likethis.
>
> There's no Tomcat configuration that will help you, here. I think you
> have to talk to your database folks to find out what changed.
>
and if you want some further speculative guesswork, based on clues in your logfile above,
and drawing on my Hercule Poirot national heritage, I would suspect that you have some
kind of Windows Domain authentication mechanism configured, and that it is when this
mechanism tries to inituially connect to the Active Directory server that this all
happens.. (the name of said server is even mentioned above)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
- Errors
Posted by George Sexton <ge...@mhsoftware.com>.
On 2/1/2016 10:16 AM, Christopher Schultz wrote:
> processConnection WARNING: processCallbacks status 2
> No description of the underlying error. :(
>
> I would imagine someone finally disabled SSLv3 on the database server,
> so you have to use a higher protocol to connect to it?
+1
I've been working on upgrading an App that stopped working because the
web service provider disabled SSLv3. The client was using JDK 1.6.0_0
and it just didn't support TLS. The host machine's a mess because the
OpenSSL libs are so outdated that apt-get can't connect to repositories
to get files for upgrade.
Unfortunately for the client, when I tried running JDK 1.8, he got class
cast exceptions. I ended up going through a very painful process of
upgrading them to the current Hibernate/Spring versions so I could get
them to JDK 1.8.
--
George Sexton
*MH Software, Inc.*
Voice: 303 438 9585
http://www.mhsoftware.com
Re: com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
- Errors
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Nithin,
On 2/1/16 11:55 AM, Bomma, Nithun wrote:
> We are using Tomcat 6.x for one of our application. It was working
> fine until today morning and all of sudden we tomcat application
> was not responding and was throwing below errors:
>
>
> Feb 1, 2016 9:00:16 AM
> com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin WARNING:
> ConnectionID:96869 Prelogin error: host
> MSSENTCLUSQL01P.amtrak.ad.nrpc port 1433 Error sending prelogin
> request: Connection reset Caught exception
> com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
> Feb 1, 2016 9:00:22 AM
> com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin WARNING:
> ConnectionID:96899 Prelogin error: host
> MSSENTCLUSQL01P.amtrak.ad.nrpc port 1433 Error sending prelogin
> request: Connection reset Caught exception
> com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
> Feb 1, 2016 9:00:29 AM org.apache.jk.common.ChannelSocket
> processConnection WARNING: processCallbacks status 2
>
> Caught exception com.microsoft.sqlserver.jdbc.SQLServerException:
> Connection reset Caught exception
> com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
> Caught exception com.microsoft.sqlserver.jdbc.SQLServerException:
> Connection reset Caught exception
> com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
> Caught exception com.microsoft.sqlserver.jdbc.SQLServerException:
> Connection reset Feb 1, 2016 9:04:25 AM
> com.microsoft.sqlserver.jdbc.TDSChannel enableSSL INFO:
> java.security path: /usr/java/jdk1.6.0_17/jre/lib/security Security
> providers: [SUN version 1.6, SunRsaSign version 1.5, SunJSSE
> version 1.6, SunJCE version 1.6, SunJGSS version 1.0, SunSASL
> version 1.5, XMLDSig version 1.0, SunPCSC version 1.6] SSLContext
> provider info: Sun JSSE provider(PKCS12, SunX509 key/trust
> factories, SSLv3, TLSv1) SSLContext provider services: [SunJSSE:
> KeyFactory.RSA -> sun.security.rsa.RSAKeyFactory aliases:
> [1.2.840.113549.1.1, OID.1.2.840.113549.1.1] , SunJSSE:
> KeyPairGenerator.RSA -> sun.security.rsa.RSAKeyPairGenerator
> aliases: [1.2.840.113549.1.1, OID.1.2.840.113549.1.1] , SunJSSE:
> Signature.MD2withRSA -> sun.security.rsa.RSASignature$MD2withRSA
> aliases: [1.2.840.113549.1.1.2, OID.1.2.840.113549.1.1.2] ,
> SunJSSE: Signature.MD5withRSA ->
> sun.security.rsa.RSASignature$MD5withRSA aliases:
> [1.2.840.113549.1.1.4, OID.1.2.840.113549.1.1.4] , SunJSSE:
> Signature.SHA1withRSA -> sun.security.rsa.RSASignature$SHA1withRSA
> aliases: [1.2.840.113549.1.1.5, OID.1.2.840.113549.1.1.5,
> 1.3.14.3.2.29, OID.1.3.14.3.2.29] , SunJSSE:
> Signature.MD5andSHA1withRSA ->
> com.sun.net.ssl.internal.ssl.RSASignature , SunJSSE:
> KeyManagerFactory.SunX509 ->
> com.sun.net.ssl.internal.ssl.KeyManagerFactoryImpl$SunX509 ,
> SunJSSE: KeyManagerFactory.NewSunX509 ->
> com.sun.net.ssl.internal.ssl.KeyManagerFactoryImpl$X509 , SunJSSE:
> TrustManagerFactory.SunX509 ->
> com.sun.net.ssl.internal.ssl.TrustManagerFactoryImpl$SimpleFactory
> , SunJSSE: TrustManagerFactory.PKIX ->
> com.sun.net.ssl.internal.ssl.TrustManagerFactoryImpl$PKIXFactory
> aliases: [SunPKIX, X509, X.509] , SunJSSE: SSLContext.SSL ->
> com.sun.net.ssl.internal.ssl.SSLContextImpl , SunJSSE:
> SSLContext.SSLv3 -> com.sun.net.ssl.internal.ssl.SSLContextImpl ,
> SunJSSE: SSLContext.TLS ->
> com.sun.net.ssl.internal.ssl.SSLContextImpl , SunJSSE:
> SSLContext.TLSv1 -> com.sun.net.ssl.internal.ssl.SSLContextImpl ,
> SunJSSE: SSLContext.Default ->
> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl , SunJSSE:
> KeyStore.PKCS12 -> com.sun.net.ssl.internal.pkcs12.PKCS12KeyStore
> ] java.ext.dirs:
> /usr/java/jdk1.6.0_17/jre/lib/ext:/usr/java/packages/lib/ext Caught
> exception com.microsoft.sqlserver.jdbc.SQLServerException: The
> driver could not establish a secure connection to SQL Server by
> using Secure Sockets Layer (SSL) encryption. Error: "Connection
> reset". Feb 1, 2016 9:04:38 AM org.apache.jk.common.ChannelSocket
> processConnection WARNING: processCallbacks status 2
No description of the underlying error. :(
I would imagine someone finally disabled SSLv3 on the database server,
so you have to use a higher protocol to connect to it?
> After 6 Minutes, we started getting OutOfmemory Errors. SEVERE:
> Caught exception (java.lang.OutOfMemoryError: GC overhead limit
> exceeded) executing
> org.apache.jk.common.ChannelSocket$SocketAcceptor@a03fd6a,
> terminating thread Caught exception
> org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot get a
> connection, pool error Timeout waiting for idle object Caught
> exception org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot
> get a connection, pool error Timeout waiting for idle object Caught
> exception org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot
> get a connection, pool error Timeout waiting for idle object Caught
> exception com.microsoft.sqlserver.jdbc.SQLServerException:
> Connection reset
Perhaps the SQL Server driver doesn't clean-up its resources when it
gets a fatal connection error likethis.
There's no Tomcat configuration that will help you, here. I think you
have to talk to your database folks to find out what changed.
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlavktkACgkQ9CaO5/Lv0PCbfACfalL5s5zZwXw9XrTHLoMx3q9N
/nEAnizpUTz5GqBy2BD7nFUnY8gMWZ7f
=5aZY
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
- Errors
Posted by "André Warnier (tomcat)" <aw...@ice-sa.com>.
On 01.02.2016 17:55, Bomma, Nithun wrote:
> Hello,
>
> We are using Tomcat 6.x for one of our application. It was working fine until today morning and all of sudden we tomcat application was not responding and was throwing below errors:
>
>
> Feb 1, 2016 9:00:16 AM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
> WARNING: ConnectionID:96869 Prelogin error: host MSSENTCLUSQL01P.amtrak.ad.nrpc port 1433 Error sending prelogin request: Connection reset
> Caught exception com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
> Feb 1, 2016 9:00:22 AM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
> WARNING: ConnectionID:96899 Prelogin error: host MSSENTCLUSQL01P.amtrak.ad.nrpc port 1433 Error sending prelogin request: Connection reset
> Caught exception com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
> Feb 1, 2016 9:00:29 AM org.apache.jk.common.ChannelSocket processConnection
> WARNING: processCallbacks status 2
>
> Caught exception com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
> Caught exception com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
> Caught exception com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
> Caught exception com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
> Caught exception com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
> Feb 1, 2016 9:04:25 AM com.microsoft.sqlserver.jdbc.TDSChannel enableSSL
> INFO: java.security path: /usr/java/jdk1.6.0_17/jre/lib/security
> Security providers: [SUN version 1.6, SunRsaSign version 1.5, SunJSSE version 1.6, SunJCE version 1.6, SunJGSS version 1.0, SunSASL version 1.5, XMLDSig version 1.0, SunPCSC version 1.6]
> SSLContext provider info: Sun JSSE provider(PKCS12, SunX509 key/trust factories, SSLv3, TLSv1)
> SSLContext provider services:
> [SunJSSE: KeyFactory.RSA -> sun.security.rsa.RSAKeyFactory
> aliases: [1.2.840.113549.1.1, OID.1.2.840.113549.1.1]
> , SunJSSE: KeyPairGenerator.RSA -> sun.security.rsa.RSAKeyPairGenerator
> aliases: [1.2.840.113549.1.1, OID.1.2.840.113549.1.1]
> , SunJSSE: Signature.MD2withRSA -> sun.security.rsa.RSASignature$MD2withRSA
> aliases: [1.2.840.113549.1.1.2, OID.1.2.840.113549.1.1.2]
> , SunJSSE: Signature.MD5withRSA -> sun.security.rsa.RSASignature$MD5withRSA
> aliases: [1.2.840.113549.1.1.4, OID.1.2.840.113549.1.1.4]
> , SunJSSE: Signature.SHA1withRSA -> sun.security.rsa.RSASignature$SHA1withRSA
> aliases: [1.2.840.113549.1.1.5, OID.1.2.840.113549.1.1.5, 1.3.14.3.2.29, OID.1.3.14.3.2.29]
> , SunJSSE: Signature.MD5andSHA1withRSA -> com.sun.net.ssl.internal.ssl.RSASignature
> , SunJSSE: KeyManagerFactory.SunX509 -> com.sun.net.ssl.internal.ssl.KeyManagerFactoryImpl$SunX509
> , SunJSSE: KeyManagerFactory.NewSunX509 -> com.sun.net.ssl.internal.ssl.KeyManagerFactoryImpl$X509
> , SunJSSE: TrustManagerFactory.SunX509 -> com.sun.net.ssl.internal.ssl.TrustManagerFactoryImpl$SimpleFactory
> , SunJSSE: TrustManagerFactory.PKIX -> com.sun.net.ssl.internal.ssl.TrustManagerFactoryImpl$PKIXFactory
> aliases: [SunPKIX, X509, X.509]
> , SunJSSE: SSLContext.SSL -> com.sun.net.ssl.internal.ssl.SSLContextImpl
> , SunJSSE: SSLContext.SSLv3 -> com.sun.net.ssl.internal.ssl.SSLContextImpl
> , SunJSSE: SSLContext.TLS -> com.sun.net.ssl.internal.ssl.SSLContextImpl
> , SunJSSE: SSLContext.TLSv1 -> com.sun.net.ssl.internal.ssl.SSLContextImpl
> , SunJSSE: SSLContext.Default -> com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl
> , SunJSSE: KeyStore.PKCS12 -> com.sun.net.ssl.internal.pkcs12.PKCS12KeyStore
> ]
> java.ext.dirs: /usr/java/jdk1.6.0_17/jre/lib/ext:/usr/java/packages/lib/ext
> Caught exception com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "Connection reset".
> Feb 1, 2016 9:04:38 AM org.apache.jk.common.ChannelSocket processConnection
> WARNING: processCallbacks status 2
>
>
> After 6 Minutes, we started getting OutOfmemory Errors.
> SEVERE: Caught exception (java.lang.OutOfMemoryError: GC overhead limit exceeded) executing org.apache.jk.common.ChannelSocket$SocketAcceptor@a03fd6a, terminating thread
> Caught exception org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object
> Caught exception org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object
> Caught exception org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object
> Caught exception com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
>
> Feb 1, 2016 9:11:29 AM com.microsoft.sqlserver.jdbc.TDSChannel enableSSL
>
>
> Can you please me understand what caused this issue?
>
Maybe : from the looks of it, your tomcat uses some (non-tomcat) mechanism to connect to
an external Microsoft SQL Server, and that is not working (anymore).
It does not seem to have anything to do with Tomcat per se.
What happened after that looks very much like a death spiral into runaway memory
consumption and vain attempts by the JVM at reclaiming some badly needed memory, until it
gives up in despair...
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org