glassfish
  1. glassfish
  2. GLASSFISH-7043

After redeployment I get 403 on basic auth metro ws

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 9.1peur2
    • Fix Version/s: not determined
    • Component/s: web_services
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      7,043

      Description

      I redeploy basic auth ws on a 2 node cluster via web gui. The realm is a file
      realm. Befor redeployment all works fine, aber deploy 403. I don't see any
      errors at log. Pls say what you need to isolate the problem.

      Os: win2000, jdk1.6.0.4
      Sun Java System Application Server 9.1_02 (build b04-fcs)

      regards Dietmar

        Activity

        Hide
        Hong Zhang added a comment -

        Assign to Bhakti as it's a web services application...

        Show
        Hong Zhang added a comment - Assign to Bhakti as it's a web services application...
        Hide
        harpreet added a comment -

        "Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1
        release whose primary release driver is SailFin.
        This issue will be scrubbed after this release and will be given the right
        priority for the next release."

        Show
        harpreet added a comment - "Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1 release whose primary release driver is SailFin. This issue will be scrubbed after this release and will be given the right priority for the next release."
        Hide
        oaspublic added a comment -

        I don't agree to this, because I have this problem at a production critical
        system and current my only workaround is restart cluster. If we found a other
        good workaround it's ok for me. If we don't find a good workaround I need a
        workable solution or a fix at this or a production release!

        Show
        oaspublic added a comment - I don't agree to this, because I have this problem at a production critical system and current my only workaround is restart cluster. If we found a other good workaround it's ok for me. If we don't find a good workaround I need a workable solution or a fix at this or a production release!
        Hide
        oaspublic added a comment -

        I did some checks and build a case and now the status is:

        this problem isn't releated to ws only! I can confirm, that the error always
        exists at a web app with file realm when I redeploy a clustered web application.
        Restart the cluster solve the problem.

        With version:

        Sun GlassFish Enterprise Server v2.1 (9.1.1) (build b60e-fcs)

        it seems to work like expected

        Show
        oaspublic added a comment - I did some checks and build a case and now the status is: this problem isn't releated to ws only! I can confirm, that the error always exists at a web app with file realm when I redeploy a clustered web application. Restart the cluster solve the problem. With version: Sun GlassFish Enterprise Server v2.1 (9.1.1) (build b60e-fcs) it seems to work like expected
        Hide
        Tom Mueller added a comment -

        Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

        Show
        Tom Mueller added a comment - Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

          People

          • Assignee:
            Bhakti Mehta
            Reporter:
            oaspublic
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: