When navigating to any of our custom applications, we get a java.io.IOException: Broken pipe error in the log, although we can get to the page and it functions. In the network traffic, I see that the GET request for content is aborted, example /bonita/portal/resource/app/mydashboard/mytasks/content/. But then immediately after that another request is made and gets a 200. The page appears and functions appropriately, but curious why the request to get the content aborts then is followed up with another successful call. Plus, it is adding noise to the log files with the broken pipe exceptions.
Yes, I get something similar but for a different reason…this is the statement from Bonitasoft I got after logging a Bug Report…
The first one is known and does not have any functional impact.
There are 3 HTTP 500 errors (resource not found) that are displayed in the logs when you load an application.
This is due to the fact that the living application components are loaded too early (before we retrieve the application id).
However, the requests are resubmitted just after so this has no impact for the end user (except for the logs).
This will be fixed in next release.
The important bit being the last line… This will be fixed in next release.
Hopefully this will also address your issue,
Now, big question is is the next release 7.2.1 (available this month I believe) or 7.3.0 (could be a while yet).
regards
Seán
PS: If this reply answers your question, please mark as resolved.
Thank you Sean, that helped a lot!