tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 34170] New: - Connection reset by peer exception while performing basic authentication (db connection pool not being used)
Date Thu, 24 Mar 2005 23:56:58 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=34170>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=34170

           Summary: Connection reset by peer exception while performing
                    basic authentication (db connection pool not being used)
           Product: Tomcat 5
           Version: 5.5.7
          Platform: Macintosh
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: sowmyav@udel.edu


Hi,
Problem:
While trying to login to our application using basic authentication, there is an
sql exception being thrown. It starts working fine after tomcat is restarted.
This happens periodically. I am not sure about how often users logged in between
 periods of failure. It is possible that there was nobody using it for may be 15
days or so. It is critical that we fix this problem asap as the users are
unhappy about failures this often. 
What's puzzling is that while performing basic authentication, the connection
should be closed after the browser is exited. So how can there be a connection
reset problem!!!

Environment:

The basic authentication has been configured using JDBC Realm entry in
context.xml of the app. The backend database is Oracle 10G that is on a
different m/c from that where tomcat runs. 

Symptoms:
The server was restarted on Feb 25 and the log below shows socket exception on
Feb 27. When there was an attempt to login on Mar 15, there was an
authentication error. But the socket exception doesn't show up in the logs
anytime after Feb 27 although authentication failed once again on Mar 24. It is
not clear why there's only one socket exception but two authentication failures
between restarts of tomcat.

Feb 25, 2005 3:12:48 PM org.apache.catalina.startup.Catalina startINFO: Server
startup in 5250 msFeb 27, 2005 3:52:51 AM
org.apache.tomcat.util.net.PoolTcpEndpoint processSocketSEVERE: Socket error
caused by remote host /60.21.206.10java.net.SocketException: Connection reset by
peer        at java.net.PlainSocketImpl.socketSetOption(Native Method)        at
java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:240)        at
java.net.Socket.setTcpNoDelay(Socket.java:771)        at
org.apache.tomcat.util.net.PoolTcpEndpoint.setSocketOptions(PoolTcpEndpoint.java:502)
       at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:514)
       at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
       at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
       at java.lang.Thread.run(Thread.java:552)Mar 15, 2005 9:41:50 AM
org.apache.catalina.realm.JDBCRealm getPasswordSEVERE: Exception retrieving
password for "evm"java.sql.SQLException: Io exception: Connection reset       
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:124)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:161)
        at
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:273)
        at
oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows(T4CPreparedStatement.java:800)
        at
oracle.jdbc.driver.OracleStatement.execute_maybe_describe(OracleStatement.java:912)
        at
oracle.jdbc.driver.T4CPreparedStatement.execute_maybe_describe(T4CPreparedStatement.java:693)
        at
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:983)
        at
oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2884)
        at
oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:2925)
        at org.apache.catalina.realm.JDBCRealm.getPassword(JDBCRealm.java:526)
        at org.apache.catalina.realm.JDBCRealm.authenticate(JDBCRealm.java:399)
        at org.apache.catalina.realm.JDBCRealm.authenticate(JDBCRealm.java:347)
at org.apache.catalina.realm.JDBCRealm.authenticate(JDBCRealm.java:347)       
at
org.apache.catalina.authenticator.BasicAuthenticator.authenticate(BasicAuthenticator.java:181)
       at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:446)
       at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)  
     at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)  
     at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
       at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)    
     at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825)     
     at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:738)
       at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:526)
        at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message