Laurent, Unfortunately I do not have WAS 5.0 at my disposal. Besides, HttpClient 2.0rc1 has been reported to work fine with IBM JSSE 1.0.3 just recently (last Friday to be exact), so I still tend to think that this is a problem of your local environment. I can only suggest that you activate JSSE debug log in order to find why the connection is dropped.
Oleg -----Original Message----- From: Laurent Garcia [mailto:[EMAIL PROTECTED] Sent: Monday, October 06, 2003 14:19 To: Commons HttpClient Project Subject: Re: IBMJSSE implementation issue Oleg, I try to disabling stale connection and I have still Socket closed. I don't want to take your time but you can do a very simple, test this code in a servlet with WSAD 5.0 (with the default JSSE) HttpClient httpclient = new HttpClient(); httpget = new GetMethod("https://www.verisign.com/";); httpclient.executeMethod(httpget); I assume that I am not the only people that use http-client in a servlet in WSAD-WAS 5.0 environment. Laurent ----- Original Message ----- From: "Kalnichevski, Oleg" <[EMAIL PROTECTED]> To: "Commons HttpClient Project" <[EMAIL PROTECTED]> Sent: Monday, October 06, 2003 11:54 AM Subject: RE: IBMJSSE implementation issue Laurent, HttpClient relies on underlying JSSE library to establish SSL connections. If there's something wrong with SSL, in the overwhelming majority of cases it has nothing to do with HttpClient as such. Usually SSL problems are caused by misconfigured JSSE stack. Please refer to the troubleshooting section of our SSL guide and see if the plain SSL socket test works for you http://jakarta.apache.org/commons/httpclient/sslguide.html Oleg -----Original Message----- From: Laurent Garcia [mailto:[EMAIL PROTECTED] Sent: Monday, October 06, 2003 11:44 To: Commons HttpClient Project Subject: Re: IBMJSSE implementation issue Oleg, Thank you for your (quick) response, I edit the Manifest file (I made a copy below) and it seems that the version is 1.03 Manifest-Version: 1.0 Created-By: Ant 1.4.1 Name: com/ibm/jsse/ com/ibm/net/ssl/www/ com/ibm/net/ssl/ com/ibm/net/ss l/internal/www/protocol/https/ com/ibm/net/ssl/www/protocol/http/ com/i bm/net/ssl/www/protocol/https/ com/ibm/pkcs11/ com/ibm/pkcs11/nat/ com/ ibm/security/cert/ com/ibm/sslight/ com/ibm/sslite/ javax/net/ javax/ne t/ssl/ javax/security/cert/ IBM-Reusable-JVM-Compatible: True Build-Level: -20021008 Implementation-Vendor: IBM Corporation Implementation-Title: JSSE Package Implementation-Version: 1.0.3 Laurent ----- Original Message ----- From: "Kalnichevski, Oleg" <[EMAIL PROTECTED]> To: "Commons HttpClient Project" <[EMAIL PROTECTED]> Sent: Monday, October 06, 2003 11:34 AM Subject: RE: IBMJSSE implementation issue Laurent, Make sure that the version of IBMJSSE library WSAD is using is 1.0.3. Oleg -----Original Message----- From: Laurent Garcia [mailto:[EMAIL PROTECTED] Sent: Monday, October 06, 2003 11:30 To: [EMAIL PROTECTED] Subject: IBMJSSE implementation issue Hi, I was working with an old commons-httpclient lib (18/2/2003) that work correctly for https connexion with both SUN adn IBM jsse implemention. But I just replaced my commons-httpclient by commons-httpclient-2.0-rc1.jar and now it is still working with SUN but I have a systematic socked closed error If I try this code in a sevlet (with WSAD 5.0) : System.out.println("HttpsTestServlet starting test..."); GetMethod httpget; try { HttpClient httpclient = new HttpClient(); httpget = new GetMethod("https://www.verisign.com/";); httpclient.executeMethod(httpget); System.out.println(httpget.getStatusLine().toString()); } catch (Exception e) { System.out.println(e); } System.out.println("HttpsTestServlet test completed..."); java.net.SocketException: Socket closed at java.net.PlainSocketImpl.socketGetOption(Native Method) at java.net.PlainSocketImpl.getOption(PlainSocketImpl.java:214) at java.net.Socket.getSendBufferSize(Socket.java:548) at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:700) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:625) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:500) is it a bug ? or I did something wrong ? Thank you Laurent --------------------------------------------------------------------- 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] --------------------------------------------------------------------- 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]
