Bug 1013990 - java.net.SocketException: Broken pipe
Summary: java.net.SocketException: Broken pipe
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 6.2.0
Assignee: manstis
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-01 08:23 UTC by Zuzana Krejčová
Modified: 2020-03-27 19:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:37:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
server log from server started msg through 3 iterations of Steps to Reproduce (22.66 KB, text/x-log)
2013-10-01 08:23 UTC, Zuzana Krejčová
no flags Details

Description Zuzana Krejčová 2013-10-01 08:23:27 UTC
Created attachment 805758 [details]
server log from server started msg through 3 iterations of Steps to Reproduce

Description of problem:
Sometimes, you can get a very confusing exception in the server log, that doesn't seem to correspond with any failure visible in the GUI:

ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/business-central].[ErraiServlet]] .. JBWEB000236: Servlet.service() for servlet ErraiServlet threw exception: javax.enterprise.event.ObserverException
..
Caused by: ClientAbortException:  java.net.SocketException: Broken pipe
..
Caused by: java.net.SocketException: Broken pipe

If there actually was a problem and some admin had to go through the server log looking for the cause, this would make the task so much harder for him.

You can get this e.g. by going to Project Authoring perspective and refreshing the page while it is still loading. (Such a scenario is quite probable if you have a lot of assets and the loading takes too long.)


Version-Release number of selected component (if applicable):
BPMS 6.0 ER3


How reproducible:
1/3 to 1/2 of tries


Steps to Reproduce:
1. Get a bigger git repository.
2. Go to Project Authoring perspective.
3. Refresh the page while the perspective is still loading.
4. Look into the server log.


Actual results:
java.net.SocketException: Broken pipe stacktrace.


Expected results:
No error.

Comment 7 Zuzana Krejčová 2015-12-08 14:25:19 UTC
Seems to be okay now.


Note You need to log in before you can comment on or make changes to this bug.