Uploaded image for project: ' AGL Development'
  1. AGL Development
  2. SPEC-2756

WAM doesn't work in "single browser process" alternative mode

    Details

    • Type: Task
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: Halibut 8.0.2
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      WAM is usually ran as a system service, which runs a shared browser process for all webapps, but there is an alternate mode. In case the shared browser process is not running (which is guessed by checking the existence of the lock file), the WAM launcher process should be able to boot a single browser process for use in that web application.

      In Halibut, I checked that this mode is not working due to a crash. Steps to reproduce:

      1. stop the wam service: systemctl stop WebAppMgr@1001.service
      2. remove the lock file: rm /tmp/wamsocket.lock (affected by SPEC-2755)
      3. start a webapp

      We haven't tested this mode for a while, but I suspect it started crashing in Halibut due to the changes in permissions and users.

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

            • Assignee:
              jaragunde Jacobo Aragunde Pérez
              Reporter:
              jaragunde Jacobo Aragunde Pérez
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: