glassfish
  1. glassfish
  2. GLASSFISH-13927

Node Tree: jdbc resource not deleted when pool deleted

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.1
    • Fix Version/s: 3.1_b25
    • Component/s: admin_gui
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      13,927

      Description

      build: glassfish-3.1-b24-10_10_2010.zip

      Create a JDBC pool, e.g. called y, and a jdbc resource using this pool, e.g.
      called z. Node tree is updated properly (though it takes time). Delete the
      pool - message is displayed saying that all the resources depending on this pool
      will also be deleted, click OK. The pool is removed from the nodes tree, but
      the resource is not. When you click on that resource node the following
      exception is printed:

      exception
      javax.servlet.ServletException: Target Unreachable, 'null' returned null

      Once user clicks on JDBC Resources node, the tree underneath is updated to
      reflect the deleted resource.

        Activity

        Hide
        lidiam added a comment -

        Created an attachment (id=5122)
        screenshot

        Show
        lidiam added a comment - Created an attachment (id=5122) screenshot
        Hide
        kenpaulsen added a comment -

        Anissa and I looked at this together. She has a fix for this + a fix for images
        / expanded state not being preserved. I am transferring this to her so she can
        resolve this as soon as her changes are committed. -Ken

        Show
        kenpaulsen added a comment - Anissa and I looked at this together. She has a fix for this + a fix for images / expanded state not being preserved. I am transferring this to her so she can resolve this as soon as her changes are committed. -Ken
        Hide
        Anissa Lam added a comment -

        Instead of admingui.nav.refreshTree() for just the JDBC connection pool, refresh
        starting from the JDBC nodes.

        While fixing this, also realize the connectors connection pool will have similar
        issue, fixed that as well.

        Also notice that the state of the tree node is not preserved, ie, collapsed or
        expanded, fixed that as well.

        Show
        Anissa Lam added a comment - Instead of admingui.nav.refreshTree() for just the JDBC connection pool, refresh starting from the JDBC nodes. While fixing this, also realize the connectors connection pool will have similar issue, fixed that as well. Also notice that the state of the tree node is not preserved, ie, collapsed or expanded, fixed that as well.
        Hide
        shaline added a comment -

        Verified in promoted b40.

        Show
        shaline added a comment - Verified in promoted b40.

          People

          • Assignee:
            Anissa Lam
            Reporter:
            lidiam
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: