Jira Application logs are flooded by REST analytics endpoint.
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
In this article we are going to describes a scenario in which atlassian-jira.log file is having lot of following ERROR messages from url: /jira/rest/analytics/1.0/publish/bulk.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
2024-04-02 12:45:31,685+0200 http-nio-8080-exec-94 url: /jira/rest/analytics/1.0/publish/bulk; user: someUser ERROR someUser 765x21153x1 1ncu74j 149.233.193.103,192.168.0.186 /rest/analytics/1.0/publish/bulk [c.s.j.spi.container.ContainerRequest] A message body reader for Java class java.util.List, and Java type java.util.List<com.atlassian.analytics.client.browser.PublisherResource$BrowserEventBean>, and MIME media type application/octet-stream was not found.
The registered message body readers compatible with the MIME media type are:
*/* ->
com.sun.jersey.core.impl.provider.entity.FormProvider
com.sun.jersey.core.impl.provider.entity.StringProvider
com.sun.jersey.core.impl.provider.entity.ByteArrayProvider
com.sun.jersey.core.impl.provider.entity.FileProvider
com.sun.jersey.core.impl.provider.entity.InputStreamProvider
com.sun.jersey.core.impl.provider.entity.DataSourceProvider
com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General
com.sun.jersey.core.impl.provider.entity.ReaderProvider
com.sun.jersey.core.impl.provider.entity.DocumentProvider
com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader
com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader
com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader
com.sun.jersey.json.impl.provider.entity.JSONJAXBElementProvider$General
com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$General
com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$General
com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General
com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General
com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General
com.sun.jersey.core.impl.provider.entity.EntityHolderReader
com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider$General
com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$General
com.sun.jersey.json.impl.provider.entity.JacksonProviderProxy
application/octet-stream ->
com.sun.jersey.core.impl.provider.entity.ByteArrayProvider
com.sun.jersey.core.impl.provider.entity.FileProvider
com.sun.jersey.core.impl.provider.entity.InputStreamProvider
com.sun.jersey.core.impl.provider.entity.DataSourceProvider
com.sun.jersey.core.impl.provider.entity.RenderedImageProviderEnvironment
9.12.x
Diagnosis
There is a reported bug:
However following exception is observed in logs that are not mentioned in the bug:
1
2
3
4
[c.s.j.spi.container.ContainerRequest]A message body reader for Java class java.util.List, and Java type java.util.List<com.atlassian.analytics.client.browser.PublisherResource$BrowserEventBean>, and MIME media type application/octet-stream was not found.
The registered message body readers compatible with the MIME media type are:Cause
Please verify when this issue was initially noticed, as it may be attributed to a recently installed custom plugin or third-party plugin.
Solution
Upon activating Jira Safe mode, the specified logs were not detected in the atlassian-jira.log file.
After enabling plugins individually, it was determined that one of the custom plugins was generating log files containing these exceptions.
Was this helpful?