Ok ... 1. Tomcat version 5.0.x is no longer supported. You should at minimum move to the latest stable 5.5.x if at all possible.
2. According to http://tomcat.apache.org/tomcat-5.5-doc/config/http.html, Tomcat's HTTP connector uses 1.1 protocol by default, falling back to 1.0 if the client doesn't support it. Of course that tomcat 5.5's docs, so your mileage may very a little in 5.0 land. Does your .NET client app support HTTP 1.1 protocol or does it only offer 1.0? It's the only thing I can think of causing connections to drop at the end of a request. 3. You could test briefly w/o SSL and use wireshark to see on the wire what's negotiated between client and server to determine if protocol versions are causing trouble. --David jithu mada wrote: > We have increased the debug value to 99. But didn't see any difference in > the log files. I have looked at all the log files catalina.log ,catalina.out > and localhost access log. > > Which log we should be looking after increase the debug to 99. > > we are using HTTP protocol 1.1 and the application is developed on Sun JDK ( > did I answer your questions). > > thanks for your help. > > On Sat, Sep 19, 2009 at 9:13 PM, Martin Gainty <mgai...@hotmail.com> wrote: > > >> can you crank up the logging debug="99" and send us the log at the point of >> failure >> >> couple of things to check : >> which version HTTP protocol="1.1" ? >> are you using IBM JDK before implementing algorithm="IbmX509" >> >> http://people.apache.org/~fhanik/http.html<http://people.apache.org/%7Efhanik/http.html> >> Martin Gainty >> ______________________________________________ >> Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité >> >> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene >> Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte >> Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht >> dient lediglich dem Austausch von Informationen und entfaltet keine >> rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von >> E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. >> Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le >> destinataire prévu, nous te demandons avec bonté que pour satisfaire >> informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie >> de ceci est interdite. Ce message sert à l'information seulement et n'aura >> pas n'importe quel effet légalement obligatoire. Étant donné que les email >> peuvent facilement être sujets à la manipulation, nous ne pouvons accepter >> aucune responsabilité pour le contenu fourni. >> >> >> >> >> >>> Date: Sat, 19 Sep 2009 20:27:25 -0400 >>> Subject: Re: Does tomcat log closed connection >>> From: jithu.m...@gmail.com >>> To: users@tomcat.apache.org >>> >>> And the communication is done on the SSL port 8443. >>> >>> On Sat, Sep 19, 2009 at 8:26 PM, jithu mada <jithu.m...@gmail.com> >>> >> wrote: >> >>>> Hi David, >>>> >>>> these are the connector elements we have in our server.xml file >>>> >>>> <!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 --> >>>> <Connector port="8080" >>>> maxThreads="150" minSpareThreads="25" >>>> >> maxSpareThreads="75" >> >>>> enableLookups="true" redirectPort="8443" >>>> >> acceptCount="100" >> >>>> debug="0" connectionTimeout="60000" >>>> disableUploadTimeout="true" /> >>>> >>>> <!-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 --> >>>> <Connector port="8443" >>>> maxThreads="150" minSpareThreads="25" >>>> >> maxSpareThreads="75" >> >>>> enableLookups="true" disableUploadTimeout="true" >>>> acceptCount="100" debug="99" scheme="https" >>>> >> secure="true" >> >>>> clientAuth="false" sslProtocol="TLS" >>>> keystoreFile="conf/keystore" >>>> algorithm="IbmX509" /> >>>> >>>> The client is a .NET client here is the sequence of communication >>>> >> before >> >>>> the connection is closed >>>> >>>> 1) The client sends a request to our application to create a session. >>>> 2) Tomcat sees the client is not logged in and sends a login.html to >>>> >> login >> >>>> in >>>> 3) Client sends a username and password. Client gets authenticated and >>>> >> is >> >>>> redirected to original request >>>> 4) Tomcat is receiving this request and our application creates a >>>> >> session >> >>>> for that user >>>> 5) After this client says the connection was closed unexpectedly. >>>> >>>> There are no proxys in between. >>>> >>>> I appreciate your help. >>>> >>>> thanks >>>> >>>> Jithu >>>> >>>> >>>> On Sat, Sep 19, 2009 at 7:38 PM, David Smith <d...@cornell.edu> wrote: >>>> >>>> >>>>> jithu mada wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I am using Tomcat 5.0.27 on AIX. >>>>>> >>>>>> Its abruptly closing a connection after processing a user request >>>>>> successfully. >>>>>> >>>>>> Wanted to know does it log anywhere why is it closing the connection >>>>>> >> or >> >>>>> do >>>>> >>>>>> we need to change any settings to make it log closed connections. >>>>>> >>>>>> Thanks >>>>>> >>>>>> Jithu >>>>>> >>>>>> >>>>>> >>>>> We need details to be able to answer you. What do you have configured >>>>> for your Connectors in server.xml. Please don't post the entire >>>>> server.xml, comments and all -- just the active (uncommented) >>>>> >> <Connector >> >>>>> ... /> elements. Also tell us a little about your client and how you >>>>> are detecting this connection close. Lastly, if you have Apache Httpd >>>>> or some other proxy like service in between tomcat and your client, we >>>>> will need to know that as well. >>>>> >>>>> --David >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >>>>> For additional commands, e-mail: users-h...@tomcat.apache.org >>>>> >>>>> >>>>> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
