1 2 Назад Вперед 23 Ответы Последний ответ: 19.10.2011 7:29, автор: 722524

    Broken Pipe + JDeveloper 10.1.3.1

    531309
      Hi,

      I have successfully deployed web application to oracle 10g application server. Applications works fine but sometimes it throws the following error

      javax.servlet.jsp.JspException: Broken pipe
      at com.sun.faces.taglib.jsf_core.ViewTag.doEndTag(ViewTag.java:223)

      What is this error and why? let me know what kind of error is it and how to resolve?

      Thanks,
      -
        • 1. Re: Broken Pipe + JDeveloper 10.1.3.1
          rade.todorovich
          yes i have application that works fine but sometimes it throws weird errors just like that
          07/04/27 09:34:51.582 TrackingSystem: Broken pipe
          07/04/27 09:34:51.582 TrackingSystem: Servlet error
          java.io.IOException: Broken pipe
               at sun.nio.ch.FileDispatcher.write0(Native Method)
               at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:29)
               at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:104)
               at sun.nio.ch.IOUtil.write(IOUtil.java:75)
               at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:302)
               at java.nio.channels.Channels.write(Channels.java:60)
               at java.nio.channels.Channels.access$000(Channels.java:47)
               at java.nio.channels.Channels$1.write(Channels.java:134)
               at com.evermind.server.http.AJPOutputStream.endRequest(AJPOutputStream.java:117)
          .....
          At the same time users experience loss of control and need to restart the browser
          • 2. Re: Broken Pipe + JDeveloper 10.1.3.1
            mattysmith
            We have started getting this same error as well. App logfile on the appserver shows
            07/06/08 11:25:36.669 ARCN: Servlet error
            java.io.IOException: Broken pipe
                 at sun.nio.ch.FileDispatcher.write0(Native Method)
                 at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:29)
                 at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:104)
                 at sun.nio.ch.IOUtil.write(IOUtil.java:75)
                 at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:302)
                 at java.nio.channels.Channels.write(Channels.java:60)
                 at java.nio.channels.Channels.access$000(Channels.java:47)
                 at java.nio.channels.Channels$1.write(Channels.java:134)
                 at com.evermind.server.http.AJPOutputStream.endRequest(AJPOutputStream.java:117)
                 at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:309)
                 at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
                 at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
                 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
                 at java.lang.Thread.run(Thread.java:595)

            This also seems to be (possibly coincidentally) related to spontaneous re-start of my applications! I.e in the log I see a few of these errors in 2 applications at around the same time, then both applications were restarted automatically by something, resulting in the users seeing a load of 'lost session' type errors.

            Anyone got any ideas? Is this memory-related?

            Matthew
            • 3. Re: Broken Pipe + JDeveloper 10.1.3.1
              rade.todorovich
              Further observation shows that these errors are transparent to the users (the delay in browser response was due to garbage collection on oc4j which could be fine-tuned with start params).

              Any idea?
              • 4. Re: Broken Pipe + JDeveloper 10.1.3.1
                580166
                We get these errors all the time, so much so that we have most of the logging on our webserver turned off so we don't have to deal with it. It has always been transparent to the users, meaning that no errors ever show up on the website itself.
                We have been told that it is connected to sessions that never finish loading, such as users leaving a web page before it fully loads.
                • 5. Re: Broken Pipe + JDeveloper 10.1.3.1
                  rade.todorovich
                  Anyone knows where to catch this exception?
                  • 6. Re: Broken Pipe + JDeveloper 10.1.3.1
                    225397
                    We too are getting the same error. We too are seeing that the browser needs to restart to get back to application. Some times the browser does not freeze but takes a long time (more than 1/2 hour). During this time clicking on refresh will bring back the page.
                    We suspected that the pauses that user is experiencing is due to Garbage collection. We turned on GC verbose. Throughout the load testing, which lasted for 20 minutes, there were only 3 full garbage collections and 600 minor GC. 600 minor GC consumed less than 18 seconds. 3 full GC consumed less than 6 seconds. So we ruled out that the GC is not major cause for pauses. Moreover the GC pauses won't last long (depending on the application and load) nor do they cause the browser to freeze.
                    This phenomenon is happening on several other applications as well.
                    There might be something else that is causing this. We did not resolve anything yet.
                    Some of the areas that can be explored are: TCP settings, Apache settings (keepalive etc.)
                    Please let us know if any one finds a solution.
                    Thanks
                    • 7. Re: Broken Pipe + JDeveloper 10.1.3.1
                      225397
                      This problem got resolved when we upgraded the App server to 10.1.3.1. May be some of the newer classes had fix for this. The application no more hangs erratically.
                      • 8. Re: Broken Pipe + JDeveloper 10.1.3.1
                        rade.todorovich
                        Well, we are already using 10.1.3.1 as the title suggests
                        • 9. Re: Broken Pipe + JDeveloper 10.1.3.1
                          TAB2912
                          hi,
                          im using 10.1.3.1 tooo and still getting this broken pipe....
                          • 10. Re: Broken Pipe + JDeveloper 10.1.3.1
                            533580
                            we are getting the same exception, and our application stays unavailable for several minutes, and sometimes gets restarted by opmn.
                            Here is what we have in the app log file located under j2ee/../application-deployment

                            java.io.IOException: An existing connection was forcibly closed by the remote host
                                 at sun.nio.ch.SocketDispatcher.write0(Native Method)
                                 at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:33)
                                 at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:104)
                                 at sun.nio.ch.IOUtil.write(IOUtil.java:75)
                                 at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:302)
                                 at java.nio.channels.Channels.write(Channels.java:60)
                                 at java.nio.channels.Channels.access$000(Channels.java:47)
                                 at java.nio.channels.Channels$1.write(Channels.java:134)
                                 at com.evermind.server.http.AJPOutputStream.endRequest(AJPOutputStream.java:117)
                                 at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:306)
                                 at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:187)
                                 at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
                                 at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:230)
                                 at oracle.oc4j.network.ServerSocketAcceptHandler.access$800(ServerSocketAcceptHandler.java:33)
                                 at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:831)
                                 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
                                 at java.lang.Thread.run(Thread.java:595)

                            Does anybody has the same in that log file?

                            thank you
                            • 11. Re: Broken Pipe + JDeveloper 10.1.3.1
                              421621
                              Hello all,

                              I also use the following exception when an user makes a signout from the application deployed on the 10.1.3.1 server. Otherwise, the exception seems to be a benign one.

                              Do you have any idea how to get rid of it?

                              Thanks,
                              Marinel



                              07/10/08 09:06:50.754 myWebapp: Broken pipe

                              07/10/08 09:06:50.755 myWebapp: Broken pipe

                              07/10/08 09:06:50.767 myWebapp: Servlet error

                              java.io.IOException: Broken pipe

                              at sun.nio.ch.FileDispatcher.write0(Native Method)

                              at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:29)

                              at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:104)

                              at sun.nio.ch.IOUtil.write(IOUtil.java:75)

                              at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:302)

                              at java.nio.channels.Channels.write(Channels.java:60)

                              at java.nio.channels.Channels.access$000(Channels.java:47)

                              at java.nio.channels.Channels$1.write(Channels.java:134)

                              at com.evermind.server.http.AJPOutputStream.endRequest(AJPOutputStream.java:117)

                              at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:309)

                              at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)

                              at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)

                              at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)

                              at java.lang.Thread.run(Thread.java:595)
                              • 12. Re: Broken Pipe + JDeveloper 10.1.3.1
                                Olaf Heimburger-Oracle
                                As 10.1.3.1 is pretty old, has someone checked the 10.1.3.3 version?
                                --olaf                                                                                                                                                                                   
                                • 13. Re: Broken Pipe + JDeveloper 10.1.3.1
                                  Olaf Heimburger-Oracle
                                  There is also a Metalink Note (333862.1) for this problem (w/ a test case).
                                  It states in essence:
                                  "To solve this issue the application needs to be tuned so response is provided before timeout fires.

                                  If application is OK, and response could not be delivered sooner then increase "Timeout" directive in file http.conf. You can use AS Control Console for this purpose.

                                  1. Select HTTP Server component

                                  2. Then select properties

                                  3. Modify timeout settings. Each unit represents a second. Default is 300 (5 minutes)."
                                  • 14. Re: Broken Pipe + JDeveloper 10.1.3.1
                                    225397
                                    We just upgraded to 10.1.3.3.
                                    The broken pipe exception still exists. We are getting it very frequently. This is with only one user accessing the application.
                                    Any other pointers are appreciated.
                                    Thanks

                                    Pavan
                                    1 2 Назад Вперед