Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-50217

Portlet scheduler-entry's don't work when the listener class is too long

    Details

      Description

      Currently method SchedulerEventMessageListenerWrapper.afterPropertiesSet() is cutting the jobName and groupName according to the maximum length configured in two portal.properties keys (scheduler.group.name.max.length and scheduler.job.name.max.length). This seems to be done due to DB limitations.

      The problem is that some lines below, the same class checks in method receive(Message) if the receiverKey of the given Message is equal to the value stored in the member fields in afterPropertiesSet(). Given that those values were cut they don't match, and the scheduler entry never gets invoked.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              brian.chan Brian Chan
              Reporter:
              ivan.zaera Ivan Zaera
              Participants of an Issue:
              Recent user:
              Brian Wulbern
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since last comment:
                7 years, 12 weeks ago

                  Packages

                  Version Package
                  7.0.0 M3