Who's Looking Error In Logs

[Joel Chuah]

Hi,

Going through our Atlassian logs in production instance,we see the following error/warning. However, I was not able to reproduce this in our test instance.

2015-11-04 01:56:03,310 http-bio-80-exec-90 ERROR testuser1116x484085x4 1qu925z 10.237.72.49 /rest/whoslooking/3.0/watchers/QWE-123[common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: null
java.util.ConcurrentModificationException

2015-11-04 01:51:19,138 http-bio-80-exec-51 WARN  testuser2 111x471255x6 1wy08tq 10.224.40.12 /rest/whoslooking/3.0/watchers/DMFERT-134 [com.atlassian.gzipfilter.GzipResponseWrapper] Was unable to create GzipResponseStream. Invalid gzip stream was sent in response body!
ClientAbortException: java.net.SocketException: Connection reset by peer: socket write error.

Has anyone encountered this error before? Thanks

[Ismael Olusula Jimoh]

@Werner Lembacher, @Joel Chuah, we would need more of the logs especially the section that talks about caused by:

This section would highlight why you are seeing the error you mentioned.

[Werner]

I saw the second one in our logs today.

It looks a little different:

2016-02-25 09:30:58,616 http-bio-8080-exec-2365 WARN      [com.atlassian.gzipfilter.GzipResponseWrapper] Was unable to create GzipResponseStream. Invalid gzip stream was sent in response body!
ClientAbortException:  java.net.SocketException: Broken pipe

We don't know why it came up, but at that exact time one of our users reported problems with loading an agile board. Coincidence? We are going to check further.

[Thomas]

@Werner, did you find out what causes this error?

It's been a long time, but suddenly you remember what the reason was. I'm facing the exact same issue.

[Werner]

Hi @Thomas !

No, we never found out.

And now we are moving to Cloud in a few days, so I guess we never will ;-)

[Thomas]

Thanks for the prompt reply and good luck on your journey to the cloud.