glassfish
  1. glassfish
  2. GLASSFISH-10245

Admin consoles for 2 simultaneoulsy running domains don't load completely

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: V3
    • Fix Version/s: None
    • Component/s: admin_gui
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

      Description

      When I simultaneously start 2 domains in the same GFv3 installation and
      subsequently try to open their admin consoles in the browser, the admin consoles
      don't fully load (left and top menu bars are missing - see screenshot). Trying
      to navigate from such crippled console results in the blank page. When I refresh
      the consoles they usually fully load and start working. Still this is a really
      annoying issue from a user perspective

        Issue Links

          Activity

          Hide
          Anissa Lam added a comment -

          There is only one copy of admin console installed for the entire glassfish installation, so there is only 1 copy of web.xml.
          There is no way to specify different cookie name based on the domain name since they all use the same web.xml. So, the suggestion from Shing Wei will not work.

          The work around is to use different browser for different domain to access the console.

          Show
          Anissa Lam added a comment - There is only one copy of admin console installed for the entire glassfish installation, so there is only 1 copy of web.xml. There is no way to specify different cookie name based on the domain name since they all use the same web.xml. So, the suggestion from Shing Wei will not work. The work around is to use different browser for different domain to access the console.
          Hide
          Shing Wai Chan added a comment -

          One can solve this issue by using a different session cookie name for different domain.
          The cookie name is configured in web.xml

          Show
          Shing Wai Chan added a comment - One can solve this issue by using a different session cookie name for different domain. The cookie name is configured in web.xml
          Hide
          Anissa Lam added a comment -

          Based on Ken's comment, transfer to web-container.

          Show
          Anissa Lam added a comment - Based on Ken's comment, transfer to web-container.
          Hide
          kenpaulsen added a comment -

          I tried this out. Here's what I found... when I used browers that did not share
          cookies (i.e. Chrome w/ 1 browser running in "Incognito Mode"), then everything
          worked exactly as expected.

          When I used browser windows that do share cookies, the JSESSIONID was
          overwritten by the other browser window. This meant that every time I switched
          between windows, I essentially logged the other window out. Also, the Woodstock
          tree component uses cookies to maintain its highlighting – it got confused when
          2 windows were both updating the tree highlighting cookie.

          The suggested work-a-round is to use 2 browsers which are in different processes
          (e.g. firefox & chrome). Or to use the "incognito window" to isolate your 2
          browser windows from updating the same cookies. The cookies are set per
          machine, and not per domain. A possible enhancement in the future would be to
          make the cookies domain-aware. This would likely have to be done in the web
          container code for the JSESSION cookie.

          Also, we hope to allow administration of multiple domains from a single console
          in the future – this would provide another way to avoid this problem.

          -Ken

          Show
          kenpaulsen added a comment - I tried this out. Here's what I found... when I used browers that did not share cookies (i.e. Chrome w/ 1 browser running in "Incognito Mode"), then everything worked exactly as expected. When I used browser windows that do share cookies, the JSESSIONID was overwritten by the other browser window. This meant that every time I switched between windows, I essentially logged the other window out. Also, the Woodstock tree component uses cookies to maintain its highlighting – it got confused when 2 windows were both updating the tree highlighting cookie. The suggested work-a-round is to use 2 browsers which are in different processes (e.g. firefox & chrome). Or to use the "incognito window" to isolate your 2 browser windows from updating the same cookies. The cookies are set per machine, and not per domain. A possible enhancement in the future would be to make the cookies domain-aware. This would likely have to be done in the web container code for the JSESSION cookie. Also, we hope to allow administration of multiple domains from a single console in the future – this would provide another way to avoid this problem. -Ken
          Hide
          Marek Potociar added a comment -

          Hello, it's been a year since I have reported this issue. What is the status of
          the issue?

          Show
          Marek Potociar added a comment - Hello, it's been a year since I have reported this issue. What is the status of the issue?
          Hide
          Nazrul added a comment -

          Will look into this in next release.

          Show
          Nazrul added a comment - Will look into this in next release.
          Hide
          Anissa Lam added a comment -

          -> ken

          Show
          Anissa Lam added a comment - -> ken
          Hide
          Marek Potociar added a comment -

          Created an attachment (id=3516)
          Screenshot of the incomplete console

          Show
          Marek Potociar added a comment - Created an attachment (id=3516) Screenshot of the incomplete console

            People

            • Assignee:
              Anissa Lam
              Reporter:
              Marek Potociar
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: