Hi Dileep, Now I understood your problem clearly. This is quite normal. When the database goes down all the connection object in your pool become Invalid. Basically you need to create new connections in order to connect to the restarted db. When you use JRun pooling, JRun is handling this. So either you can use JRun pooling or change your algorithm accordingly.
This is absolutely nothing to do with query. Regards Savant -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, April 01, 2002 11:11 PM To: JRun-Talk Subject: RE: Connection reset by peer: socket write error Thanks savant for writing. We are using Oracle 8.1.5 version. And I get the problem when I use my connectio pooling, but if I use JRun's connection pooling then it works fine. So the problem lies somewhere in my connection pooling. I have tried resetting the connection to null after closing but that also doesn't work. Let me describe a bit more about the situation in that this error occurs. We have a Oracle database that is down for 15 minutes everyday in the night for some backup process. When database is up we get "Connection reset by peer", until we restart the JRun server. But that doesn't happen using JRun's connection pool. Now do you still think that this is related to query not pool? Regards Dilip -----Original Message----- From: Savantraj, Chennamakal Subramanian [mailto:[EMAIL PROTECTED]] Sent: Sunday, March 31, 2002 7:21 PM To: JRun-Talk Subject: RE: Connection reset by peer: socket write error Hi Dilip, Are you using Oracle 8.1.6 Version? Try to run the same SQL from SQLPLUS. If that also fails problem is not with JAVA .Problem is with Oracle. I have encountered this problem while I was running a complicated SQL having a few inner Queries and Distinct clauses. Funny thing was once I removed some Distinct clause the SQL worked. The problem is still a misery.We moved to Oracle 8.1.7 then everything went fine. Rgds Savant -----Original Message----- From: Theodore Zimmerman [mailto:[EMAIL PROTECTED]] Sent: Friday, March 29, 2002 2:26 AM To: JRun-Talk Subject: RE: Connection reset by peer: socket write error Are you using a datatypes like blobs or clobs? I've been doing some testing lately with those datatypes and unless you used Oracle's implementation would get that same error. Ted Zimmerman -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 28, 2002 11:51 AM To: JRun-Talk Subject: RE: Connection reset by peer: socket write error Ya, I am using Oracle's thin driver. -----Original Message----- From: Ben Groeneveld [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 28, 2002 11:34 AM To: JRun-Talk Subject: Re: Connection reset by peer: socket write error What's JRun's Oracle driver? Have you tried using oracle's free thin driver? We use oracle JDBC driver-8.1.6.2.0 on a large variety of projects and operations w/o a hiccup. Maybe trying it will help you. BenG. [EMAIL PROTECTED] wrote: >Hi, >I am getting the following error while accessing the database. >I have JRun 3.1.15506 app server running on win2000 and NT both, and using >oracle database. Instead of using JRun's connection pool for oracle I am >using my own connection pool. The system works fine most of the times but >all of a sudden it starts giving "Connection reset by peer". I didn't have >this problem when I was using JRun's Oracle thin driver connection pool >before. But for migrating reasons I started using my own connection pool. >Sometimes when I query the database using preparedStatement, it throws the >below exception. I am seeing the same exception both on NT and win2000. >Please tell what might the reason behind. >Thanks >_________________________________________ >_________________________________________ > >Thu Mar 28 10:13:31 EST 2002 >Io exception: Connection reset by peer: socket write error >java.sql.SQLException: Io exception: Connection reset by peer: socket write >error > at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114) > at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:156) > at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269) > at >oracle.jdbc.driver.OracleStatement.<init>(OracleStatement.java:292) > at >oracle.jdbc.driver.OracleStatement.<init>(OracleStatement.java:307) > at >oracle.jdbc.driver.OraclePreparedStatement.<init>(OraclePreparedStatement.j a >va:194) > at >oracle.jdbc.driver.OraclePreparedStatement.<init>(OraclePreparedStatement.j a >va:177) > at >oracle.jdbc.driver.OracleConnection.prepareStatement(OracleConnection.java: 3 >39) > at >com.emc.asi.ejb.pool.ASIConnection.prepareStatement(ASIConnection.java:61) > at com.emc.asi.ejb.LoginBean.processLogin(LoginBean.java:48) > at java.lang.reflect.Method.invoke(Native Method) > at >allaire.ejipt._BeanMethod._invoke(allaire/ejipt/_BeanMethod.java:166) > at >allaire.ejipt._SessionObject._invoke(allaire/ejipt/_SessionObject.java:182) > at >allaire.ejipt._CallableObject.call(allaire/ejipt/_CallableObject.java:101) > at java.lang.reflect.Method.invoke(Native Method) > at >sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:241) > at sun.rmi.transport.Transport$1.run(Transport.java:152) > at java.security.AccessController.doPrivileged(Native Method) > at sun.rmi.transport.Transport.serviceCall(Transport.java:148) > at >sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:465) > at >sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java: 7 >06) > at java.lang.Thread.run(Thread.java:484) > ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
