-
Bug
-
Resolution: Fixed
-
Medium
-
4.3, 4.3.2, 4.3.3, 5.0-OD-15
-
None
-
Gmail as the SMTP server via JDNI configuration.
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
Scenario:
Sharing a page with multiple users always returns an "Error while sending" message:
While sharing a page with a single user is not an issue as it returns the expected result which is "Sent"
However, Confluence sends all of the notifications without any problems (there is no queued messages, all users get their notifications). Nevertheless, this is a problem because this error is misleading and when users see this error message, they think their shared pages won't get through so they try to send it out again and again and this became a spam.
Resolution
This issue has been fixed in version 1.26.1 of the Share Page plugin. This is compatible for Confluence 4.3 and above. You can update the plugin by going to Manage Add-ons in Confluence Admin. If the update is compatible with your version of Confluence, it will be displayed in Action Required.
- is duplicated by
-
-
- Closed
-
- relates to
-
-
- Closed
-
- mentioned in
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page")
Wiki Page
Failed to load
[CONFSERVER-27300] Confluence always displays "Error While Sending" message when sharing a page with multiple users, although the notifications are sent without problem
Hi Chris,
Thanks for informing us about this problem. Can you please raise a new ticket outlining the steps you took to reproduce the error, and noting your version of the Share Page plugin? (Granted, it may be identical to the description for this issue).
We have just upgraded to Confluence 5.5 and are now experiencing this problem. Can we either reopen this ticket? I can create a new ticket if that is preferred.
Deleted Account (Inactive)
added a comment - Nice one, Atlassian! 
Chad Barnes
added a comment - That was unexpected. Thank you. We will try that out immediately. Hey Chad, a new version of the Share Page plugin has been released which includes the fix for this issue.
Please see: https://marketplace.atlassian.com/plugins/com.atlassian.confluence.plugins.share-page
You should find the fix in version 1.26.1 of the Share Page plugin. This is compatible for Confluence 4.3.x
Hi Chad,
Unfortunately, there isn't a solution for 4.x users. The fix is part of the share-page plugin and is included in version 2.0.6 of the plugin. This version of the plugin is, however, only compatible with Confluence 5.x.
Chad Barnes
added a comment - We have this issue and do not plan an upgrade to 5.x in the near future. Is there a solution for 4.x users?
Chad Barnes
added a comment - We have this issue and do not plan an upgrade to 5.x in the near future. Is there a solution for 4.x users? Deleted Account (Inactive)
added a comment - Oops, just noticed this is fixed for Confluence 5.0.x, so hopefully once we upgrade in the next week or two it won't happen again.
Deleted Account (Inactive)
added a comment - Oops, just noticed this is fixed for Confluence 5.0.x, so hopefully once we upgrade in the next week or two it won't happen again. Deleted Account (Inactive)
added a comment - Just want to add that we see this issue too, and there's nothing relevant in the atlassian-confluence.log when it occurs.
Deleted Account (Inactive)
added a comment - Just want to add that we see this issue too, and there's nothing relevant in the atlassian-confluence.log when it occurs.
I created
CONF-33876. As I have not been able to recreate this issue since the day of initial finding, they have already closed the issue. I linkedCONF-33876to this issue when I created it, but it didn't reciprocate on this end.We are using Share Page 3.1.5. As for the steps, a user simply tried to share a page (from the share page link on the page) with 5 users. I was able to recreate this on other pages with as few as 3 users. We have since rebuilt the search index and I have not been able to recreate this error since. I do not know if that is the fix, but I don't really know of any other maintenance (besides restarts) that we have completed.