Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Errors loading images/CSS/JS after upgrading to Crowd 3

After upgrading to Crowd 3.0.1 from version 2.11.1 loading images, CSS, and JS files stopped working. It seems that the response header indicates that GZIP compression is used, but the content is considered invalid by the browser.

At the same time the following error is logged:

WARN [webresource] error in `Content.writeTo` for com.atlassian.plugins.atlassian-nps-plugin:nps-btf-admin-resources/btf-admin.js
java.lang.RuntimeException: com.atlassian.plugin.servlet.DownloadException: Unable to stream to the output
        at com.atlassian.plugin.webresource.impl.helpers.ResourceServingHelpers$6.writeTo(
        at com.atlassian.plugin.webresource.impl.helpers.ResourceServingHelpers$2.lambda$writeTo$0(
        at com.atlassian.plugin.cache.filecache.impl.PassThroughCache.cache(
        at com.atlassian.plugin.webresource.impl.helpers.ResourceServingHelpers$2.writeTo(
        at com.atlassian.plugin.webresource.impl.helpers.ResourceServingHelpers$8.writeTo(
Caused by: com.atlassian.plugin.servlet.DownloadException: Unable to stream to the output
        at com.atlassian.plugin.webresource.transformer.TransformerUtils.transformAndStreamResource(
        at com.atlassian.plugin.webresource.transformer.CharSequenceDownloadableResource.streamResource(
        at com.atlassian.plugin.webresource.impl.helpers.ResourceServingHelpers$6.writeTo(
        ... 114 more
Caused by: org.apache.catalina.connector.ClientAbortException: Broken pipe (Write failed)
        at org.apache.catalina.connector.OutputBuffer.doFlush(
        at org.apache.catalina.connector.OutputBuffer.flush(
        at org.apache.catalina.connector.CoyoteOutputStream.flush(
        at sun.nio.cs.StreamEncoder.implFlush(
        at sun.nio.cs.StreamEncoder.flush(
        at com.atlassian.plugin.webresource.transformer.TransformerUtils.transformAndStreamResource(
        ... 116 more
Caused by: Broken pipe (Write failed)
        at Method)
        at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(
        at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(
        at org.apache.coyote.http11.InternalOutputBuffer.flush(
        at org.apache.coyote.http11.AbstractHttp11Processor.action(
        at org.apache.coyote.Response.action(
        at org.apache.catalina.connector.OutputBuffer.doFlush(
        ... 124 more

Note that connecting using localhost does work because GZIP compression is then automatically disabled.

I found a workaround by disabling compression as described here:

Why did this stop working? What is the nps plugin? And why is it messing with output streams?

1 answer

1 accepted

1 vote
Answer accepted
AnnWorley Atlassian Team Oct 20, 2017

I am happy to hear you already found a workaround.

I discussed your case with a Crowd developer and he suggested that the nps plugin was an innocent bystander, and we were running into this bug: Tomcat7 produces corrupted gzip response with newest zlib (1.2.11) library

The bug is fixed in Crowd 3.1, but should have also impacted your Crowd 2.11.1 instance. Is it possible that the zlib library was also upgraded recently?

Looking at my logs I did indeed upgrade zlib (from version 1.2.8.dfsg-2+b1 to 1.2.8.dfsg-5), although this is not 1.2.11 I think some (security related) fixes where backported by Debian into 1.2.8, causing the issue as described in CWD-4968.

Nice to hear that this was already fixed, looking forward to Crowd 3.1!

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events