Bug 1013990
| Summary: | java.net.SocketException: Broken pipe | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Zuzana Krejčová <zkrejcov> | ||||
| Component: | Business Central | Assignee: | manstis | ||||
| Status: | CLOSED EOL | QA Contact: | Lukáš Petrovický <lpetrovi> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 6.0.0 | CC: | etirelli, kverlaen, lpetrovi, rrajasek | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 6.2.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-03-27 19:37:58 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Seems to be okay now. |
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.