-
Bug
-
Resolution: Won't Fix
-
High
-
None
-
7.19.0, 7.19.1
-
16
-
Severity 3 - Minor
-
92
-
Issue Summary
When a Jira Activity Stream is refreshed, it throws a warning message:
2022-09-09 13:45:44,155 WARN [StreamsCompletionService::thread-16] [streams.confluence.changereport.ActivityItemFactory] add Error building ActivityItem from ConfluenceEntityObject
-- url: /confluence/plugins/servlet/streams | traceId: 3624c1a24868c112 | userName: admin
com.hazelcast.nio.serialization.HazelcastSerializationException: Failed to serialize 'com.hazelcast.hibernate.local.Invalidation'
Environment
- Issue reproducible on Data Center and Server
- Issue replicated by integrating Jira 8.20.12 with Confluence 7.19.6 using an application link
Steps to Reproduce
Steps - Scenario 1
- Create an application link between Jira and Confluence
- Configure Jira feed in External Gadget by following the instructions from this documentation
- Add the Activity Stream gadget to a page
- Refresh the page
Steps - Scenario 2
- Create an app link between Jira and Confluence
- Create a new dashboard in Jira
- Add an Activity Stream gadget to this dashboard and tick the Confluence option (to pull Confluence activity)
- Make some updates in the Confluence application
- Refresh the gadget in the Jira dashboard and noticed that the Confluence activity is updated there:
Expected Results - for Scenario 1 and 2
No warning message thrown in the Confluence logs when the activity stream is refreshed in both scenarios.
Actual Results - for Scenario 1 and 2
As soon as the gadget is added or refreshed the following warning message is thrown in the Confluence logs:
2022-09-09 13:45:44,155 WARN [StreamsCompletionService::thread-16] [streams.confluence.changereport.ActivityItemFactory] add Error building ActivityItem from ConfluenceEntityObject -- url: /confluence/plugins/servlet/streams | traceId: 3624c1a24868c112 | userName: admin com.hazelcast.nio.serialization.HazelcastSerializationException: Failed to serialize 'com.hazelcast.hibernate.local.Invalidation' at com.hazelcast.internal.serialization.impl.SerializationUtil.handleSerializeException(SerializationUtil.java:82) at com.hazelcast.internal.serialization.impl.AbstractSerializationService.toBytes(AbstractSerializationService.java:157) at com.hazelcast.internal.serialization.impl.AbstractSerializationService.toBytes(AbstractSerializationService.java:133) at com.hazelcast.internal.serialization.impl.AbstractSerializationService.toData(AbstractSerializationService.java:118) at com.hazelcast.internal.serialization.impl.AbstractSerializationService.toData(AbstractSerializationService.java:106) ... Caused by: com.hazelcast.nio.serialization.HazelcastSerializationException: Failed to serialize 'com.hazelcast.hibernate.region.CacheKeyImpl' ... Caused by: com.hazelcast.nio.serialization.HazelcastSerializationException: Failed to serialize 'com.atlassian.confluence.pages.Page' ... Caused by: org.apache.commons.lang3.NotImplementedException: serializableProxy not implemented
Workaround
Remove the Jira Activity Stream gadget from any pages containing it.
To identify Confluence pages containing this gadget, a query like the following can be executed against the Confluence DB:
select s.spacename, c.contentid, c.title, c.contenttype, c.content_status, c.version from content as c join bodycontent as bc on c.contentid = bc.contentid join spaces as s on c.spaceid = s.spaceid where body like '%jira-plugin:activitystream-gadget%' order by s.spacename, c.title desc;
This query was written for Postgres and may need to be adjusted depending on the DB in use.
Note
If auto refresh is configured, the error message is thrown based on the auto-refresh configuration
[CONFSERVER-79911] Warning logged when Jira Activity Stream gadget is refreshed
Hi James,
The scenario 2 is still happening with application link between recent versions of Jira 9.4.14 and Confluence 7.19.17 and is indipendent of the deprecation of Activity Strem Gadget of Confluence.
The Activity Stream in Jira is very common and the tick "Confluence option" is checked by default.
Please reopen this bug, it's not fixed.
Regards
Funny to say that "the impact is a message in the Confluence logs"
In our log we have more than 30 000 lines due to this problem.
Since it is default to have the activity stream in the profile in Jira. Every time someone opens a profile in Jira, Confluence is spammed with these lines.
Hi All,
Just a quick update on this one.
We deprecated the Activity Stream Gadget in 2019 with the release of Confluence 7.0. As part of this deprecation, we removed the ability to add the gadget to pages, but left existing gadgets in place.
As this is a deprecated gadget, and the impact of the issue is a message in the Confluence logs, I'm going to be closing this issue as Won't Fix.
I'll leave this note here for anyone else who encounters the issue moving forward.
Thanks,
James Ponting
Engineering Manager - Confluence Data Center
If this gadget were deprecated in 2019, why in version from 2023 (7.19.17) this issue still persist?
2024-01-22 09:21:09,051
Jira v9.4.9
<entry> <title>Gadget spec at https://jira.itgit.oneadr.net/rest/gadgets/1.0/g/com.atlassian.streams.streams-jira-plugin:activitystream-gadget/gadgets/activitystream-gadget.xml</title> <link rel="alternate" href="https://jira.itgit.oneadr.net/rest/gadgets/1.0/g/com.atlassian.streams.streams-jira-plugin:activitystream-gadget/gadgets/activitystream-gadget.xml" /> <id>https://jira.itgit.oneadr.net/rest/gadgets/1.0/g/com.atlassian.streams.streams-jira-plugin:activitystream-gadget/gadgets/activitystream-gadget.xml</id> <updated>2024-01-22T08:15:19Z</updated> </entry>If this is cause by left over pages with this macro, please provide sql query how to find pages affected by this macro/gadget. It will be more helpful than closing the ticket without providing any workaround or resolution.