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 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
-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,
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.SQLServer
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:96
> The solution was to 1) set acceptCount to a higher value in Tomcat and 2) to
> configure my OS to allow applications to specify longer accept queues. That
> last step was the one missing. I had changed acceptCount before, but since
> the OS was limiting the accept queue length I did not see an
Dear All,
Well, I managed to track this down. As it turned out, the problem was that I
had a rather short TCP listen queue on the Tomcat connector port (100 elements)
and that queue was overflowing.
The solution was to 1) set acceptCount to a higher value in Tomcat and 2) to
configure my OS to
Dear André,
Took me a while to answer, because I wanted to get more precise readings.
>>> Assuming that your client is really connecting to that HTTP connector on
>>> port 8080 mentioned above..
>> Yes, it has a forwarded port 80 (using FreeBSD ipfw) that also points to
>> 8080, and there is an
Kees Jan Koster wrote:
Dear André,
Assuming that your client is really connecting to that HTTP connector on port
8080 mentioned above..
Yes, it has a forwarded port 80 (using FreeBSD ipfw) that also points to 8080,
and there is an Apache with mod_proxy_http that hooks into 8081. My tests ar
Dear André,
> Assuming that your client is really connecting to that HTTP connector on port
> 8080 mentioned above..
Yes, it has a forwarded port 80 (using FreeBSD ipfw) that also points to 8080,
and there is an Apache with mod_proxy_http that hooks into 8081. My tests are
on the vanilla port,
Dear Jose,
>> Yes I am. In finally{} block. Here is the client code:
>
> Calling the disconnect() method of HttpURLConnection may close the
> underlying socket
> if a persistent connection is otherwise idle at that time
> Try don't call it, test it and tell us :-)
>
> http://docs.oracle.com/jav
> Yes I am. In finally{} block. Here is the client code:
Calling the disconnect() method of HttpURLConnection may close the
underlying socket
if a persistent connection is otherwise idle at that time
Try don't call it, test it and tell us :-)
http://docs.oracle.com/javase/1.5.0/docs/guide/net/ht
Kees Jan Koster wrote:
Dear Tomcat community,
I am trying to resolve the problem where some client code in Java frequently
gets the following error in the logs:
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at java.io.
Dear Jose,
> 2012/5/22 Kees Jan Koster :
>> Dear Tomcat community,
>>
>> I am trying to resolve the problem where some client code in Java frequently
>> gets the following error in the logs:
>>
>> java.net.SocketException: Connection reset
>>at java.net.SocketInputStream.read(SocketInpu
2012/5/22 Kees Jan Koster :
> Dear Tomcat community,
>
> I am trying to resolve the problem where some client code in Java frequently
> gets the following error in the logs:
>
> java.net.SocketException: Connection reset
> at java.net.SocketInputStream.read(SocketInputStream.java:168)
>
Dear Tomcat community,
I am trying to resolve the problem where some client code in Java frequently
gets the following error in the logs:
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at java.io.BufferedInputStream.fill(
16 matches
Mail list logo
