MessageListeners that attempt to re-register (rather than update) will log a warning

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: Master
• Fix Version/s: 7.0.0 DXP FP30, 7.0.X EE, 7.0.4 CE GA5, 7.1.X, Master
• Component/s: Portal Services > Scheduler
• Labels:
  • liferay-digital-enterprise-70-sp5
  • liferay-fixpack-de-30-7010
• Branch Version/s:
  7.0.x
• Backported to Branch:
  Committed
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/51203

Changes made in LPS-74127 caused MessageListeners that attempted to re-register rather than update to log a warning.

This is correct, but now any *MessageListeners that register during @Modified after a configuration change need to instead use the update method on the SchedulerEngineHelper.

Otherwise, they will log warnings when trying to re-register.

Files that need updating:
modules/apps/twitter/twitter-service/src/main/java/com/liferay/twitter/internal/model/listener/SynchronizeTwitterMessageListener.java
modules/apps/collaboration/blogs/blogs-web/src/main/java/com/liferay/blogs/web/internal/messaging/CheckEntryMessageListener.java
modules/apps/collaboration/blogs/blogs-web/src/main/java/com/liferay/blogs/web/internal/messaging/LinkbackMessageListener.java
modules/apps/collaboration/document-library/document-library-web/src/main/java/com/liferay/document/library/web/internal/messaging/TempFileEntriesMessageListener.java
modules/apps/collaboration/subscription/subscription-web/src/main/java/com/liferay/subscription/web/internal/messaging/DeleteExpiredTicketsMessageListener.java
modules/apps/collaboration/message-boards/message-boards-web/src/main/java/com/liferay/message/boards/web/internal/messaging/ExpireBanMessageListener.java
modules/apps/collaboration/recent-documents/recent-documents-web/src/main/java/com/liferay/recent/documents/web/internal/messaging/RecentDocumentsMessageListener.java
modules/apps/foundation/portal/portal-pop-notifications/src/main/java/com/liferay/portal/pop/notifications/internal/messaging/POPNotificationsMessageListener.java
modules/apps/foundation/portal-security/portal-security-ldap/src/main/java/com/liferay/portal/security/ldap/internal/messaging/UserImportMessageListener.java
modules/apps/foundation/server/server-admin-web/src/main/java/com/liferay/server/admin/web/internal/messaging/PluginRepositoriesMessageListener.java

It's possible that there are more, we should check all MessageListeners just in case.