Tomcat Error: Output stream closed - can't load dashboard

Development
,
1

Hello @ibacher, @dkayiwa, @samuel34,

After deploying the micro-frontends in Tomcat, I can’t go past the login page as I keep getting the Error:

ERROR - GZIPResponseWrapper.finishResponse(60) |2022-11-06 22:38:07,815| Error during closing writer or stream java.io.IOException: This output stream has already been closed at org.openmrs.web.filter.GZIPResponseStream.close(GZIPResponseStream.java:55) at org.openmrs.web.filter.GZIPResponseWrapper.finishResponse(GZIPResponseWrapper.java:55) at org.openmrs.module.xforms.web.XformsFilter.doFilter(XformsFilter.java:63) at org.openmrs.module.web.filter.ModuleFilterChain.doFilter(ModuleFilterChain.java:71) at org.openmrs.module.web.filter.ModuleFilter.doFilter(ModuleFilter.java:57) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.openmrs.web.filter.OpenmrsFilter.doFilterInternal(OpenmrsFilter.java:109)

See full log here: https://codeshare.io/LwqWZ6

Similar error here but not exactly: https://issues.openmrs.org/browse/TRUNK-5978

Arthur

2

Which OpenMRS platform version are you running?

3

@dkayiwa it is OpenMRS Version: 2.3.2 Build 437b7f

4

That was fixed in OpenMRS platform 2.4.0

2 Likes
5

Thank you @dkayiwa for the update

6

@amugume & @dkayiwa do you think this means that implementers will be required to have Platform version 2.4.0+ in order to use OHRI? Or even O3 in general?

Or was this triggered by a specific, semi-unusual use case…?

Reason I’m asking is that my understanding until now has been that folks only need Platform 2.1+ in order to use O3 (though we recommend >2.3)

7

Looking at the commits, i have just noticed that it was also applied to the 2.3.x branch and released in platform version 2.3.3. I have added this fix version to the JIRA ticket. Does this automatically fit in our recommendation? :slight_smile:

That being said, the fix was was so simple that we can easily back port it all the way to the platform 2.1.x branch.

Probably. Some interesting details can be found on this ticket: https://issues.openmrs.org/browse/TRUNK-5978