Connection reset by peer : Socket write

Hi, everybody
I am working with weblogic5.1 with servicepack 8. Our server is running for
24X7X365 but i got some weired error this morning saying that "IO Exception
:Connection reset by peer : Socket write
error". I believe this has to do with weblogic.
Can somebody guide me on this issue.
Any help would be appreciated.
Thanks
Gautam

Pretty difficult to track such kind of things if it is not easily
reproducible. Could you also try it out with SP9? Also, try posting it
on the JDBC newsgroup. Maybe, Joe Weinstein might have more answers.
Shiva.
"G.........." wrote:
LoggingService is one of class that calls db methods.well, we get
connection from pool and return it pool .we are refreshing connection
pool regularly, following is some of the entries in properties
file initialCapacity=5,\
maxCapacity=10,\
capacityIncrement=1,\
allowShrinking=true,\
shrinkPeriodMins=15,\
refreshMinutes=10,\ No this message is not easily
reproductible.JDK version 1.2.2 and os is windows NT4.0 ThanksGautam
"Shiva Paranandi" <[email protected]> wrote in message
news:[email protected] does this
"com.gdaxs.util.LoggingService.logSystemErrorMsg" do? How is
your pool usage? Do you use the connection pools for a long
time? Also, can you check if this happens after a pool
refresh or not? Is this message easily reproducable? What is
the jdk version you are using and what OS?
Shiva.
"G.........." wrote:
Here is complete stack trace.
Io exception: Connection reset by peer: JVM_recv in socket
input stream read
Stack trace:
java.sql.SQLException: Io exception: Connection reset by
peer: JVM_recv in socket input stream read
at
com.gdaxs.util.LoggingService.logSystemErrorMsg(LoggingService.java:309)
at
com.gdaxs.DBManager.DataRetrieverBean.getCloseOrders(DataRetrieverBean.java:2208)
at
com.gdaxs.DBManager.DataRetrieverBeanEOImpl.getCloseOrders(DataRetrieverBeanEOImpl.java:2656)
at
com.gdaxs.DBManager.DataRetrieverBeanEOImpl_ServiceStub.getCloseOrders(DataRetrieverBeanEOImpl_ServiceStub.java:343)
at
com.gdaxs.closedOrdersBean.init(closedOrdersBean.java:95)
at
jsp_servlet._closedorders._jspService(_closedorders.java:236)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
at
weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
and after it series of exception like below
Io exception: Connection reset by peer: socket write error
Stack trace:
java.sql.SQLException: Io exception: Connection reset by
peer: socket write error
at
com.gdaxs.util.LoggingService.logSystemErrorMsg(LoggingService.java:309)
at
com.gdaxs.traderadministrator.LDAPInterfaceBean.getTradingAccounts(LDAPInterfaceBean.java:285)
at
com.gdaxs.traderadministrator.LDAPInterfaceBean.getTraderCredentials(LDAPInterfaceBean.java:137)
at
com.gdaxs.traderadministrator.LDAPInterfaceBeanEOImpl.getTraderCredentials(LDAPInterfaceBeanEOImpl.java:99)
at
com.gdaxs.traderadministrator.LDAPInterfaceBeanEOImpl_ServiceStub.getTraderCredentials(LDAPInterfaceBeanEOImpl_ServiceStub.java:109)
at
com.gdaxs.traderadministrator.TraderAdministrator.onMessage(TraderAdministrator.java:278)
at
progress.message.jclient.Session.ew_(progress/message/jclient/Session.java)
at
progress.message.jclient.QueueSession.run(progress/message/jclient/QueueSession.java)
at
progress.message.jclient.sl.run(progress/message/jclient/Session$SessionThread.java)
Thanks
Gautam"Shiva Paranandi" <[email protected]> wrote in
message news:[email protected]...> Could you
post the entire exception?
Shiva.
"G.........." wrote:
Hi, everybody
I am working with weblogic5.1 with servicepack 8. Our
server is running for
24X7X365 but i got some weired error this morningsaying that "IO Exception
:Connection reset by peer : Socket write
error". I believe this has to do with weblogic.
Can somebody guide me on this issue.
Any help would be appreciated.
Thanks
Gautam
[att1.html]

Similar Messages

JCOM throwing SocketException: Connection reset by peer: socket write error

I have an ejb which is calling a simple ActiveX component using JCOM.
Ocassionally the ejb loses the ability to connect to the ActiveX component. Any attempt to call a method results in a java.net.SocketException: Connection reset by peer: socket write error.
However the ActiveX component continues to run correctly. I can still connect to it using a vb test client. This is using com to connect, not DCOM as used by JCOM(JIntegra).
The application server and the ActiveX component are running on the same server.
Any suggestions as to why the JIntegra DCOM request could be failing?
Thanks,
Greg.

I have an ejb which is calling a simple ActiveX component using JCOM.
Ocassionally the ejb loses the ability to connect to the ActiveX component. Any attempt to call a method results in a java.net.SocketException: Connection reset by peer: socket write error.
However the ActiveX component continues to run correctly. I can still connect to it using a vb test client. This is using com to connect, not DCOM as used by JCOM(JIntegra).
The application server and the ActiveX component are running on the same server.
Any suggestions as to why the JIntegra DCOM request could be failing?
Thanks,
Greg.

Connection reset by peer: socket write error

Anybody can help me?
I run vdbench to test our NAS server, but it always failed with "
Slave localhost-0 aborting: Error writing file Y:\dir11\vdb.1_2.dir\vdb.2_2.dir\vdb.3_1.dir\vdb.4_1.dir\vdb.5_2.dir\vdb.6_2.dir\vdb.7_1.dir\vdb.8_2.dir\vdb.9_2.dir\vdb.10_1.dir\vdb_f0001.file
Error: Windows System Error code: 64: ", how to solve this fail ?
conf file:
fsd=fsd,anchor=Y:\dir,count=(11,15),depth=10,width=2,files=1,size=(10k,20,100k,20,160k,20,8m,20,10m,10,1g,5,2g,5)
fwd=fwd1,fsd=(fsd11,fsd12,fsd13,fsd14,fsd15),rdpct=85,xfersize=(10k,22,100k,22,160k,22,8m,22,10m,12),fileio=random,fileselect=random,threads=5
rd=rd1,fwd=fwd1,operations=read,fwdrate=max,format=yes,elapsed=10,interval=1
logfile.html:
14:22:49.510 Vdbench distribution: vdbench50401
14:22:49.510
14:22:49.526 input argument scanned: '-fcifs'
14:22:49.526 java.vendor Sun Microsystems Inc.
14:22:49.526 java.home C:\Program Files\Java\jre6
14:22:49.526 java.vm.specification.version 1.0
14:22:49.526 java.vm.version 16.3-b01
14:22:49.526 java.vm.vendor Sun Microsystems Inc.
14:22:49.526 java.specification.version 1.6
14:22:49.526 java.class.version 50.0
14:22:49.526 user.name zcuser1002
14:22:49.526 user.dir C:\Users\zcuser1002\Desktop\Y-vdbench-1021
14:22:49.526 java.class.path C:\Users\zcuser1002\Desktop\Y-vdbench-1021\;C:\Users\zcuser1002\Desktop\Y-vdbench-1021\classes;C:\Users\zcuser1002\Desktop\Y-vdbench-1021\vdbench.jar
14:22:49.526 os.name Windows Server 2008 R2
14:22:49.526 os.arch amd64
14:22:49.526 os.version 6.1
14:22:49.526 sun.arch.data.model 64
14:22:49.557 'fsd=fsd,count=(start,count)' added fsd11 Y:\dir11
15:08:57.031 2704 0.0 0.00 0.9 4.42 0.0 0.0 0.00 0.0 0.00 0.00 0.00 0.00 0 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00
15:08:58.030 2705 343.0 386.6 8.5 4.36 0.0 0.0 0.00 343.0 386.6 0.00 42.22 42.22 129071 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00
15:08:59.031 2706 15.0 983.4 0.0 3.41 0.0 0.0 0.00 15.0 983.4 0.00 1.85 1.85 129160 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00
15:09:51.406 localhost-0: anchor=Y:\dir15: Created 420 of 1024 files (41.02%)
15:10:02.202 2707 12143 31.35 8.0 6.25 0.0 0.0 0.00 12143 31.35 0.00 1513 1513.9 130736 0.0 0.00 0.0 0.00 65.0 59795 65.0 202.8 67.0 44969 0.0 0.00 0.0 0.00 0.0 0.00
15:10:02.234 2708 0.0 0.00 8.6 8.40 0.0 0.0 0.00 0.0 0.00 0.00 0.00 0.00 0 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00
15:10:02.249 2709 0.0 0.00 43.7 37.5 0.0 0.0 0.00 0.0 0.00 0.00 0.00 0.00 0 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 27.0 4268 0.0 0.00 0.0 0.00 0.0 0.00
15:10:02.265 2710 0.0 0.00 0.0 0.00 0.0 0.0 0.00 0.0 0.00 0.00 0.00 0.00 0 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00
15:10:02.296 2711 0.0 0.00 100.0 81.2 0.0 0.0 0.00 0.0 0.00 0.00 0.00 0.00 0 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00
15:10:02.312 2712 0.0 0.00 0.0 0.00 0.0 0.0 0.00 0.0 0.00 0.00 0.00 0.00 0 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00
15:10:02.312 localhost-0: 15:10:02.218 op: write lun: Y:\dir11\vdb.1_2.dir\vdb.2_2.dir\vdb.3_1.dir\vdb.4_1.dir\vdb.5_2.dir\vdb.6_2.dir\vdb.7_1.dir\vdb.8_2.dir\vdb.9_2.dir\vdb.10_1.dir\vdb_f0001.file lba: 1484652544 0x587E0000 xfer: 131072 errno: Windows System Error code: 64: ??¡§????????????
15:10:02.327 localhost-0: 15:10:02.234 op: write lun: Y:\dir14\vdb.1_2.dir\vdb.2_2.dir\vdb.3_1.dir\vdb.4_1.dir\vdb.5_2.dir\vdb.6_2.dir\vdb.7_1.dir\vdb.8_2.dir\vdb.9_2.dir\vdb.10_1.dir\vdb_f0001.file lba: 1971847168 0x75880000 xfer: 131072 errno: Windows System Error code: 64: ??¡§????????????
15:10:02.343 2713 0.0 0.00 100.0 74.9 0.0 0.0 0.00 0.0 0.00 0.00 0.00 0.00 0 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00 0.0 0.00
15:10:02.343
15:10:02.343 **********************************************************
15:10:02.343 Slave localhost-0 aborting: Error writing file Y:\dir11\vdb.1_2.dir\vdb.2_2.dir\vdb.3_1.dir\vdb.4_1.dir\vdb.5_2.dir\vdb.6_2.dir\vdb.7_1.dir\vdb.8_2.dir\vdb.9_2.dir\vdb.10_1.dir\vdb_f0001.file
Error: Windows System Error code: 64: ??¡§????????????
lba: 1484652544
xfersize: 131072
blocks_done: 11327
bytes_done: 1484652544
open_for_read: false
15:10:02.343 **********************************************************
15:10:02.343
15:10:18.013 Exception from slave: localhost-0
15:10:18.013
15:10:18.013 common.failure():
java.net.SocketException: Connection reset by peer: socket write error
java.net.SocketException: Connection reset by peer: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(Unknown Source)
at java.net.SocketOutputStream.write(Unknown Source)
at java.io.ObjectOutputStream$BlockDataOutputStream.drain(Unknown Source)
at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(Unknown Source)
at java.io.ObjectOutputStream.reset(Unknown Source)
at Vdb.SlaveSocket.putMessage(SlaveSocket.java:277)
at Vdb.CollectSlaveStats.<init>(CollectSlaveStats.java:121)
at Vdb.Reporter.run(Reporter.java:183)
localhost-0.stdout.html:
stdout/stderr for slave=localhost-0
14:22:50.072 14:22:50.072 SlaveJvm execution parameter: '-m localhost'
14:22:50.072 14:22:50.072 SlaveJvm execution parameter: '-n localhost-10-141104-14.22.49.432'
14:22:50.072 14:22:50.072 SlaveJvm execution parameter: '-l localhost-0'
14:22:50.072 14:22:50.072 SlaveJvm execution parameter: '-p 5570'
14:22:50.072 14:22:50.072 SlaveJvm positional parameter: 'SlaveJvm'
14:22:50.118 14:22:50.118 successfully connected to master localhost
14:22:50.118 14:22:50.118 Connection to localhost using port 5570 successful
14:22:50.571 14:22:50.571 execute(): ls -l Y:\dir11
14:22:50.618 14:22:50.618 execute(): ls -l Y:\dir12
14:22:50.633 14:22:50.633 execute(): ls -l Y:\dir13
14:22:50.664 14:22:50.664 execute(): ls -l Y:\dir14
14:22:50.680 14:22:50.680 execute(): ls -l Y:\dir15
14:22:50.711 14:22:50.711 Configuration interpretation took 0.45 seconds
Link to Run Definitions: <A HREF="#_225912260">format_for_rd1 For loops: None</A>
 <A HREF="#_156265924">rd1 For loops: None</A>
14:22:50.852 14:22:50.852 Beginning of run setup
14:22:50.852 14:22:50.852 **********************
14:22:50.852
14:22:50.852
14:22:51.538 14:22:51.538 Completed the creation of the directory list for Y:\dir11: 2046 directories.
14:22:56.811 14:22:56.811 Memory total Java heap: 77.438 MB; Free: 32.782 MB; Used: 44.655 MB;
14:22:56.874 14:22:56.874 checkMemory()
14:22:56.874 14:22:56.874 Memory total Java heap: 77.438 MB; Free: 52.364 MB; Used: 25.074 MB;
14:23:03.426 14:23:03.426 Generated 1024 file names; total anchor size: 130.841g
14:23:03.426 14:23:03.426 Writing control file for anchor=Y:\dir11 at start of run.
14:23:03.457 14:23:03.441 Completed control file for anchor=Y:\dir11 at start of run. dirs: 2046/2046 files: 1024/88 sizes: 130.841g/8.721g/0/0.0
14:23:03.457 14:23:03.441 During anchor creation for anchor=Y:\dir11 there were 2046 directories and 88 files
14:23:03.551 14:23:03.551 Completed the creation of the directory list for Y:\dir12: 2046 directories.
14:23:08.902 14:23:08.902 Memory total Java heap: 77.438 MB; Free: 24.149 MB; Used: 53.288 MB;
14:23:08.964 14:23:08.964 checkMemory()
14:23:08.964 14:23:08.964 Memory total Java heap: 77.438 MB; Free: 50.640 MB; Used: 26.798 MB;
14:23:15.579 14:23:15.579 Generated 1024 file names; total anchor size: 130.841g
14:23:15.579 14:23:15.579 Writing control file for anchor=Y:\dir12 at start of run.
14:23:15.594 14:23:15.594 Completed control file for anchor=Y:\dir12 at start of run. dirs: 2046/2046 files: 1024/74 sizes: 130.841g/7.092g/0/0.0
14:23:15.594 14:23:15.594 During anchor creation for anchor=Y:\dir12 there were 2046 directories and 74 files
14:23:15.688 14:23:15.688 Completed the creation of the directory list for Y:\dir13: 2046 directories.
14:23:21.210 14:23:21.210 Memory total Java heap: 74.688 MB; Free: 19.725 MB; Used: 54.963 MB;
14:23:21.273 14:23:21.273 checkMemory()
14:23:21.273 14:23:21.273 Memory total Java heap: 76.562 MB; Free: 48.176 MB; Used: 28.386 MB;
14:23:28.168 14:23:28.168 Generated 1024 file names; total anchor size: 130.841g
14:23:28.168 14:23:28.168 Writing control file for anchor=Y:\dir13 at start of run.
14:23:28.184 14:23:28.184 Completed control file for anchor=Y:\dir13 at start of run. dirs: 2046/2046 files: 1024/84 sizes: 130.841g/8.886g/0/0.0
14:23:28.184 14:23:28.184 During anchor creation for anchor=Y:\dir13 there were 2046 directories and 84 files
14:23:28.262 14:23:28.262 Completed the creation of the directory list for Y:\dir14: 2046 directories.
14:23:33.785 14:23:33.785 Memory total Java heap: 74.250 MB; Free: 17.213 MB; Used: 57.037 MB;
14:23:33.863 14:23:33.863 checkMemory()
14:23:33.863 14:23:33.863 Memory total Java heap: 72.812 MB; Free: 42.829 MB; Used: 29.983 MB;
14:23:40.976 14:23:40.976 Generated 1024 file names; total anchor size: 130.841g
14:23:40.976 14:23:40.976 Writing control file for anchor=Y:\dir14 at start of run.
14:23:40.976 14:23:40.976 Completed control file for anchor=Y:\dir14 at start of run. dirs: 2046/2046 files: 1024/87 sizes: 130.841g/8.778g/0/0.0
14:23:40.976 14:23:40.976 During anchor creation for anchor=Y:\dir14 there were 2046 directories and 87 files
14:23:41.054 14:23:41.054 Completed the creation of the directory list for Y:\dir15: 2046 directories.
14:23:46.296 14:23:46.296 Memory total Java heap: 74.062 MB; Free: 42.390 MB; Used: 31.672 MB;
14:23:46.374 14:23:46.374 checkMemory()
14:23:46.374 14:23:46.374 Memory total Java heap: 101.000 MB; Free: 68.809 MB; Used: 32.191 MB;
14:23:52.958 14:23:52.958 Generated 1024 file names; total anchor size: 130.841g
14:23:52.958 14:23:52.958 Writing control file for anchor=Y:\dir15 at start of run.
14:23:52.989 14:23:52.973 Completed control file for anchor=Y:\dir15 at start of run. dirs: 2046/2046 files: 1024/96 sizes: 130.841g/8.995g/0/0.0
14:23:52.989 14:23:52.973 During anchor creation for anchor=Y:\dir15 there were 2046 directories and 96 files
14:23:52.989 14:23:52.973 Skew for fwd=format,fsd=fsd11,operation=read: 20.0
14:23:52.989 14:23:52.973 Skew for fwd=format,fsd=fsd12,operation=read: 20.0
14:23:52.989 14:23:52.973 Skew for fwd=format,fsd=fsd13,operation=read: 20.0
14:23:52.989 14:23:52.973 Skew for fwd=format,fsd=fsd14,operation=read: 20.0
14:23:52.989 14:23:52.973 Skew for fwd=format,fsd=fsd15,operation=read: 20.0
14:23:53.051 14:23:53.051 Started 8 threads for fwd=format,fsd=fsd11
14:23:53.114 14:23:53.114 Started 8 threads for fwd=format,fsd=fsd12
14:23:53.161 14:23:53.161 Started 8 threads for fwd=format,fsd=fsd13
14:23:53.207 14:23:53.207 Started 8 threads for fwd=format,fsd=fsd14
14:23:53.270 14:23:53.270 Started 8 threads for fwd=format,fsd=fsd15
14:23:53.270 14:23:53.270 Started 40 FwgThreads
14:23:53.270 14:23:53.270 Waiting for task synchronization
14:23:53.270 14:23:53.270 task_wait_start_complete() end
<a name="_225912260"></a>14:23:53.971 Starting RD=format_for_rd1
14:23:54.002 14:23:54.002 task_run_all(): 41 tasks
14:23:54.051 14:23:54.051 Message to master: anchor=Y:\dir15 mkdir complete.
14:23:54.051 14:23:54.051 Message to master: anchor=Y:\dir11 mkdir complete.
14:23:54.051 14:23:54.051 Message to master: anchor=Y:\dir13 mkdir complete.
14:23:54.066 14:23:54.066 Message to master: anchor=Y:\dir14 mkdir complete.
14:23:54.066 14:23:54.066 Message to master: anchor=Y:\dir12 mkdir complete.
14:24:24.685 14:24:24.685 Message to master: anchor=Y:\dir14: Created 130 of 1024 files (12.70%)
14:24:56.311 14:24:56.311 Message to master: anchor=Y:\dir12: Created 130 of 1024 files (12.70%)
14:25:40.473 14:25:40.464 Message to master: anchor=Y:\dir13: Created 140 of 1024 files (13.67%)
14:32:52.125 14:32:52.125 Message to master: anchor=Y:\dir12: Created 140 of 1024 files (13.67%)
14:33:30.374 14:33:30.374 Message to master: anchor=Y:\dir12: Created 160 of 1024 files (15.63%)
14:34:33.842 14:34:33.842 Message to master: anchor=Y:\dir14: Created 170 of 1024 files (16.60%)
14:35:49.810 14:35:49.810 Message to master: anchor=Y:\dir14: Created 180 of 1024 files (17.58%)
14:36:34.451 14:36:34.451 Message to master: anchor=Y:\dir14: Created 190 of 1024 files (18.55%)
14:38:13.437 14:38:13.437 Message to master: anchor=Y:\dir14: Created 200 of 1024 files (19.53%)
14:39:01.966 14:39:01.966 Message to master: anchor=Y:\dir11: Created 210 of 1024 files (20.51%)
14:39:57.837 14:39:57.837 Message to master: anchor=Y:\dir15: Created 220 of 1024 files (21.48%)
14:41:51.763 14:41:51.763 Message to master: anchor=Y:\dir13: Created 220 of 1024 files (21.48%)
14:42:31.156 14:42:31.156 Message to master: anchor=Y:\dir14: Created 240 of 1024 files (23.44%)
14:45:32.607 14:45:32.607 Message to master: anchor=Y:\dir15: Created 260 of 1024 files (25.39%)
14:46:44.611 14:46:44.611 Message to master: anchor=Y:\dir11: Created 270 of 1024 files (26.37%)
14:47:53.707 14:47:53.707 Message to master: anchor=Y:\dir14: Created 280 of 1024 files (27.34%)
14:48:25.032 14:48:25.032 Message to master: anchor=Y:\dir12: Created 280 of 1024 files (27.34%)
14:48:56.946 14:48:56.946 Message to master: anchor=Y:\dir13: Created 290 of 1024 files (28.32%)
14:50:40.869 14:50:40.868 Message to master: anchor=Y:\dir11: Created 300 of 1024 files (29.30%)
14:51:22.062 14:51:22.062 Message to master: anchor=Y:\dir15: Created 330 of 1024 files (32.23%)
14:53:55.390 14:53:55.390 Message to master: anchor=Y:\dir14: Created 350 of 1024 files (34.18%)
14:56:20.897 14:56:20.897 Message to master: anchor=Y:\dir14: Created 360 of 1024 files (35.16%)
14:58:08.513 14:58:08.513 Message to master: anchor=Y:\dir11: Created 360 of 1024 files (35.16%)
14:59:34.933 14:59:34.933 Message to master: anchor=Y:\dir12: Created 360 of 1024 files (35.16%)
15:02:15.234 15:02:15.234 Message to master: anchor=Y:\dir13: Created 370 of 1024 files (36.13%)
15:02:48.482 15:02:48.482 Message to master: anchor=Y:\dir14: Created 380 of 1024 files (37.11%)
15:04:27.359 15:04:27.359 Message to master: anchor=Y:\dir13: Created 380 of 1024 files (37.11%)
15:05:57.406 15:05:57.406 Message to master: anchor=Y:\dir15: Created 390 of 1024 files (38.09%)
15:07:18.982 15:07:18.982 Message to master: anchor=Y:\dir11: Created 390 of 1024 files (38.09%)
15:08:15.419 15:08:15.419 Message to master: anchor=Y:\dir11: Created 410 of 1024 files (40.04%)
15:08:50.624 15:08:50.624 Message to master: anchor=Y:\dir13: Created 410 of 1024 files (40.04%)
15:09:51.406 15:09:51.406 Message to master: anchor=Y:\dir15: Created 420 of 1024 files (41.02%)
15:10:02.202 15:10:02.202 file_write error2: 64
15:10:02.202 15:10:02.202 file_write error2: 64
15:10:02.202 15:10:02.202 handle: 0000000000000B38
15:10:02.202 15:10:02.202 seek: 0000000075880000
15:10:02.202 15:10:02.202 handle: 0000000000000BC0
15:10:02.202 15:10:02.202 length: 0000000000020000
15:10:02.202 15:10:02.202 seek: 00000000587E0000
15:10:02.202 15:10:02.202 buffer: 0000000034430000
15:10:02.202 15:10:02.202 length: 0000000000020000
15:10:02.202 15:10:02.202 buffer: 000000002E3E0000
15:10:02.234 15:10:02.234
15:10:02.234 15:10:02.234 Error writing file Y:\dir11\vdb.1_2.dir\vdb.2_2.dir\vdb.3_1.dir\vdb.4_1.dir\vdb.5_2.dir\vdb.6_2.dir\vdb.7_1.dir\vdb.8_2.dir\vdb.9_2.dir\vdb.10_1.dir\vdb_f0001.file
15:10:02.234 15:10:02.234 Error: Windows System Error code: 64: ??¡§????????????
15:10:02.234 15:10:02.234 lba: 1484652544
15:10:02.234 15:10:02.234 xfersize: 131072
15:10:02.234 15:10:02.234 blocks_done: 11327
15:10:02.234 15:10:02.234 bytes_done: 1484652544
15:10:02.234 15:10:02.234 open_for_read: false
15:10:02.234 15:10:02.234
15:10:02.234 java.lang.RuntimeException: Error writing file Y:\dir11\vdb.1_2.dir\vdb.2_2.dir\vdb.3_1.dir\vdb.4_1.dir\vdb.5_2.dir\vdb.6_2.dir\vdb.7_1.dir\vdb.8_2.dir\vdb.9_2.dir\vdb.10_1.dir\vdb_f0001.file
15:10:02.234 Error: Windows System Error code: 64: ??¡§????????????
15:10:02.234 lba: 1484652544
15:10:02.234 xfersize: 131072
15:10:02.234 blocks_done: 11327
15:10:02.234 bytes_done: 1484652544
15:10:02.234 open_for_read: false
15:10:02.234 at Vdb.common.failure(common.java:308)
15:10:02.234 at Vdb.ActiveFile.writeError(ActiveFile.java:611)
15:10:02.234 at Vdb.ActiveFile.writeBlock(ActiveFile.java:458)
15:10:02.234 at Vdb.FwgThread.doSequentialWrite(FwgThread.java:327)
15:10:02.234 at Vdb.OpCreate.doOperation(OpCreate.java:51)
15:10:02.234 at Vdb.OpFormat.doOperation(OpFormat.java:91)
15:10:02.234 at Vdb.FwgThread.run(FwgThread.java:157)

'Socket write error' is merely the master finding out that the slave aborted unexpectedly.
It it the '64' you have to worry about.
Windows system error code 64:
(It appears that the Vdbench translation from number to text may have some language issues and therefore can not properly print it).
ERROR_NETNAME_DELETED
64 (0x40)
The specified network name is no longer available.

Connection reset by peer.

I recently started getting following exception. I use Windows 2000
          with weblogic 5.1 service pack 12. This problem does not effect the
          functionality, and happens randomly.
          Thank you,
          berker(at)optonline.net
          java.net.SocketException: Connection reset by peer: socket write error
               at java.net.SocketOutputStream.socketWrite(Native Method)
               at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
               at weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:88)
               at weblogic.servlet.internal.ResponseHeaders.writeHeaders(ResponseHeaders.java:336)
               at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:603)
               at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:101)
               at weblogic.servlet.internal.ServletOutputStreamImpl.writeStream(ServletOutputStreamImpl.java:430)
               at weblogic.servlet.FileServlet.sendFile(FileServlet.java:199)
               at weblogic.servlet.FileServlet.service(FileServlet.java:56)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:105)
               at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:742)
               at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:686)
               at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:247)
               at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
               at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)


Looks like the browser user is closing the browser or moving on to a new url before the response comes back.
          Search the newsgroup, as there are a number of posts concerning this.
          Bill
          berker wrote:
          > I recently started getting following exception. I use Windows 2000
          > with weblogic 5.1 service pack 12. This problem does not effect the
          > functionality, and happens randomly.
          >
          > Thank you,
          > berker(at)optonline.net
          >
          > java.net.SocketException: Connection reset by peer: socket write error
          > at java.net.SocketOutputStream.socketWrite(Native Method)
          > at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
          > at weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:88)
          > at weblogic.servlet.internal.ResponseHeaders.writeHeaders(ResponseHeaders.java:336)
          > at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:603)
          > at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:101)
          > at weblogic.servlet.internal.ServletOutputStreamImpl.writeStream(ServletOutputStreamImpl.java:430)
          > at weblogic.servlet.FileServlet.sendFile(FileServlet.java:199)
          > at weblogic.servlet.FileServlet.service(FileServlet.java:56)
          > at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
          > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:105)
          > at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:742)
          > at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:686)
          > at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:247)
          > at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
          > at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

Connection reset by peer problem

I have the following code, and every time I run it i get a "java.net.SocketException: Connection reset by peer: socket write error" exception. Why is that? This is the first time I'm writing a network client application, so please help :)
Socket s = new Socket("127.0.0.1",8080);
OutputStream out = new BufferedOutputStream(s.getOutputStream());
InputStream in = new BufferedInputStream(s.getInputStream());
out.write("server status\r\n".getBytes());
//out.flush();
StringBuffer responseLine = new StringBuffer();
int c;
while(in.available() > 0) {
c = in.read();
responseLine.append((char)c);
//out.close();
//in.close();
//s.close();
System.out.println(responseLine.toString());P.S. It's the same problem with or wothout the out.flush(), and with or wothout closing my streams and socket.

InputStream = new BufferedReader
Um..just look at that code, oh boy.
InputStream is a class and so is
BufferedReader
Two different classes (event if they are subclasses)
cant be directly assigned to each other.The human eye sometimes sees what it wants to see and not what it is... :-)
I think the problem is with the protocol and the timing. The while loop may never execute due to timing:
1. Client's "server status" request takes a few ms to arrive in the server.
2. In the meanwhile, in.available is zero and the client does not enter the loop and does not append any characters to the string buffer.
3. Server writes its status on the socket which arrives at the client which is no longer reading it a few ms later.
Which brings us to the protocol:
If the server status is a fixed length block of data, try reading it into a single byte buffer.
If it is variable length or text, use a BufferedReader on the socket, read the response a line at a time and make the server end the report with a token (like a last line of "END_OF_SERVER_STATUS_REPORT" or "01234567890123456789012345678901234567890123456789", whatever).
Don't check if data is available on a socket if you know it should be, sooner or later, and you don't want to multiplex your flow on data availability.

Javax.servlet.ServletException: Connection reset by peer....Help needed..

Initially, when I clicked on my JSPs, everything was fine. I was able to retrieve data successfully from all the JSPs. However, after much clicking through the JSPs. I was not able to access the JSPs and the Internal Servlet Error was shown.
Below is my Tomcat.log:
Context log: path="/Aedge" Error in jsp service() : Connection reset by peer: socket write error
javax.servlet.ServletException: Connection reset by peer: socket write error
 at org.apache.jasper.runtime.JspServlet.service(JspServlet.java:375)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java:503)
 at org.apache.tomcat.core.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:163)
 at org.apache.tomcat.servlets.DefaultServlet.doGet(DefaultServlet.java:187)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java:503)
 at org.apache.tomcat.core.ContextManager.service(ContextManager.java:559)
 at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:160)
 at org.apache.tomcat.service.TcpConnectionThread.run(SimpleTcpEndpoint.java:338)
 at java.lang.Thread.run(Unknown Source)
Context log: path="/Aedge" Internal Servlet Error: .....
What is the problem here? How can I solve this as I had to restart my Tomcat once a while due to this problem.

ok.. I have db classes where all my sql statements methods are being displayed.. In each db class, there will be a getInstance() method to create the connection. Below is one of my db class.. How to I modified the things you had mentioned in my codes..
package aedgeSoft.access;
import aedgeSoft.business.*;
import java.sql.*;
import java.util.*;
import java.util.Date;
import java.io.*;
public class DBMemberType
 private Connection con;
 private static DBMemberType instance = null;
 public static DBMemberType getInstance()
 try
 if(instance==null)
 instance = new DBMemberType();
 catch(SQLException e)
 System.out.println("Problems with loading database in DBMemberType");
 catch(ClassNotFoundException e)
 System.out.println("Problems with loading db driver in DBMemberType");
 finally
 return instance;
 private DBMemberType() throws SQLException, ClassNotFoundException
 try{
 Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver").newInstance();
 con = DriverManager.getConnection("jdbc:microsoft:sqlserver://localhost:1433;user=username;password=password;DatabaseName=db");
 catch(InstantiationException e)
 e.printStackTrace();
 catch(IllegalAccessException e)
 e.printStackTrace();
 //add memberType
 public boolean addMemberType(MemberType mt)
..........

Connection reset by peer (jdk/jre 1.5.0_06, oracle 10.2.0.2)

I keep getting the "Oracle says: Io exception: Connection reset by peer: socket write error" to my jdbc thin client connection.
I have talked to our dba's and they don't see anything wrong on the oracle side. Network people say the network is good. Was this bug fixed in newer versions of ojdbc14.jar?

With JDK 5.0 use ojdbc5.jar instead of ojdbc14.jar.

Re: Connection reset by peer: Connection reset by peer

 >This is not a problem. It is an error message that you can safely ignore (that
 we should not be printing) and have fixed in version 6.0.
 Sorry but we are upgrading from 5.1 to 6.1sp2 and this became a problem for us.
 Indeed we just ignored this exception in 5.1, but today with 6.1sp2, we get it
 each time we do a RequestDispatcher.forward(). The forward is done, but every
 attributes set on the request are lost !!
 At first I thought it was related with the NT Muxer, or the NT Performance Pack,
 I removed the property NativeIOEnabled but I still get a :
 ven. 20020726 09:11:31 CEST <0> java.net.SocketException: Connection reset by
 peer: socket write error
 at java.net.SocketOutputStream.socketWrite(Native Method)
 at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
 at weblogic.servlet.internal.ChunkUtils.writeHeaderChunk(ChunkUtils.java:151)
 at weblogic.servlet.internal.ResponseHeaders.writeHeaders(ResponseHeaders.java:380)
 at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:827)
 at weblogic.servlet.internal.ServletOutputStreamImpl.sendHeaders(ServletOutputStreamImpl.java:222)
 at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:113)
 at weblogic.servlet.internal.ServletOutputStreamImpl.commit(ServletOutputStreamImpl.java:446)
 at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:266)
 at cegedim.tvf.teamsweb.gui.TeamsWebScreenBuilder.forwardScreen(TeamsWebScreenBuilder.java:155)
 at cegedim.tvf.teamsweb.gui.TeamsWebScreenBuilder.build(TeamsWebScreenBuilder.java:98)
 at cegedim.tvf.koala.servlet.GlobalServlet.callResultBuilder(GlobalServlet.java:365)
 at cegedim.tvf.teamsweb.servlet.ConnectionServlet.doPost(ConnectionServlet.java:112)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
 at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
 at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)


 Yann,
 This is not a J2EE Connector problem. From the stack trace it looks like you might
 have better luck posting this to the Servlet newsgroup.
 Also, just so that you are aware, this newsgroup is not monitored regularly so
 if your issue/question is not getting answered in a timely manner, please send
 a request to BEA Support.
 >
 >>This is not a problem. It is an error message that you can safely ignore
 >(that
 >we should not be printing) and have fixed in version 6.0.
 >
 >--
 >
 >Sorry but we are upgrading from 5.1 to 6.1sp2 and this became a problem
 >for us.
 >Indeed we just ignored this exception in 5.1, but today with 6.1sp2,
 >we get it
 >each time we do a RequestDispatcher.forward(). The forward is done, but
 >every
 >attributes set on the request are lost !!
 >At first I thought it was related with the NT Muxer, or the NT Performance
 >Pack,
 >I removed the property NativeIOEnabled but I still get a :
 >
 >ven. 20020726 09:11:31 CEST <0> java.net.SocketException: Connection
 >reset by
 >peer: socket write error
 > at java.net.SocketOutputStream.socketWrite(Native Method)
 > at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
 > at weblogic.servlet.internal.ChunkUtils.writeHeaderChunk(ChunkUtils.java:151)
 > at weblogic.servlet.internal.ResponseHeaders.writeHeaders(ResponseHeaders.java:380)
 > at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:827)
 > at weblogic.servlet.internal.ServletOutputStreamImpl.sendHeaders(ServletOutputStreamImpl.java:222)
 > at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:113)
 > at weblogic.servlet.internal.ServletOutputStreamImpl.commit(ServletOutputStreamImpl.java:446)
 > at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:266)
 > at cegedim.tvf.teamsweb.gui.TeamsWebScreenBuilder.forwardScreen(TeamsWebScreenBuilder.java:155)
 > at cegedim.tvf.teamsweb.gui.TeamsWebScreenBuilder.build(TeamsWebScreenBuilder.java:98)
 > at cegedim.tvf.koala.servlet.GlobalServlet.callResultBuilder(GlobalServlet.java:365)
 > at cegedim.tvf.teamsweb.servlet.ConnectionServlet.doPost(ConnectionServlet.java:112)
 > at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
 > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
 > at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
 > at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
 > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 >
 >

RE: SocketException: Connection reset by peer

I am getting a same exception in WebLogic6.1 SP1.
java.net.SocketException: Connection reset by peer: socket write error
     at java.net.SocketOutputStream.socketWrite(Native Method)
     at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
     at weblogic.servlet.internal.ChunkUtils.writeHeaderChunk(ChunkUtils.java:151)
     at weblogic.servlet.internal.ResponseHeaders.writeHeaders(ResponseHeaders.java:380)
     at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:827)
     at weblogic.servlet.internal.ServletOutputStreamImpl.sendHeaders(ServletOutputStreamImpl.java:222)
     at weblogic.servlet.internal.ChunkOutput.flush(ChunkOutput.java:241)
     at weblogic.servlet.internal.ChunkOutput.checkForFlush(ChunkOutput.java:306)
     at weblogic.servlet.internal.MultibyteOutput.write(ChunkOutput.java:413)
     at weblogic.servlet.internal.MultibyteOutput.print(ChunkOutput.java:389)
     at weblogic.servlet.internal.ChunkOutputWrapper.print(ChunkOutputWrapper.java:134)
     at weblogic.servlet.jsp.JspWriterImpl.print(JspWriterImpl.java:111)
Anybody has any idea?

"Connection reset by peer" Help Me

Hi
I have j2re1.4.2_08 and Oracle 9.2
When I tried to update database with huge data I got following exception:
java.sql.SQLException: Io exception: Connection reset by peer: socket write error
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:333)
at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:2061)
at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1940)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2709)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:589)
at edu.bnmit.BookDBUpdateThread.run(BookDBUpdateThread.java:80)
at edu.bnmit.BookDBUpdateThread.update(BookDBUpdateThread.java:46)
at java.lang.Thread.run(null:-1)
method used to update database is:
void update(Books b[]){
Connection dbConnection;
PreparedStatement stmt;
try{
dbConnection = DriverManager.getConnection(
dbConnection.setAutoCommit(false);
String sqlStmt = "UPDATE Books SET " +
"bookName=?, bookAuthor=?" +
"WHERE bookId=?";
stmt = dbConnection.prepareStatement(sqlStmt);
for(int i = 0; i < b.length; i++){
stmt.setString(1,b.bookName);
stmt.setString(2,b.bookAuthor);
stmt.setInt(3,b.bookId);
stmt.executeUpdate();
dbConnection.commit();
stmt.close();
dbConnection.close();
}catch(SQLException e){
System.err.println("Error While Updating Table");
String s = e.toString();
StackTraceElement trace[] = e.getStackTrace();
for(int j = 0; j < trace.length; j++){
s += "\n\tat "
+ trace[j].getClassName() + trace[j].getMethodName()
+ "(" + trace[j].getFileName()
+ ": " + trace[j].getLineNumber() + ")";
System.err.println(s);
}Orcale server is distently placed. I get this exception when I send 10,000+ records to update.
Can anyone help me.
Thanks

[Just a note: the stack does not match the code posted here. In the stack, executeUpdate() is called from BookDBUpdateThread.run() whereas your code shows that it's called from BookDBUpdateThread.update(). It helps to post the correct stack/code.)
The problem might just be that you have an unreliable connection. The fact that you have a long running operation is just exposing connection drops that may otherwise go unnoticed.
I suggest that you test this over a more reliable connection. If that is not possible, split the update into multiple shorter running updates. Of course, this would only work if the updates do not require a single transaction. If a single transaction is required, you can use your own XATransaction (the details on XATransactions are beyond the scope of this forum.)

Servlet Forward + Connection reset by peer

I have a strange error when making a forward from a servlet to a JSP page that exists !
i have the following message :
Connection reset by peer: socket write error
If i use Mozilla to access the same page, it works fine !!!
Strange !
Can you help me please ?

I use OC4J 9.0.4 and had the same error in IE6 but everything works fine in IE5 ! The same application works fine in JBOSS with both versions of IE (5 and 6).

ServletException - Connection reset by peer

Hi all,
I have a Servlet (ModificaCorpoOrdineService.java) with two method:
1) maskEditOrderCorp(req,resp)
2) EditOrderCorp(req,resp)
1) The first method is called when I have to present
the page addModCorpoOrdine.jsp and contain
the redirect to that jsp page:
RequestDispatcher rd = getServletContext().getRequestDispatcher("/Jsp/addModCorpoOrdine.jsp");
rd.forward(req, resp);
2) The second is called when I press "modify" from the JSP page when finish of edit the Order Corp. This method check data and if success save into DB the Order.
When some check fails, I call the method maskEditOrderCorp() to re-present the page displaying the error.
In some case this cause the error:
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at it.webconsulting.util.servlet.GenericService.doGet(GenericService.java:111)
at it.webconsulting.util.servlet.GenericService.doPost(GenericService.java:136)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:765)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:317)
at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:220)
at it.webconsulting.util.servlet.ServletDispatcher.doGet(ServletDispatcher.java:140)
at it.karnak.web.servlet.KarnakServletDispatcher.doGet(KarnakServletDispatcher.java:58)
at it.webconsulting.util.servlet.ServletDispatcher.doPost(ServletDispatcher.java:159)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
at oracle.lite.web.CheckSessionFilter.doFilter(CheckSessionFilter.java:212)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:604)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:317)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:270)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)
Caused by: javax.servlet.ServletException: Connection reset by peer: socket write error at com.evermind.server.http.EvermindPageContext.handlePageThrowable(EvermindPageContext.java:595)
at com.evermind.server.http.EvermindPageContext.handlePageException(EvermindPageContext.java:537)
at jsp.addModCorpoOrdine._jspService(_addModCorpoOrdine.java:2230)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:765)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:317)
at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:220)
at it.karnak.web.servlet.ModificaCorpoOrdineService.maskEditOrderCorp(ModificaCorpoOrdineService.java:260)
at it.karnak.web.servlet.ModificaCorpoOrdineService.clienteNonCompleto(ModificaCorpoOrdineService.java:1347)
at it.karnak.web.servlet.ModificaCorpoOrdineService.checkInviaAKarnak(ModificaCorpoOrdineService.java:2403)
at it.karnak.web.servlet.ModificaCorpoOrdineService.editOrderCorp(ModificaCorpoOrdineService.java:535)
... 24 more
Can someone help me?
Tanks for all your help.
D.

ok.. I have db classes where all my sql statements methods are being displayed.. In each db class, there will be a getInstance() method to create the connection. Below is one of my db class.. How to I modified the things you had mentioned in my codes..
package aedgeSoft.access;
import aedgeSoft.business.*;
import java.sql.*;
import java.util.*;
import java.util.Date;
import java.io.*;
public class DBMemberType
     private Connection con;
     private static DBMemberType instance = null;
     public static DBMemberType getInstance()
          try
               if(instance==null)
                    instance = new DBMemberType();
          catch(SQLException e)
               System.out.println("Problems with loading database in DBMemberType");
          catch(ClassNotFoundException e)
               System.out.println("Problems with loading db driver in DBMemberType");
          finally
               return instance;
     private DBMemberType() throws SQLException, ClassNotFoundException
          try{
          Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver").newInstance();
          con = DriverManager.getConnection("jdbc:microsoft:sqlserver://localhost:1433;user=username;password=password;DatabaseName=db");
          catch(InstantiationException e)
               e.printStackTrace();
          catch(IllegalAccessException e)
               e.printStackTrace();
     //add memberType
     public boolean addMemberType(MemberType mt)
..........

Broken Pipe/Connection Reset By Peer IO Exceptions

Can someone explain what causes a connection reset by peer exception vs.
          a Broken Pipe IO exception? I realize they are generally caused by
          someone hitting stop, closing their browser, hitting a different link,
          etc.. but I was trying to understand what might cause a connection
          reset by peer exception vs. a broken pipe exception. I've added code to
          my servlet to suppress the "Connection Reset By Peer" socket exceptions
          but I'm wondering if I should do the same with Broken Pipe. Also, are
          there are other types of similar exceptions that can occur when users
          get impatient.. Thanks
          Kirk


I do not have an idea about your application server but i do know how i solved it in weblogic. Just see whether this is helpful to you.
Points to be sure of........
1) Make sure that when ever you request a connection from a pool, after you are done with it return it. If you are not returning it and trying to use that reference again, this problem will occur.
2) Look at the capabilities of your app server. Set the connection pool such that
a) All the connections are checked at regular interval with some default select statement from any table in the database.
b) Connections are check when the connection is checked out and returned to the pool.
I the connection object is not ready , close it and create a new one. The app server which manages the pool should implement these feature so that when you get the connection - its the tested and working object.
If your app server does not support - then think of ways you testing it before you using it(Anyway this is not the good solution).

IOException: Connection reset by peer: JVM_recv in socket input stream read

hi
I encountered a problem : a program throw out an exception:java.io.IOException: Io exception:
Connection reset by peer: JVM_recv in socket input stream read.
I tried my best to resolve it ,but unfortunately,i didn't know what caused the exception.
the following is my application environment:
I have two PC(Win2000os),one is a server which installed oracle9.2.0.2 and jdeveloper9.0.3,the another is a
client which only intalled jdeveloper9.0.3.Two days ago,i performed a web application on my client with
jdeveloper,and it includes some JSP and a javabean files.JSP Page finished uploading client xml file to a
folder on server and the javabean finished loading the xml file into a xmltype column.I can make sure the
connection is established and the javabean is OK,beacause my some jsp page can successfully use
<jsp:usebean> tag and use the javabean's some other public interfaces,except the interface that finishs
loading the xml file into a xmltype(clob) column.
Then i do many tests!I changed the javabean to a java class incluse a main method beacause it is easy to
debug.Finally i found the following code caused the exception:
public CLOB writetoClob( CLOB clob, InputStream is )throws SQLException, IOException {
InputStreamReader reader = new InputStreamReader( is );
Writer writer = clob.getCharacterOutputStream( );
char[] buffer = new char[clob.getChunkSize( )];
int charsRead;
for ( charsRead = reader.read( buffer ); charsRead > -1;charsRead = reader.read( buffer ) ) {
writer.write( buffer, 0, charsRead );
writer.close();
return clob;
when it runs to writer.close(),the exception is caused!
Then i copy the java class to the server,it runs ok!
That is to say ,the same code,the different result!
But when i run my web application on server with jdeveloper Embedded OC4J Server and a jsp page loaded javabean
and run to mentioned code ,the same exception occured!
I checked the application log in event viewer,the descriptions was:
The data buffer created for the "AppleTalk" service in the "C:\WINNT\system32\atkctrs.dll" library is not
aligned on an 8-byte boundary. This may cause problems for applications that are trying to read the
performance data buffer. Contact the manufacturer of this library or service to have this problem corrected or
to get a newer version of this library.
I search some some resolution about this exception with web and someone sayed :
This basically means that a network error occurred while the client was receiving data from the server. But
what is really happening is that the server actually accepts the connection, processes the request, and sends a
reply to the client. However, when the server closes the socket, the client believes that the connection has
been terminated abnormally because the socket implementation sends a TCP reset segment telling the client to
throw away the data and report an error.
Sometimes, this problem is caused by not properly closing the input/output streams and the socket connection.
Make sure you close the input/output streams and socket connection properly. If everything is closed properly,
however, and the problem persists, you can work around it by adding Thread.sleep(1000) before closing the
streams and the socket. This technique, however, is not reliable and may not work on all systems.
In general,the following information is conclution:
Web application runs error both on client and on server.
If it was changed to a client java class,it only run ok on server!
i have done anything that i can do now,i feel depressed very much!
how can i resolve the problem!
Any a little help will be appreciated!
regards!
Thanks
Jiawei ZHAO

How can i solve the problem.
Thanks in advance!
Jiawei Zhao

Socket read error: connection reset by peer

Hi.
Has anybody experienced the error message �Socket read error: connection reset by peer�
Please see below for detailed information.
Appreciate your help
Regards
RT
Enviroment specification
Server: HP/UX 11.00 64-bit, Oracle RDBMS 8.1.6.0.0 64-bit
2 firewalls between client and db.
Client:
Win 2000,
SP3,
Oracle Client 8.1.7.0.0 ,JDBC OCI (thin JDBC driver,class12.zip)
JDK 1.3
JRUN3.0
The TCP protocol is being used in the communication
Error messages
Web Users receive: Socket read error: connection reset by peer
Trace files on the sever: Read unexpected EOF ERROR on 18.
Explanation: The error in the server sqlnet trace file, suggests that a client connection has terminated abnormally, i.e. client machine powered off, a cable removed or a network connection aborted without warning. No user has complained of such a problem and there is no client trace with an error.
The problem
The users of the java web application, experiencing an exception almost once or twice a day.
The JRUN web-server reports broken connections to the db and client are receiving "connection reset by peer".
At the moment when the errors occurs the users just have to wait a while(2-10 min) and then they can use the web application again.(no action is taken)
This problem can not be reproduced. The problem happens only occasionally when the network is under heavy load and new DB connection is being created.
The application
The java web-application uses a customized connection pooling against the database. This pool is shared among all the users of the website. whenever a user process needs to fetch data from the database, a free connection from this pool is allocated. The application is testing if the connection is valid before making a transaction (select '1' from dual). When the error occurs a ORA-3113 end-of-file on communication channel is returned to the application.
The path between the client and db involves at least two firewalls. The firewalls are opened for sql*net traffic. The network group can tell that enquiries from the app.server is not getting feedback from the db. They have not however, identified if the enquiries are reaching the db-srever, or if they are stopped earlier in the network.
Around 1000 users, are using other applications which uses dedicated sqlnet connections against the db and they have not experienced any problems.
Issues considered
Connection pooling
It is a customized connection pooling, developed by Lindorff developers.
I have read through the source code for the connection pooling and it does the job as it should, and in case of bad connection, it tries to create a new connection.
The log file shows that the call to the method DriverManager.getConnection() hangs until the server goes down, which is probably because of the fact that the method DriverManager.setLoginTimeout(), does not take effect and timeout value is Zero. ( According to oracle , Oracle JDBC does not support login timeouts and calling the static DriverManager.setLoginTimeout() method will have no effect).
Firewall
One thing to consider is when the firewall may decide to shut down the socket due to long inactivity of a connection. This will cause problems to JDBC Connection Pool because the pool is not aware of this disconnection at the TCP/IP level; until someone checks out the connection from the pool and tries to use it. The user will get a Socket read error: connection reset by peer.
Jrun timeout paramter is less than the firewall�s timeout so the firewall will not close a connection before Jrun does.
Number of processes the DB can handle
Processes parameter is 1300, , they have not experienced the Oracle error msg �max # of processes reached�.
Port redirection through a firewall:
Since the firewall has a sql net proxy Port redirection through a firewall is not a problem. Problems with port redirection only appear at connect time, but in this situation the connections fail long after the connection is established.
The network group
The network people who investigaged the problem at Lindorff report that there are a significant amount of "dropped packages" between the database server and the jdbc client (web-application) 24 hrs. The reason for this is "unknown established TCP packet" which means that the firewall does not consider these packages to be part of an already established session. The network group believes this happen because one of the hosts send a RESET or FIN signal which the firewall have noticed but are not received by the other host.
It seems like the firewall are dropping packages bacause of "Unknown
established TCP packet" from both the JDBC client and the TNSLISTENER on the database server. The dropped packages are SQL*Net v2 traffic so clearly Oracle products are involved

Presumably something is working.
Thus the problem is not with your code. At least not the database part that you have control over.
That error occurs when the other side closes the socket. Presumably you are catching lost connection exceptions and trying to restore it.

Connection reset by peer : Socket write

Similar Messages

Maybe you are looking for