Hi,

The problem seems to have disappeared - looks like it was a 'load' related 
issue.

Thanks,
Chris

-----Original Message-----
From: Mark Claassen [mailto:[email protected]] 
Sent: 28 March 2013 20:39
To: 'HttpClient User Discussion'
Subject: RE: SSL verification - is it a warning, can it be made strict?

I am jumping in on a conversation I have not really followed, so I apologize if 
I am just adding noise to your conversion.

When I saw you mention random ConnectionReset errors, I recalled when I was 
getting this error.  It turned out to be something in the Tomcat configuration. 
 If you are using Tomcat, you may want to try to add this to your connector:
maxKeepAliveRequests="-1"

Tomcat, by default, closes persistent connections periodically.  With the 
ConnectionLinger set to 0 (as we had it), this caused problems.

Here is what Oleg said in an email:

-----Original Message-----
From: Oleg Kalnichevski [mailto:[email protected]]
Sent: Tuesday, January 29, 2013 3:09 PM
To: HttpClient User Discussion
Subject: Re: Connection Reset errors 

> Tomcat by default closes persistent connections once it has been used to 
> serve 100 requests. 
> See 'maxKeepAliveRequests' parameter:
> http://tomcat.apache.org/tomcat-7.0-doc/config/http.html
> Try setting this value to -1 and see if that makes the problem go away.

-----Original Message-----
From: Kimpton, C (Chris) [mailto:[email protected]]
Sent: Thursday, March 28, 2013 8:04 AM
To: '[email protected]'
Subject: RE: SSL verification - is it a warning, can it be made strict?

Hi,

I am trying it with less threads and that seems to help.

I am also getting (and have been all along) intermittent connection issues, 
like so:

java.net.SocketException: Connection reset
12:02:06:752|TH12 INFO: Backtrace:
        java/net/SocketInputStream.java:168:in `read'
        com/sun/net/ssl/internal/ssl/InputRecord.java:293:in `readFully'
        com/sun/net/ssl/internal/ssl/InputRecord.java:331:in `read'
        com/sun/net/ssl/internal/ssl/SSLSocketImpl.java:863:in `readRecord'
        com/sun/net/ssl/internal/ssl/SSLSocketImpl.java:820:in `readDataRecord'
        com/sun/net/ssl/internal/ssl/AppInputStream.java:75:in `read'
        org/apache/http/impl/io/AbstractSessionInputBuffer.java:166:in 
`fillBuffer'
        org/apache/http/impl/io/SocketInputBuffer.java:90:in `fillBuffer'
        org/apache/http/impl/io/AbstractSessionInputBuffer.java:281:in 
`readLine'
        org/apache/http/impl/conn/DefaultHttpResponseParser.java:92:in 
`parseHead'
        org/apache/http/impl/conn/DefaultHttpResponseParser.java:62:in 
`parseHead'
        org/apache/http/impl/io/AbstractMessageParser.java:254:in `parse'
        org/apache/http/impl/AbstractHttpClientConnection.java:289:in 
`receiveResponseHeader'
        org/apache/http/impl/conn/DefaultClientConnection.java:252:in 
`receiveResponseHeader'
        org/apache/http/impl/conn/ManagedClientConnectionImpl.java:191:in 
`receiveResponseHeader'
        org/apache/http/protocol/HttpRequestExecutor.java:300:in 
`doReceiveResponse'
        org/apache/http/protocol/HttpRequestExecutor.java:127:in `execute'
        org/apache/http/impl/client/DefaultRequestDirector.java:717:in 
`tryExecute'
        org/apache/http/impl/client/DefaultRequestDirector.java:522:in `execute'
        org/apache/http/impl/client/AbstractHttpClient.java:906:in `execute'
        com/rabobank/bondtrading/rabowriterx/HttpClient.java:112:in `post'

I wonder if its possible that if these occur during the SSL connection part 
that it results in the SSLPeerUnverified error?

Regards,
Chris
_____________________________________________________________

This email (including any attachments to it) is confidential, legally 
privileged, subject to copyright and is sent for the personal attention of the 
intended recipient only. If you have received this email in error, please 
advise us immediately and delete it. You are notified that disclosing, copying, 
distributing or taking any action in reliance on the contents of this 
information is strictly prohibited. Although we have taken reasonable 
precautions to ensure no viruses are present in this email, we cannot accept 
responsibility for any loss or damage arising from the viruses in this email or 
attachments. We exclude any liability for the content of this email, or for the 
consequences of any actions taken on the basis of the information provided in 
this email or its attachments, unless that information is subsequently 
confirmed in writing.
_____________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to