Thank you, that's very helpful. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 26, 2005 5:22 PM To: [email protected] Subject: RE: Websphere
The "Connection reset by peer" exception happens when your servlet is trying to write back to the browser and the browser has closed its socket, often by having sent another http request before the first one was returned. It's like asking a question to someone over the phone and hanging up right before they answer... Not sure how this is provoked by the inputCalendar, but I just wanted to give you a 'heads up' on how why WebSphere often reports this error. HTH Mark -----Message d'origine----- De : Zhai, Warren [IT] [mailto:[EMAIL PROTECTED] Envoyé : mardi 26 juillet 2005 17:11 À : [email protected] Objet : Websphere I am testing the <x:inputCalendar /> control on WSAD 5.1.2, and everything seems to work except when I click on the refresh button on my browser, I get the following error: [7/26/05 15:56:14:968 EDT] 79afc35f WebGroup E SRVE0026E: [Servlet Error]-[Filter [extensionsFilter]: filter is unavailable.]: java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:112) at java.net.SocketOutputStream.write(SocketOutputStream.java:156) at com.ibm.ws.io.Stream.write(Stream.java:26) at com.ibm.ws.io.WriteStream.flushMyBuf(WriteStream.java:145) at com.ibm.ws.io.WriteStream.flush(WriteStream.java:137) at com.ibm.ws.http.ResponseStream.flush(ResponseStream.java:303) at com.ibm.ws.io.WriteStream.flush(WriteStream.java:139) at com.ibm.ws.webcontainer.http.HttpConnection.flush(HttpConnection.java:379) at com.ibm.ws.webcontainer.srp.SRPConnection.flush(SRPConnection.java:242) at com.ibm.ws.webcontainer.srt.SRTOutputStream.flush(SRTOutputStream.java:46) at com.ibm.ws.webcontainer.srt.BufferedServletOutputStream.flushBytes(BufferedServletOutputStream.java:357) at com.ibm.ws.webcontainer.srt.BufferedServletOutputStream.write(BufferedServletOutputStream.java(Compiled Code)) at org.apache.myfaces.component.html.util.AddResource.serveResource(AddResource.java(Compiled Code)) at org.apache.myfaces.component.html.util.ExtensionsFilter.doFilter(ExtensionsFilter.java:98) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:132) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:71) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:974) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:564) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:200) at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:119) at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:276) at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71) at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:116) at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186) at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334) at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56) at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:618) at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:439) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:672) Any idea how to correct this? Warren
