java.net.SocketException: Broken pipe

Atlassian JIRA | Ian Daniel [Atlassian] | 9 years ago
  1. 0

    If there is a slow network connection between web browser and the box running JIRA, and if the JIRA instance has many projects (of the order of 100 or more), and if the user has the Projects Portlet on their dashboard, then the dashboard does not display in Internet Explorer 6 and 7. It works fine in Firefox. The browser (Internet Explorer) renders the header - the logo and the Home | Browse Projects | Find Issues | Create New Issue, but then not the rest of the dashboard page. The browser appears to try to reload the page a few times. This is apparent because the page briefly flashes and the "Waiting for <URL>" text at the bottom of the browser seems to redisplay. Sometimes there is first a "Website found. Waiting for reply." message briefly displayed in the message window at the bottom of the browser. The browser tries this several times, sometimes for 30 seconds or so, sometimes for several minutes, before finally giving up, displaying a popup window saying: Internet Explorer cannot open the Internet site <URL>. Operation aborted. This behaviour is readily reproducible using a local import of http://developer.atlassian.com/jira and using [TCPMon|http://ws.apache.org/commons/tcpmon/] to simulate a slow network connection. Use the following delay settings in TCPMon: Bytes per pause: 1024 Delay in Milliseconds: 50 The behaviour is also readily observable on http://developer.atlassian.com/jira (if you add the Projects Portlet to your dashboard, or create a new dashboard page containing the Projects Portlet). The problem was previously reported by two (separate) support customers. In their cases it only appears on slow links. The behaviour is not observable on the local import of http://developer.atlassian.com/jira if you do not use the delay. It is interesting to note that at the times when the browser seems to be trying to reload the page, the shell running TCPMon displays the following error: {noformat} java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.ws.commons.tcpmon.SocketRR.run(SocketRR.java:213) {noformat} Microsoft has a bug report for the above error message: http://support.microsoft.com/default.aspx/kb/927917. However that bug relates to Javascript, specifically to when a child container HTML element contains script code that tries to modify the parent container element of the child container. It is unlikely that this bug is the cause of our error, as you can turn off Javascript in IE and comment out all Javascript and links to Javascript files in the served page, and the error still occurs. We tried saving the static page back on the server (do a View Source in Firefox after the page is successfully displayed, then save it back to the server), and then accessing it. Same error occurs. We tried another page that is about the same size - ~900K - and it displays correctly. So the error is content specific. Perhaps it is related to nested tables? We spent significant time trying to find the root cause and have been unable to. As there are straightforward workarounds, we will not spend any more time on it at this stage. The workarounds are either: - Don't use the Projects Portlet in the dashboard if you have lots of projects. If you want links to projects on your dashboard, consider using the Project Table portlet instead. - Use Firefox instead of Internet Explorer.

    Atlassian JIRA | 9 years ago | Ian Daniel [Atlassian]
    java.net.SocketException: Broken pipe
  2. 0

    If there is a slow network connection between web browser and the box running JIRA, and if the JIRA instance has many projects (of the order of 100 or more), and if the user has the Projects Portlet on their dashboard, then the dashboard does not display in Internet Explorer 6 and 7. It works fine in Firefox. The browser (Internet Explorer) renders the header - the logo and the Home | Browse Projects | Find Issues | Create New Issue, but then not the rest of the dashboard page. The browser appears to try to reload the page a few times. This is apparent because the page briefly flashes and the "Waiting for <URL>" text at the bottom of the browser seems to redisplay. Sometimes there is first a "Website found. Waiting for reply." message briefly displayed in the message window at the bottom of the browser. The browser tries this several times, sometimes for 30 seconds or so, sometimes for several minutes, before finally giving up, displaying a popup window saying: Internet Explorer cannot open the Internet site <URL>. Operation aborted. This behaviour is readily reproducible using a local import of http://developer.atlassian.com/jira and using [TCPMon|http://ws.apache.org/commons/tcpmon/] to simulate a slow network connection. Use the following delay settings in TCPMon: Bytes per pause: 1024 Delay in Milliseconds: 50 The behaviour is also readily observable on http://developer.atlassian.com/jira (if you add the Projects Portlet to your dashboard, or create a new dashboard page containing the Projects Portlet). The problem was previously reported by two (separate) support customers. In their cases it only appears on slow links. The behaviour is not observable on the local import of http://developer.atlassian.com/jira if you do not use the delay. It is interesting to note that at the times when the browser seems to be trying to reload the page, the shell running TCPMon displays the following error: {noformat} java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.ws.commons.tcpmon.SocketRR.run(SocketRR.java:213) {noformat} Microsoft has a bug report for the above error message: http://support.microsoft.com/default.aspx/kb/927917. However that bug relates to Javascript, specifically to when a child container HTML element contains script code that tries to modify the parent container element of the child container. It is unlikely that this bug is the cause of our error, as you can turn off Javascript in IE and comment out all Javascript and links to Javascript files in the served page, and the error still occurs. We tried saving the static page back on the server (do a View Source in Firefox after the page is successfully displayed, then save it back to the server), and then accessing it. Same error occurs. We tried another page that is about the same size - ~900K - and it displays correctly. So the error is content specific. Perhaps it is related to nested tables? We spent significant time trying to find the root cause and have been unable to. As there are straightforward workarounds, we will not spend any more time on it at this stage. The workarounds are either: - Don't use the Projects Portlet in the dashboard if you have lots of projects. If you want links to projects on your dashboard, consider using the Project Table portlet instead. - Use Firefox instead of Internet Explorer.

    Atlassian JIRA | 9 years ago | Ian Daniel [Atlassian]
    java.net.SocketException: Broken pipe
  3. 0

    Can't get Jedis Connect in some other thread ?

    GitHub | 5 years ago | sunjian
    redis.clients.jedis.exceptions.JedisConnectionException: java.net.SocketException: Broken pipe
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    DataStax Support Forums ยป Recent Topics

    rssing.com | 8 months ago
    org.apache.thrift.transport.TTransportException: java.net.SocketException: Broken pipe
  6. 0

    Uploading image fails in finder

    GitHub | 4 years ago | wezell
    java.net.SocketException: Broken pipe

  1. linxiaolong 1 times, last 1 week ago
  2. Tahir 11 times, last 1 month ago
  3. serious2monkeys 7 times, last 1 week ago
  4. linxiaolong 1 times, last 4 months ago
  5. regisso 1 times, last 5 months ago
5 more registered users
90 unregistered visitors
Not finding the right solution?
Take a tour to get the most out of Samebug.

Tired of useless tips?

Automated exception search integrated into your IDE

Root Cause Analysis

  1. java.net.SocketException

    Broken pipe

    at java.net.SocketOutputStream.socketWrite0()
  2. Java RT
    SocketOutputStream.write
    1. java.net.SocketOutputStream.socketWrite0(Native Method)
    2. java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
    3. java.net.SocketOutputStream.write(SocketOutputStream.java:136)
    3 frames
  3. org.apache.ws
    SocketRR.run
    1. org.apache.ws.commons.tcpmon.SocketRR.run(SocketRR.java:213)
    1 frame