Connection Reset exception received in Windows only

Hi,
I have two instances of my java app, one on Windows, one on Linux, both connected to the same cpp app running on Linux, and the machine running the cpp app is very heavily loaded. After some time, only the windows java app gets a Socket Exception (Connection Reset), not the linux.
In fact, after connecting to the cpp app, the java app starts a number of transactions with the cpp app, requesting data from the cpp app. The trasanctions are timing out on Windows, but not on Linux.
Does anyone have any idea why this might be happening?
Thanks for any help,
Regards,
Shefali

Hello,
I have the same problem. My java TCP client detect disconnection (Connection Reset exception is generated) after about 60 seconds. With Suse 10 it make more then 15 minutes!!!!
This is not normal of an application that it takes that long to detect a disconnection! Is there a way of changing/configuring the timeout of the TCP/IP layer of the OS?
Thanks in advance for your help.
Alain.

Similar Messages

Connect Reset exception

hi
I am currently doing distributed computing as my project.
My problem statement is "doing a complex computation(e.g matrix multiplication ,sorting a big array) by distributing the job across different or heterogenous(want to connect linux and windows )machines in the network.
we are using RMI.we took matrix multiplication and we disributed the job equally depending upon the no of machines avalable.
i.e if we have matrix of order 4 and four clients then we give each row of the matrix to each client and if we have 2 clients we give 2 rows for each client and do the calculation.
we are able to run it on windows platform sucessfully and able to gather the results back correctly.
But when we tried to run it on cross platform(one linux machine and one windows machine or between linux machines)we get CONNECTION RESET EXCEPTION
how to overcome or handle this exception,we are not able to run our project in linux...
suggest me your ideas on this
thanks in advance
vasu

This isn't really JavaMail or even Java related, but you can do a google search for "lotus notes pop3 setup" and the first few pages that come up seem to be pretty helpful (I've only used notes once a couple of years ago).
travis (at) overwrittenstack.com

Connection reset exception

I am getting the below exception in my weblogic logs
[FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.
java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.
     at weblogic.jdbc.sqlserverbase.dda4.b(Unknown Source)
     at weblogic.jdbc.sqlserverbase.dda4.a(Unknown Source)
     at weblogic.jdbc.sqlserverbase.dda3.b(Unknown Source)
     at weblogic.jdbc.sqlserverbase.dda3.a(Unknown Source)
     at weblogic.jdbc.sqlserverbase.dda3.a(Unknown Source)
     at weblogic.jdbc.sqlserver.tds.ddb.a(Unknown Source)
     at weblogic.jdbc.sqlserver.ddj.a(Unknown Source)
     at weblogic.jdbc.sqlserverbase.ddde.a(Unknown Source)
     at weblogic.jdbc.sqlserverbase.ddde.a(Unknown Source)
     at weblogic.jdbc.sqlserverbase.ddde.r(Unknown Source)
     at weblogic.jdbc.sqlserverbase.ddde.execute(Unknown Source)
     at gov.fssa.bcd.utils.JDBCConnection.runQuery(JDBCConnection.java:366)
     at gov.fssa.bcd.utils.JDBCConnection.runQuery(JDBCConnection.java:492)
     at gov.fssa.bcd.utils.JDBCConnection.runQuery(JDBCConnection.java:428)
This exception happens randomly on production.
I am not sure is it a problem with Weblogic 10.3.5 or my database server or the java app or network related.
Can anyone please help me to conclude which side of the appplication is at fault.
I am using Java 1.6.0_27,Weblogic 10.3.5, sql server 2005
Weblogic is on a Windows server 2008 sp2 and database is on windows server 2003.
Is it because of Java coding or some network related?In what scenarios will a java program throw such errors.
Let me know if any more info is required .
Thanks,

"Failing Client" means the application you are using to connect fails unexpectedly. It is a failure of the application you are using to run the process.
you can check the Managed Server logs for more detail of what is happening.
Edited by: HDeiby on 4/10/2012 04:25 PM

Regarding connection reset exception in socket

hi,
I am using java socket on one side and c socket on other side iam trying to send data and recieve from it but i got error socketexception connection reset by the peer,
Environment which i am using to open a socket is websphere studio test environment
opereating system on one side is linux and other side is windows
could somebody please help
it's urgent

You will get this under the following circumstances:
(1) The process at the other end has crashed.
(2) the other end has closed after messing around with SO_LINGER.
(3) you have sent data to the other end after it has closed its socket.

Connection reset exception while accessing the server page using HttpClient

hi all,
In my servlet class I am using HttpClient to connect to the server.
while connecting i am getting the below exception...
please guide me guys..
Nov 21, 2007 4:29:23 PM org.apache.commons.httpclient.HttpMethodBase processRequest
INFO: Recoverable exception caught when processing request
Nov 21, 2007 4:29:23 PM org.apache.commons.httpclient.HttpMethodBase processRequest
WARNING: Recoverable exception caught but MethodRetryHandler.retryMethod() returned false, rethrowing exception
org.apache.commons.httpclient.HttpRecoverableException: java.net.SocketException: Connection reset
        at org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1962)
        at org.apache.commons.httpclient.HttpMethodBase.processRequest(HttpMethodBase.java:2653)
        at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1087)
        at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:643)
        at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:497)
        at LoginToKotak.accountTxn(LoginToKotak.java:916)
        at LoginToKotak.kotakAmountTxn(LoginToKotak.java:147)
        at ResponseServlet_kotakMB.getAccountTxn(ResponseServlet_kotakMB.java:158)
        at ResponseServlet_kotakMB.processRequest(ResponseServlet_kotakMB.java:128)
        at ResponseServlet_kotakMB.doPost(ResponseServlet_kotakMB.java:197)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
        at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
        at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
        at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
        at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
        at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
        at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
        at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
        at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
        at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
        at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
        at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
        at java.lang.Thread.run(Thread.java:595)

Mallikarjuna,
PL/SQL: ORA-00942: table or view does not exist
ORA-06550: line 1, column 7:As the error message specifies.. table XXCUR_TRADE_CUSTOMER_DETAILS doesnt exists.
Create a synonyms for this table in apps schema with all the grants.
Regards,
Gyan

Io exception: Connection reset - after some time interval

Hi,
We are facing a problem in connection while implementing connection pooling using OracleDataSource .
Application is running with out any issue if it is called continuously.
If we call the application after some time interval, connection is being reset. We are able to get the connection instance but connection reset exception is thrown while calling callableStatement.execute().
If application called after application restart it is working fine.This issue is happening only for the first few calls made after some time interval.(after 1 hr)
After that call is proceeding without any issue.
Environment Details
Application is accessing 4 oracle databases and the versions are viz., 9.2.0.8,10.2.0.3,10.2.0.4 and 9.2.0.1.
Driver : ojdbc14.jar
App Server : tomcat
jdk version: 1.5
OracleDataSource is being used for connection pooling.
propCache.setProperty("ConnectionWaitTimeout",10); // caching parms
ods.setConnectionCachingEnabled(true);
ods.setLoginTimeout(intLoginTimeout);
propCache.setProperty("MinLimit","5");
propCache.setProperty("MaxLimit", "20");
propCache.setProperty("InitialLimit","5");
propCache.setProperty("ValidateConnection", "true");
propCache.setProperty("AbandonedConnectionTimeout", "10");
The exception details are as follows
java.sql.SQLException: Io exception: Connection reset
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:255)
at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:987)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1170)
at oracle.jdbc.driver.OracleStatement.doScrollExecuteCommon(OracleStatement.java:4043)
at oracle.jdbc.driver.OraclePreparedStatement.doScrollPstmtExecuteUpdate(OraclePreparedStatement.java:10826)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3337)
at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3445)
at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:4394)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:834)
at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:640)
at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1286)
at java.lang.Thread.run(Unknown Source)
Any suggestion to resolve this issue is greatly appreciated.
Thanks.

Hi,
try to utilize OracleDataSource#setConnectionCacheProperties() with property InactivityTimeout equals to 1800 (30 minutes in seconds).

Problem of Connection Reset

hello all,
can you please tell me in my client,server program why it gives connection reset exception if I try to send an integer from server to client.Client Program
import java.net.*;
import java.io.*;
public class ClientServer {
    public static void main(String[] args) {
         Socket ClientSock;
     DataInputStream in;
     DataOutputStream out;
     DataInputStream info;
            // TODO, add your application code
         System.out.println("Hello World!");
             try
          ClientSock =new Socket("localhost",4000);
          in=new DataInputStream(ClientSock.getInputStream());
          out=new DataOutputStream(ClientSock.getOutputStream());
          info=new DataInputStream(System.in);
          System.out.println("client");
          System.out.println("EFN");
          out.writeInt(Integer.parseInt(info.readLine()));
          System.out.println("ESN");
          out.writeInt(Integer.parseInt(info.readLine()));
          System.out.println(in.readUTF());
          System.out.println("sum ="+in.readInt());
           }catch(Exception e)
                System.out.println(e.getMessage());
Server Program
import java.net.*;
import java.io.*;
public class server {
     ServerSocket serv;
     Socket client;
     FileInputStream fin;
     FileOutputStream fout;
     DataInputStream din;
     DataOutputStream dout;
    public server() {
         try{
              serv=new ServerSocket(4000);
         catch(Exception e)
              e.printStackTrace();
    public static void main(String args[])
         server s=new server();
         s.talk();
    public void talk()
    {String msg;
         try{
         client=serv.accept();
         System.out.println("request received");
         System.out.println(client.toString());
    DataInputStream     in=new DataInputStream(client.getInputStream());
          DataOutputStream   out=new DataOutputStream(client.getOutputStream());
          int a=in.readInt();
          int b=in.readInt();
          try{
          int x=a+b;
          String no=new String(new Integer(x).toString());
          System.out.println(no);
          out.writeUTF(no);
          out.writeUTF("man");
          catch(Exception e)
               e.getStackTrace();
         catch(Exception e)
         finally
                   try{
                   serv.close();
                   catch(Exception e)
}

actually server should be in the continuous listeneing mode...
so i added the line
while(true)
all the server side logic
it worked fine
actually server was returning the result and was hanging up..
thank you

JDBC 4.J - Connection reset

Hi,
I have problem with JDBC(4.1) cennection to MS SQL 2012. I have java application which is running in loop and contacting sql server. Java program works for few minutes(max 4hours) and then going to down with error message:
com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerC
onnection.java:1668)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerC
onnection.java:1655)
at com.microsoft.sqlserver.jdbc.TDSChannel.read(IOBuffer.java:1789)
at com.microsoft.sqlserver.jdbc.TDSReader.readPacket(IOBuffer.java:4881)
at com.microsoft.sqlserver.jdbc.TDSReader.nextPacket(IOBuffer.java:4791)
at com.microsoft.sqlserver.jdbc.TDSReader.ensurePayload(IOBuffer.java:47
67)
at com.microsoft.sqlserver.jdbc.TDSReader.readUnsignedByte(IOBuffer.java
:4970)
at com.microsoft.sqlserver.jdbc.SQLServerResultSet.initializeNullCompres
sedColumns(SQLServerResultSet.java:711)
at com.microsoft.sqlserver.jdbc.SQLServerResultSet.discardCurrentRow(SQL
ServerResultSet.java:1709)
at com.microsoft.sqlserver.jdbc.SQLServerResultSet.fetchBufferNext(SQLSe
rverResultSet.java:1774)
at com.microsoft.sqlserver.jdbc.SQLServerResultSet.next(SQLServerResultS
et.java:1034)
at javaapplication1.JavaApplication1.main(JavaApplication1.java:79)
Anybody idea?
Thanks
Tom

Hi Eric,
thank you for the answer. I tried JDBC 4.0, 4.1 and our supplier works with JTDS. Both have the same result with connection reset exception. If I put query with few records(tens of record), it is work fine. But If I put query on table with 1000 - 1 000 000
recods, the loop is gooing to Exception (connection reset), sometimes it work few minutes sometimes it works for few hours.
Tom
code here:
public class JavaApplication1 {
public static void main(String[] args) {
String url = "jdbc:sqlserver://X.X.X.X\\ITSQL:1433;databaseName=Alvao;autoReconnect=true";
Statement stmt = null;
ResultSet result = null;
String driver = "com.microsoft.sqlserver.jdbc.SQLServerDriver";
String databaseUserName = "USER";
String databasePassword = "PSWD";
try {
while(true){
String col1, col2, col3;
Class.forName(driver);
conn = DriverManager.getConnection(url, databaseUserName, databasePassword);
long startTime = System.currentTimeMillis();
stmt = conn.createStatement();
result = null;
result = stmt.executeQuery("SELECT SYSDATETIME()");
result.next();
String serverTime = result.getString(1);
System.out.println(serverTime);
result = stmt.executeQuery("SELECT Convert(nvarchar(20), PK_USER_ID) +'_'+ Convert(nvarchar(20), PersonalId) +'_'+ Convert(nvarchar(20), Employment) as ret FROM [Alvao].[nova_idm_export].[Person]
where PersonalId = '710804'");
result.next();
String result1 = result.getString(1);
System.out.println(result1);
result = stmt.executeQuery("SELECT count(*) celkem FROM [Alvao].[nova_idm_import].[tImportPerson]");
result.next();
String result2 = result.getString(1);
System.out.println(result2);
stmt.setQueryTimeout(30000);
// This table returns > 1 000 000 records. If I skip this query, the lopp newer crashes
result = stmt.executeQuery("SELECT * FROM [Alvao].[dbo].[tblLog]");
result.setFetchSize(10000);
int counter = 0;
while(result.next()){
counter++;
String result3 = Integer.toString(counter);
System.out.println(result3);
conn.close();
long estimatedTime = System.currentTimeMillis() - startTime;
System.out.println(estimatedTime);
System.out.println("---------------");
BufferedWriter bw = new BufferedWriter(new FileWriter("soubor.txt", true));
bw.write(serverTime+" "+result1+" "+result2+" "+estimatedTime);
bw.newLine();
bw.flush();
Thread.sleep(2000);
} catch (Exception e) {
e.printStackTrace();
try{
BufferedWriter bw = new BufferedWriter(new FileWriter("souborChyb.txt", true));
bw.write(e.getMessage());
bw.newLine();
bw.flush();
}catch(IOException ex){

Io exception: Connection reset by peer: JVM_recv in socket input stream read

We are developing a new J2EE app using JDev, OC4J, servlets, and EJBs. We have determined that our firewall is closing database connections that have been idle for 1 hour. This is a security requirement that cannot be changed. When we try to use these idle connections in both stateless and entity beans, we consistently receive this or a similar error message:
"ServletSACategoryList: Error invoking EJB procedure. Exception: java.sql.SQLException: StatelessSysAdminBean::getCategoryList - Io exception: Connection reset by peer: JVM_recv in socket input stream read "
Environment:
Oracle 9iAS 9.0.2.0.0
Database: Oracle 8.1.7
JDBC 8.1.7
JDK 1.3
JDev 9.0.2.829
We are using the ejb-location attribute within data-sources.xml for JNDI lookup of the DataSource. Here is what this file looks like:
<data-sources>
<data-source
class="oracle.jdbc.pool.OracleDataSource"
name="jdbc/OracleDS"
location="jdbc/OracleCoreDS"
xa-location="jdbc/xa/OracleXADS"
ejb-location="jdbc/OraclePoolDS"
url="jdbc:oracle:thin:@###.###.#.###:1521:dev1"
connection-driver="oracle.jdbc.driver.OracleDriver"
username="????????"
password="????????"
max-connections="4"
wait-timeout="20"
min-connections="1"
inactivity-timeout="60"
connection-retry-interval="1"
max-connect-attempts="3"
/>
</data-sources>
After calling getConnection() on the Connection object in my stateless bean, I have tried checking if the Connection object is null or isClosed(), I have caught any Exception, and looped to try again, but nothing has worked.
Please respond to [email protected] or directly to this post if you can help in any way.
Thank you,
- Rob

Hi Robert,
If you don't mind, I can only offer a few suggestions for things
to try -- I'm afraid I don't have a solution for you. Of-course,
you may have already tried these things, so please excuse me if
this is the case.
Firstly, your "data-sources.xml" file looks "different". Have
you read the "Data Sources" chapter of the "Oracle9iAS Containers
for J2EE Services Guide, Release 2 (9.0.2)"? It is accessible
from here:
http://otn.oracle.com/docs/products/ias/doc_library/90200doc_otn/web.902/a95879/ds.htm#1004903
Also, have you tried running OC4J in "debug" mode? This web
page has more details:
http://kb.atlassian.com/content/atlassian/howto/orionproperties.jsp
I get the impression from the information you have supplied,
that you may not be explicitly closing your database connections
in your code. It looks to me like you are obtaining a database
connection in your session bean, and then keeping it for the
lifetime of that bean. Is that correct? I think it's better
to obtain a connection when you need to interact with the database,
and then close the connection immediately after completing the
interaction with the database (but that's just my opinion).
Lastly, if you haven't already discovered them, these web sites
may also be of help:
http://www.orionserver.com
http://www.orionsupport.com
http://www.elephantwalker.com
Hope this helps you.
Good Luck,
Avi.

-708 Data receive failed [Connection reset].

We have a problem with this error in DB.
-708 Data receive failed [Connection reset]
We use
MAXDB version: 7.6.00.37
JDBC driver version 7.6.00
After first error occurrence, is error repeating and DB server must be restarted to continue. I read some info about this error on internet, but it didn't help us. We doing nothing with statistics. In this case we execute only simple SELECT prepared statement.
Here is part of our log file with first error:
15.07.2008 13:45:28.114
Caused by: com.sap.dbtech.jdbc.exceptions.ConnectionException: [-708] Data receive failed [Connection reset].
     at com.sap.dbtech.jdbc.ConnectionSapDB.execute(Unknown Source)
     at com.sap.dbtech.jdbc.CallableStatementSapDB.sendCommand(Unknown Source)
     at com.sap.dbtech.jdbc.StatementSapDB.sendSQL(Unknown Source)
     at com.sap.dbtech.jdbc.CallableStatementSapDB.doParse(Unknown Source)
     at com.sap.dbtech.jdbc.CallableStatementSapDB.constructor(Unknown Source)
     at com.sap.dbtech.jdbc.CallableStatementSapDB.<init>(Unknown Source)
     at com.sap.dbtech.jdbc.ConnectionSapDB.prepareStatement(Unknown Source)
     at sk.nbs.database.Transaction.getPreparedStatement(Transaction.java:185)
     ... 30 more
Here is part of knldiag file from this time
2008-07-10 14:41:41      0xD3C     20019 Pager    First DataCacheSegment:62
2008-07-10 14:41:41      0xD3C     20018 Pager    Start TaskId: 6
2008-07-10 14:41:41      0xD3C     20019 Pager    First DataCacheSegment:63
2008-07-10 14:41:42      0xD3C        31 SrvTasks Permanently reserved 66 servertasks for 'Backup / Restore'.
2008-07-10 14:41:42      0xD3C        31 SrvTasks Permanently reserved 2 servertasks for 'Backup / Restore'.
2008-07-10 14:41:42      0xD3C        31 SrvTasks Permanently reserved 1 servertasks for 'Savepoint'.
2008-07-10 14:41:42      0x7AC         3 RunTime State changed from STARTING to ADMIN
2008-07-10 14:41:42      0x7AC     19601 DBSTATE SERVERDB is ready
============================================ begin of write cycle ==================
2008-07-15 13:45:27     0x13B8     19651 CONNECT Connection released, T493
2008-07-15 13:45:27     0x13B8     19677 CONNECT Client has released connection, T412
2008-07-15 13:45:27     0x13B8     19651 CONNECT Connection released, T412
2008-07-15 13:45:27     0x13B8     19677 CONNECT Client has released connection, T379
2008-07-15 13:45:27     0x13B8     19651 CONNECT Connection released, T379
2008-07-15 13:45:27     0x13B8     19677 CONNECT Client has released connection, T476
2008-07-15 13:45:27     0x13B8     19651 CONNECT Connection released, T476
2008-07-15 13:45:27      0xCF4     19677 CONNECT Client has released connection, T291
2008-07-15 13:45:27      0xCF4     19651 CONNECT Connection released, T291
2008-07-15 13:45:27      0xCF4     19677 CONNECT Client has released connection, T200
2008-07-15 13:45:27      0xCF4     19651 CONNECT Connection released, T200
2008-07-15 13:45:27      0xCF4     19677 CONNECT Client has released connection, T229
2008-07-15 13:45:27      0xCF4     19651 CONNECT Connection released, T229
2008-07-15 13:45:27      0xCF4     19677 CONNECT Client has released connection, T179
2008-07-15 13:45:27      0xCF4     19651 CONNECT Connection released, T179
2008-07-15 13:45:27      0xCF4     19677 CONNECT Client has released connection, T295
2008-07-15 13:45:27      0xCF4     19651 CONNECT Connection released, T295
2008-07-15 13:45:28     0x13B8     19633 CONNECT Connect req. (T413, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:28     0x13B8     19633 CONNECT Connect req. (T479, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:28     0x13B8     19651 CONNECT Connection released, T413
2008-07-15 13:45:28     0x13B8     19651 CONNECT Connection released, T479
2008-07-15 13:45:28     0x13B8     19633 CONNECT Connect req. (T500, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:28     0x13B8     19633 CONNECT Connect req. (T345, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:28     0x13B8     19651 CONNECT Connection released, T500
2008-07-15 13:45:28     0x13B8     19633 CONNECT Connect req. (T494, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:28     0x13B8     19651 CONNECT Connection released, T345
2008-07-15 13:45:28     0x13B8     19633 CONNECT Connect req. (T502, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:28     0x13B8     19651 CONNECT Connection released, T494
2008-07-15 13:45:28     0x13B8     19633 CONNECT Connect req. (T532, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:28     0x13B8     19651 CONNECT Connection released, T502
2008-07-15 13:45:28     0x13B8     19633 CONNECT Connect req. (T329, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:28     0x13B8     19651 CONNECT Connection released, T532
2008-07-15 13:45:28      0xCF4     19651 CONNECT Connection released, T308
2008-07-15 13:45:28     0x13B8     19651 CONNECT Connection released, T329
2008-07-15 13:45:28      0xCF4     19633 CONNECT Connect req. (T204, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:28     0x13B8     19633 CONNECT Connect req. (T373, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:28     0x13B8     19633 CONNECT Connect req. (T381, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:28     0x13B8     19651 CONNECT Connection released, T373
2008-07-15 13:45:28     0x13B8     19651 CONNECT Connection released, T381
2008-07-15 13:45:28     0x13B8     19633 CONNECT Connect req. (T438, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:28     0x13B8     19651 CONNECT Connection released, T438
2008-07-15 13:45:28     0x13B8     19633 CONNECT Connect req. (T474, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:28     0x13B8     19651 CONNECT Connection released, T474
2008-07-15 13:45:28     0x13B8     19633 CONNECT Connect req. (T482, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:28      0xCF4     19651 CONNECT Connection released, T204
2008-07-15 13:45:28     0x13B8     19651 CONNECT Connection released, T482
2008-07-15 13:45:28      0xCF4     19633 CONNECT Connect req. (T156, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:28     0x13B8     19633 CONNECT Connect req. (T486, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:28     0x13B8     19633 CONNECT Connect req. (T504, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:28     0x13B8     19651 CONNECT Connection released, T486
2008-07-15 13:45:28     0x13B8     19633 CONNECT Connect req. (T461, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:28     0x13B8     19651 CONNECT Connection released, T504
2008-07-15 13:45:28     0x13B8     19651 CONNECT Connection released, T461
2008-07-15 13:45:28     0x13B8     19633 CONNECT Connect req. (T356, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:28     0x13B8     19651 CONNECT Connection released, T356
2008-07-15 13:45:28     0x13B8     19633 CONNECT Connect req. (T516, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:28     0x13B8     19651 CONNECT Connection released, T516
2008-07-15 13:45:28     0x13B8     19633 CONNECT Connect req. (T462, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:28     0x13B8     19633 CONNECT Connect req. (T420, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:29      0xCF4     19633 CONNECT Connect req. (T253, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:29      0xCF4     19651 CONNECT Connection released, T253
2008-07-15 13:45:29      0xCF4     19633 CONNECT Connect req. (T220, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:29     0x13B8     19633 CONNECT Connect req. (T432, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:29      0xCF4     19633 CONNECT Connect req. (T244, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:29     0x13B8     19651 CONNECT Connection released, T432
2008-07-15 13:45:29     0x13B8     19633 CONNECT Connect req. (T441, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:29      0xCF4     19651 CONNECT Connection released, T244
2008-07-15 13:45:29     0x13B8     19651 CONNECT Connection released, T462
2008-07-15 13:45:29     0x13B8     19651 CONNECT Connection released, T420
2008-07-15 13:45:29     0x13B8     19633 CONNECT Connect req. (T442, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:29     0x13B8     19651 CONNECT Connection released, T442
2008-07-15 13:45:29     0x13B8     19633 CONNECT Connect req. (T561, Node:'sipseu-nbslsc1', PID:0)
2008-07-15 13:45:29     0x13B8     19651 CONNECT Connection released, T561
Can you help me with this error?

Hi Juraj,
this looks like a network issue.
Anyhow - you should also consider to install the current patch 7.6.03 available here from SDN Downloadarea.
regards,
Lars

I bought an external hard drive for backups to use with Time Machine, but however when I try to connect it with the other windows laptop it doesn't work ? intact it doesn't work on any other device except my MAC ?

I bought an external hard drive for backups to use with Time Machine, but however when I try to connect it with the other windows laptop it doesn't work ? intact it doesn't work on any other device except my MAC ?

Do not worry about it.
Time Machine needs that your external drive is formatted in HFS+, or better known as "Mac OS Extended (Journaled)". This filesystem is used by Apple on Macs and Windows cannot read or write drives formatted with this filesystem, being this the reason why all your devices do not read the external drive except your Mac.
You can only use your external drive to make Time Machine drives. If you store anything different, you may damage the Time Machine structure, so it is better not to use it as a drive to store other data. Instead, get another external drive to do it or create a second partition on the external drive formatted in FAT32 by using Disk Utility > http://pondini.org/OSX/DU3.html FAT32 can be read by Windows PCs

Recurring Page Exception - 'SocketException: Connection reset by peer'

I have implemented a popup calendar that is implemented as an include of a file in a lower directory (i.e. 'script/calendar.jsp') that uses an iframe. This calendar is only in a few of my pages, but I get the below exception in each page which implements it.
Is this happening after the page is sent? It's after the afterRenderResponse() method. Any thoughts? Thanks.
[#|2005-06-30T21:44:37.593-0500|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web
     |_ThreadID=19;|org.apache.catalina.core.StandardHostValve@1a70476: Exception Processing ErrorPage[errorCode=404, location=/faces/error.jsp]
     ClientAbortException: java.net.SocketException: Software caused connection abort: socket write error
     at org.apache.coyote.tomcat5.OutputBuffer.realWriteBytes(OutputBuffer.java:378)
     at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:401)
     at org.apache.coyote.tomcat5.OutputBuffer.doFlush(OutputBuffer.java:320)
     at org.apache.coyote.tomcat5.OutputBuffer.flush(OutputBuffer.java:302)
     at org.apache.coyote.tomcat5.CoyoteResponse.flushBuffer(CoyoteResponse.java:512)
     at org.apache.coyote.tomcat5.CoyoteResponseFacade$1.run(CoyoteResponseFacade.java:212)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.coyote.tomcat5.CoyoteResponseFacade.flushBuffer(CoyoteResponseFacade.java:207)
     at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:306)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:133)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:539)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.security.web.SingleSignOn.invoke(SingleSignOn.java:254)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.web.VirtualServerValve.invoke(VirtualServerValve.java:209)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:114)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at com.sun.enterprise.web.VirtualServerMappingValve.invoke(VirtualServerMappingValve.java:166)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:936)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:165)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:683)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:604)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:542)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:647)
     at java.lang.Thread.run(Thread.java:534)References: http://forum.java.sun.com/thread.jspa?messageID=3767674&#56698;

Hi,
Please go throught the following link:
http://www.websina.com/bugzero/errors/http-connection-reset.html
Hope this helps
Cheers
Giri :-)

Destroying connection that is not valid, due to the following exception [com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset]

Hi everyone,
I'm facing the following problem in a Server runing Linux with JBoss AS 4.2.2, JRE 1.6, and MSSQL Server 2005 with JDBC 2.0 (sqljdbc4.jar).
The thing is: on friday morning I started up the server and everything worked fine ... next, from Friday at 6pm to Saturday at 8am nobody has used the system.
Then on Saturday at 8:05 got the following warning lines every time I tried to do something in my application. While it seems that everything works, after a few days the system starts to decrease their performance and malfunction, so I want to know why it
might happen these warnings.
I have tried to find a solution to this problem in several places but I'm not succeeding. That's why I'm writing my problem here...
Hope somebody can help me!
Thanks in advance and best regards!
Cristian.
This is the "error" log.
2011-06-11 08:05:29,680 WARN [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Destroying connection that is not valid, due to the following exception: ConnectionID:2941
com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1352)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1339)
at com.microsoft.sqlserver.jdbc.TDSChannel.read(IOBuffer.java:1654)
at com.microsoft.sqlserver.jdbc.TDSReader.readPacket(IOBuffer.java:3694)
at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.java:5022)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:773)
at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:676)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:4575)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1400)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:179)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:154)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(SQLServerStatement.java:649)
at org.jboss.resource.adapter.jdbc.CheckValidConnectionSQL.isValidConnection(CheckValidConnectionSQL.java:58)
at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:435)
at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkValid(BaseWrapperManagedConnection.java:231)
at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.matchManagedConnections(LocalManagedConnectionFactory.java:200)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:211)
at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:538)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:341)
at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:315)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:396)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:842)
at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88)
at org.hibernate.connection.DatasourceConnectionProvider.getConnection(DatasourceConnectionProvider.java:69)
at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:423)
at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:144)
at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:139)
at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1547)
at org.hibernate.loader.Loader.doQuery(Loader.java:673)
at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236)
at org.hibernate.loader.Loader.doList(Loader.java:2220)
And this is my mssql-ds.xml
<local-tx-datasource>
<jndi-name>jdbc/bpmsdb</jndi-name>
<connection-url>jdbc:sqlserver://ipaddress:1433;DatabaseName=BPMS</connection-url>
<driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
<user-name>user</user-name>
<password>pwd</password>
<min-pool-size>5</min-pool-size>
<max-pool-size>50</max-pool-size>
<exception-sorter-class-name>
org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter
</exception-sorter-class-name>
<metadata>
<type-mapping>MS SQLSERVER2000</type-mapping>
</metadata>
<new-connection-sql>select 1</new-connection-sql>
<check-valid-connection-sql>select 1</check-valid-connection-sql>
<idle-timeout-minutes>5</idle-timeout-minutes>
</local-tx-datasource>

I´m facing similar problem with Linux and SQL Server 2008 R2. I made the downgrade of JDK 1.6 from 27 to 26 (some people reporting errors when upgraded to jdk1.6_29 and rolling back is ok) but for me the error persists. At this moment we are testing with
sqljdbc4.jar version 4.0 (released in 3/6/2012). The curious I have two equals Linux boxes and only one have presented connection reset errors.
Thanks in advance.
Carlos

My RMI Server application Not work under Linux: Exception: Connection reset

Under Red Hat Linux 8.0 my RMI server application, when I try to bind the Impl class, sends me the exception:
"java.rmi.UnmarshalException: Error unmarshaling return header;
nested exception is: java.net.SocketException: Connection reset".
And it works under Windows 2000 without any problem.
What could it be?
Many thanks,
Ales.

Hi Ales,
Try to change your /etc/hosts file, and change the line that says :
127.0.0.1 MDK localhost.localdomain localhost
(where MDK is the machine's name).
Remove MDK from this line and add a new one mapping it to a 'real' outside IP address, visible (check firewall!!!) to the network from where you are approaching the Linux Box
Good luck,
Aart

"Connection reset by peer" exceptions in JDBC

I wonder if someone from Oracle JDBC development can answer the issues raised in
this posting.
component: Oracle JDBC Thin Driver
component version: 8.1.6
rdbms version: 8.1.5.
Summary of problem:
A long running application that opens JDBC connections and holds them for the lifetime of the application gets SQLExceptions with a "connection reset" message when attempting to reuse a connection that has been idle for a long period of time.
( The exact period is not determinable from Oracle documentation).
We need to handle this exception and open a new connection when this happens.
The problem is how do we determine when this exception has happened when we
catch a SQLException. Our software is internationalized and we cant interrogate
the message text to match for "connection reset by peer".
The ideal way to do this is for Oracle to throw a subclass of SQLException or to
use a error code that is unique for the "connection reset by peer" case.
The following is a summary of the items in this message
1. Oracle should document when the software throws away open connections.
2. Provide documented support for handling the above SQLException in
a language independent manner.
3. The method isClosed() on class Connection should return true once the
connection is rendered unusable for whatever reason ( as per the JDBC specification).
4. The Oracle JDBC drivers should include a retry mechanism on socket errors.
( We dont know that whether the connection is reset by the server or if the
client just gives up once it gets any socket error).
business need:
long running applications have no documented way of detecting when a connection has been discarded by the Oracle Server.
null

The FAQ does not answer our problem as
it is not a server problem. The
support person for the Server group
asked me to look through the Alrt.log file
for the database and there were no entries
for that time.
Our application has multiple threads, each having its own connection to the database, some inactive threads seem to lose their database connection. We use a driver from a third-party vendor going against SQLServer in the same network and that does not fail in this manner.
The above seems to rule out
1. server problems ( no, the problem is not
happening on the first connection, but
after the connection has been in use for
a long time).
2. network problems. ( the other driver is
functioning reliably ).
I believe that the driver may be giving up
fairly early in the retry process.
The only way that we know to deal with the
problem is as follows:
1. when a SQLException is caught, we dont
know that the connection has been reset.
( we dont want to interrograte the
message string as it will not work
in other language environments).
2. we just ping the connection to the server
( use a simple call to set the transaction
isolation level). If this fails, we
assume that the connection has been reset. ( Of course, we would prefer a simpler
way like checking whether the connection
has been closed).
Conclusions:
1. We feel that connections should not be
lost in this manner.
2. The connection loss should be detectable
in a much more reliable manner than the
hack we use.

Connection Reset exception received in Windows only

Similar Messages

Maybe you are looking for