Details

      Description

      Background
      The LCS logs used to be in a separate log file. With the LCS client changes they have been added to the regular portal log. This means that LCS client messages that were hidden away before can appear to the user as a serious ERRORs in the portal log.

      Steps to reproduce:

      1. Start portal (with LCS deployed)

      Expected results:
      Out of the box, there should be no errors

      Actual results:
      Multiple errors like the following appear to notify the user that they have not deployed an LCS connection token:

      ERROR [LCS Worker 1][LCSClusterEntryTokenCheckTask:85] Unable to validate the environment token file
      com.liferay.lcs.client.exception.MissingLCSClusterEntryTokenException: The environment token file is missing. Please download a token file from LCS and place it in /media/jpince/l/72p-b/data
      	at com.liferay.lcs.client.internal.advisor.LCSClusterEntryTokenAdvisorImpl.getLCSClusterEntryTokenFileName(LCSClusterEntryTokenAdvisorImpl.java:235)
      	at com.liferay.lcs.client.internal.advisor.LCSClusterEntryTokenAdvisorImpl._processLCSClusterEntryTokenFile(LCSClusterEntryTokenAdvisorImpl.java:336)
      	at com.liferay.lcs.client.internal.advisor.LCSClusterEntryTokenAdvisorImpl.processLCSClusterEntryToken(LCSClusterEntryTokenAdvisorImpl.java:132)
      	at com.liferay.lcs.client.internal.task.LCSClusterEntryTokenCheckTask._checkLCSClusterEntryToken(LCSClusterEntryTokenCheckTask.java:109)
      	at com.liferay.lcs.client.internal.task.LCSClusterEntryTokenCheckTask.run(LCSClusterEntryTokenCheckTask.java:60)
      	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
      	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
      	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
      	at java.lang.Thread.run(Thread.java:748)
      

      Although the logs are correctly showing that the user has not added an LCS connection token, there are a few concerns:

      • Since LCS is an optional subscription method, there are valid cases where a user would never want to deploy a connection token
      • In the case that the user is not using LCS, meaning that no connection token is expected, does it make sense for the message to be an "ERROR" in the main logs? This kind of error messaging could scare the user.

        Attachments

          Activity

            People

            • Assignee:
              victor.ware Victor Ware
              Reporter:
              christian.stokes Christian Stokes
              Participants of an Issue:
              Recent user:
              Clarissa Velazquez
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Days since last comment:
                11 weeks, 2 days ago

                Packages

                Version Package
                7.0.0 DXP FP83
                7.0.X
                7.1.10 DXP FP12
                7.1.X
                7.2.X
                Master