Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 9.1pe
    • Fix Version/s: 4.0
    • Component/s: orb
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

      Description

      In case of an orderly shutdown of GlassFish v2 it should block new incoming
      requests and throw a CORBA exception with COMPLETE_NO while the shutdown is in
      progress. This is documented in section "Impact of orderly shutdown" in this
      document https://glassfish-corba.dev.java.net/design/orbdArchitecture.html

      But the client receives an java.rmi.ServerException with a notice "server is in
      STOPPING". But this exception is not a CORBA exception and so it's impossible
      for the client to initiate a failover. Only if it's a CORBA exception with
      COMPLETE_NO the client tries to failover, as described in this document.

      The result is that all rmi-iiop calls to a server instance which is in a
      shutdown in progress state will fail and will not failover to other instances.

      More details are in the forum Threads
      http://forums.java.net/jive/thread.jspa?threadID=34528&tstart=15
      and
      https://glassfish-corba.dev.java.net/servlets/ProjectForumMessageView?forumID=2940&messageID=22494

        Activity

        fmeili created issue -
        Hide
        fmeili added a comment -
            • Issue 3935 has been confirmed by votes. ***
        Show
        fmeili added a comment - Issue 3935 has been confirmed by votes. ***
        Hide
        Ken Cavanaugh added a comment -

        Changed target to V3.

        Show
        Ken Cavanaugh added a comment - Changed target to V3.
        Hide
        sanandal 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
        sanandal 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
        Ken Cavanaugh added a comment -

        Moved to v3.1.

        Show
        Ken Cavanaugh added a comment - Moved to v3.1.
        Hide
        Ken Cavanaugh added a comment -

        Moving to P3: we should fix this in V3.1.

        Show
        Ken Cavanaugh added a comment - Moving to P3: we should fix this in V3.1.
        Hide
        Ken Cavanaugh added a comment -

        I decided to leave this in 3.1 for now, to remind me to look at it.

        Show
        Ken Cavanaugh added a comment - I decided to leave this in 3.1 for now, to remind me to look at it.
        Hide
        Ken Cavanaugh added a comment -

        This issue is likely to have changed behavior significantly in GF 3.1.
        But I cannot address this in GF 3.1, because for many other reasons,
        we don't have a completely clean orderly shutdown. The asadmin command
        stop-instance of course shuts down the instance, but it forces the shutdown
        with a System.exit or equivalent mechanism due to some unresolved issues
        with non-daemon threads.

        There are also problems in the EJB container, because the EJB contained
        does not shutdown the ORB. It should, and it should to this BEFORE it
        undeploys EJBs and marks the container as STOPPED (or whatever the equivalent
        is in GF 3.1). Consequently, I am moving this issue to GF 3.2 for further
        consideration in the next release.

        Show
        Ken Cavanaugh added a comment - This issue is likely to have changed behavior significantly in GF 3.1. But I cannot address this in GF 3.1, because for many other reasons, we don't have a completely clean orderly shutdown. The asadmin command stop-instance of course shuts down the instance, but it forces the shutdown with a System.exit or equivalent mechanism due to some unresolved issues with non-daemon threads. There are also problems in the EJB container, because the EJB contained does not shutdown the ORB. It should, and it should to this BEFORE it undeploys EJBs and marks the container as STOPPED (or whatever the equivalent is in GF 3.1). Consequently, I am moving this issue to GF 3.2 for further consideration in the next release.
        Hide
        Nazrul added a comment -

        Excluding from 3.1 query

        Show
        Nazrul added a comment - Excluding from 3.1 query
        kenaiadmin made changes -
        Field Original Value New Value
        issue.field.bugzillaimportkey 3935 35539
        Hide
        Ken Cavanaugh added a comment -

        Moving to orb component (where it belongs).

        Show
        Ken Cavanaugh added a comment - Moving to orb component (where it belongs).
        Ken Cavanaugh made changes -
        Component/s orb [ 10610 ]
        Component/s rmi_iiop_failover [ 10615 ]
        Ken Cavanaugh made changes -
        Priority Major [ 3 ] Minor [ 4 ]
        Jill Sato made changes -
        Fix Version/s 4.0 [ 10970 ]
        Fix Version/s 3.2 [ 10969 ]
        Ed Bratt made changes -
        Assignee Ken Cavanaugh [ kcavanaugh ] Harshad Vilekar [ hvilekar ]

          People

          • Assignee:
            Harshad Vilekar
            Reporter:
            fmeili
          • Votes:
            3 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated: