4 Replies Latest reply on Apr 3, 2001 9:37 PM by 3004

    Problem configuring AuditProvider class

    3004

      Hi,
      I have installed my customrealm(accessing oracle database) & am running the
      security webapp sample that comes with WLS6.0 successfully.But when I configured
      the CustomLogAuditProvider class(which is also part of the sample files in WLS)the
      sample is not working.The Server is throwing the following exception:

      javax.management.RuntimeOperationsException: RuntimeException thrown by the getA
      ttribute method of the DynamicMBean for the attribute FileTimeSpan
      at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.j
      ava:1183)
      at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.j
      ava:1151)
      at weblogic.management.internal.MBeanProxy.getAttribute(MBeanProxy.java:
      223)
      at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:156)
      at $Proxy3.getFileTimeSpan(Unknown Source)
      at weblogic.logging.FileStreamLogger.log(FileStreamLogger.java:169)
      at weblogic.management.logging.DomainLogHandler.handleNotification(Domai
      nLogHandler.java:308)
      at weblogic.management.internal.MBeanProxy.sendNotification(MBeanProxy.j
      ava:764)
      at weblogic.management.internal.BaseNotificationListenerImpl.handleNotif
      ication(BaseNotificationListenerImpl.java:71)
      at com.sun.management.jmx.MBeanServerNotificationListener.handleNotifica
      tion(MBeanServerNotificationListener.java:48)
      at javax.management.NotificationBroadcasterSupport.sendNotification(Noti
      ficationBroadcasterSupport.java:142)
      at weblogic.management.internal.DynamicMBeanImpl.sendNotification(Dynami
      cMBeanImpl.java:742)
      at weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:22
      3)
      at weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:18
      7)
      at weblogic.logging.LogManager.log(LogManager.java:144)
      at weblogic.logging.LogOutputStream.error(LogOutputStream.java:63)
      at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:142)
      at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)


      The weblogic.log file reflects the following entries which I think means the
      configuing of AuditProvider class is OK.
      ####<Mar 30, 2001 9:27:35 AM PST> <Info> <Audit> <SMULOMUDI> <examplesServer>
      <main> <system> <> <000000> <[NamingService] check perm: acl="weblogic.jndi",
      principal="system", permission="lookup", ALLOW>

      Any help on this would be greatly appreciated.
      Thanks in advance,
      Sita
        • 1. Re: Problem configuring AuditProvider class
          3004
          Try replacing the logging calls in the sample LogAuditProvider with a
          system.out and see if that helps. I don't remember exactly but it seems to
          me that I remember seeing a situation where the audit provider was called to
          log something and I think that the actual logging call caused an audit event
          to fire which in turn caused the audit provider to be called...recursion ad
          infititum...


          "Sita Mulomudi" <sita_mulomudi@flytecomm.com> wrote in message
          news:3ac4c559@newsgroups.bea.com...
          >
          Hi,
          I have installed my customrealm(accessing oracle database) & am running
          the
          security webapp sample that comes with WLS6.0 successfully.But when I
          configured
          the CustomLogAuditProvider class(which is also part of the sample files in
          WLS)the
          sample is not working.The Server is throwing the following exception:

          javax.management.RuntimeOperationsException: RuntimeException thrown by
          the getA
          ttribute method of the DynamicMBean for the attribute FileTimeSpan
          at
          com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.j
          ava:1183)
          at
          com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.j
          ava:1151)
          at
          weblogic.management.internal.MBeanProxy.getAttribute(MBeanProxy.java:
          223)
          at
          weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:156)
          at $Proxy3.getFileTimeSpan(Unknown Source)
          at
          weblogic.logging.FileStreamLogger.log(FileStreamLogger.java:169)
          at
          weblogic.management.logging.DomainLogHandler.handleNotification(Domai
          nLogHandler.java:308)
          at
          weblogic.management.internal.MBeanProxy.sendNotification(MBeanProxy.j
          ava:764)
          at
          weblogic.management.internal.BaseNotificationListenerImpl.handleNotif
          ication(BaseNotificationListenerImpl.java:71)
          at
          com.sun.management.jmx.MBeanServerNotificationListener.handleNotifica
          tion(MBeanServerNotificationListener.java:48)
          at
          javax.management.NotificationBroadcasterSupport.sendNotification(Noti
          ficationBroadcasterSupport.java:142)
          at
          weblogic.management.internal.DynamicMBeanImpl.sendNotification(Dynami
          cMBeanImpl.java:742)
          at
          weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:22
          3)
          at
          weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:18
          7)
          at weblogic.logging.LogManager.log(LogManager.java:144)
          at weblogic.logging.LogOutputStream.error(LogOutputStream.java:63)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:142)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)


          The weblogic.log file reflects the following entries which I think
          means the
          configuing of AuditProvider class is OK.
          ####<Mar 30, 2001 9:27:35 AM PST> <Info> <Audit> <SMULOMUDI>
          <examplesServer>
          <main> <system> <> <000000> <[NamingService] check perm:
          acl="weblogic.jndi",
          principal="system", permission="lookup", ALLOW>

          Any help on this would be greatly appreciated.
          Thanks in advance,
          Sita
          • 2. Re: Problem configuring AuditProvider class
            3004

            Hi Paul,
            Thanks for the suggestion.I have included System.out.println statements in
            the CustomLogAuditProvider class.Previously the server was starting but the sample
            created problems.Now the server itself is not starting.It is going into infinte
            loops as you said with recursive calls to checkpermission & filtercheckPermission.The
            fn code is as follows:

            public void checkPermission(String subsystem, Acl acl, Principal principal,
                           Permission permission, boolean result)
            {
            System.out.println("In the checkPermission..");
            if (filterCheckPermission(subsystem, acl, principal, permission, result))
            {
            dump(subsystem, "check perm",
                 "acl=" + str(acl != null ? acl.getName() : null) +
                 ", principal=" + str(principal != null ? principal.getName() : null) +
                 ", permission=" + str(permission) + ", " +
                 (result ? "ALLOW" : "DISALLOW"));
            }
            }

            protected boolean filterCheckPermission(String subsystem, Acl acl,
                                     Principal principal,
                                     Permission permission, boolean result)
            {
            System.out.println("In the filterCP..");
            return true;
            }
            Any suggestion about this infinite loop problem would be helpful.Thanks in
            advance,
            Sita


            "Paul Ferwerda" <ferwerda@somewhere.com> wrote:
            Try replacing the logging calls in the sample LogAuditProvider with a
            system.out and see if that helps. I don't remember exactly but it seems
            to
            me that I remember seeing a situation where the audit provider was called
            to
            log something and I think that the actual logging call caused an audit
            event
            to fire which in turn caused the audit provider to be called...recursion
            ad
            infititum...


            "Sita Mulomudi" <sita_mulomudi@flytecomm.com> wrote in message
            news:3ac4c559@newsgroups.bea.com...
            Hi,
            I have installed my customrealm(accessing oracle database) & am running
            the
            security webapp sample that comes with WLS6.0 successfully.But when
            I
            configured
            the CustomLogAuditProvider class(which is also part of the sample files
            in
            WLS)the
            sample is not working.The Server is throwing the following exception:

            javax.management.RuntimeOperationsException: RuntimeException thrown
            by
            the getA
            ttribute method of the DynamicMBean for the attribute FileTimeSpan
            at
            com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.j
            ava:1183)
            at
            com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.j
            ava:1151)
            at
            weblogic.management.internal.MBeanProxy.getAttribute(MBeanProxy.java:
            223)
            at
            weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:156)
            at $Proxy3.getFileTimeSpan(Unknown Source)
            at
            weblogic.logging.FileStreamLogger.log(FileStreamLogger.java:169)
            at
            weblogic.management.logging.DomainLogHandler.handleNotification(Domai
            nLogHandler.java:308)
            at
            weblogic.management.internal.MBeanProxy.sendNotification(MBeanProxy.j
            ava:764)
            at
            weblogic.management.internal.BaseNotificationListenerImpl.handleNotif
            ication(BaseNotificationListenerImpl.java:71)
            at
            com.sun.management.jmx.MBeanServerNotificationListener.handleNotifica
            tion(MBeanServerNotificationListener.java:48)
            at
            javax.management.NotificationBroadcasterSupport.sendNotification(Noti
            ficationBroadcasterSupport.java:142)
            at
            weblogic.management.internal.DynamicMBeanImpl.sendNotification(Dynami
            cMBeanImpl.java:742)
            at
            weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:22
            3)
            at
            weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:18
            7)
            at weblogic.logging.LogManager.log(LogManager.java:144)
            at weblogic.logging.LogOutputStream.error(LogOutputStream.java:63)
            at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:142)
            at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)


            The weblogic.log file reflects the following entries which I think
            means the
            configuing of AuditProvider class is OK.
            ####<Mar 30, 2001 9:27:35 AM PST> <Info> <Audit> <SMULOMUDI>
            <examplesServer>
            <main> <system> <> <000000> <[NamingService] check perm:
            acl="weblogic.jndi",
            principal="system", permission="lookup", ALLOW>

            Any help on this would be greatly appreciated.
            Thanks in advance,
            Sita
            • 3. Re: Problem configuring AuditProvider class
              3004
              Sita,
              Is it a truly ifinite recursion or just a very deep one? What resource
              is causing the CheckPermission? It sounds like this is a bug that should be
              reported to BEA.

              Paul

              "Sita Mulomudi" <sita_mulomudi@flytecomm.com> wrote in message
              news:3ac511ae$1@newsgroups.bea.com...
              >
              Hi Paul,
              Thanks for the suggestion.I have included System.out.println statements
              in
              the CustomLogAuditProvider class.Previously the server was starting but
              the sample
              created problems.Now the server itself is not starting.It is going into
              infinte
              loops as you said with recursive calls to checkpermission &
              filtercheckPermission.The
              fn code is as follows:

              public void checkPermission(String subsystem, Acl acl, Principal
              principal,
              Permission permission, boolean result)
              {
              System.out.println("In the checkPermission..");
              if (filterCheckPermission(subsystem, acl, principal, permission,
              result))
              {
              dump(subsystem, "check perm",
              "acl=" + str(acl != null ? acl.getName() : null) +
              ", principal=" + str(principal != null ? principal.getName() : null) +
              ", permission=" + str(permission) + ", " +
              (result ? "ALLOW" : "DISALLOW"));
              }
              }

              protected boolean filterCheckPermission(String subsystem, Acl acl,
              Principal principal,
              Permission permission, boolean result)
              {
              System.out.println("In the filterCP..");
              return true;
              }
              Any suggestion about this infinite loop problem would be helpful.Thanks
              in
              advance,
              Sita


              "Paul Ferwerda" <ferwerda@somewhere.com> wrote:
              Try replacing the logging calls in the sample LogAuditProvider with a
              system.out and see if that helps. I don't remember exactly but it seems
              to
              me that I remember seeing a situation where the audit provider was called
              to
              log something and I think that the actual logging call caused an audit
              event
              to fire which in turn caused the audit provider to be called...recursion
              ad
              infititum...


              "Sita Mulomudi" <sita_mulomudi@flytecomm.com> wrote in message
              news:3ac4c559@newsgroups.bea.com...
              Hi,
              I have installed my customrealm(accessing oracle database) & am
              running
              the
              security webapp sample that comes with WLS6.0 successfully.But when
              I
              configured
              the CustomLogAuditProvider class(which is also part of the sample files
              in
              WLS)the
              sample is not working.The Server is throwing the following exception:

              javax.management.RuntimeOperationsException: RuntimeException thrown
              by
              the getA
              ttribute method of the DynamicMBean for the attribute FileTimeSpan
              at
              com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.j
              ava:1183)
              at
              com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.j
              ava:1151)
              at
              weblogic.management.internal.MBeanProxy.getAttribute(MBeanProxy.java:
              223)
              at
              weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:156)
              at $Proxy3.getFileTimeSpan(Unknown Source)
              at
              weblogic.logging.FileStreamLogger.log(FileStreamLogger.java:169)
              at
              weblogic.management.logging.DomainLogHandler.handleNotification(Domai
              nLogHandler.java:308)
              at
              weblogic.management.internal.MBeanProxy.sendNotification(MBeanProxy.j
              ava:764)
              at
              weblogic.management.internal.BaseNotificationListenerImpl.handleNotif
              ication(BaseNotificationListenerImpl.java:71)
              at
              com.sun.management.jmx.MBeanServerNotificationListener.handleNotifica
              tion(MBeanServerNotificationListener.java:48)
              at
              javax.management.NotificationBroadcasterSupport.sendNotification(Noti
              ficationBroadcasterSupport.java:142)
              at
              weblogic.management.internal.DynamicMBeanImpl.sendNotification(Dynami
              cMBeanImpl.java:742)
              at
              weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:22
              3)
              at
              weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:18
              7)
              at weblogic.logging.LogManager.log(LogManager.java:144)
              at
              weblogic.logging.LogOutputStream.error(LogOutputStream.java:63)
              at
              weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:142)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)


              The weblogic.log file reflects the following entries which I think
              means the
              configuing of AuditProvider class is OK.
              ####<Mar 30, 2001 9:27:35 AM PST> <Info> <Audit> <SMULOMUDI>
              <examplesServer>
              <main> <system> <> <000000> <[NamingService] check perm:
              acl="weblogic.jndi",
              principal="system", permission="lookup", ALLOW>

              Any help on this would be greatly appreciated.
              Thanks in advance,
              Sita
              • 4. It is a bug !! Re: Problem configuring AuditProvider class
                3004

                Hi Paul,
                The server is starting after I configured the CustomLogAuditProvider class(with
                the checkPermission fn code commented out) & the security webapp is running fine.But
                the server is still throwing the RuntimeOperationsException I had copied in my
                mail below.It is a bug in WLS6.0 & I have reported this to BEA.
                Thanks,
                Sita

                "Paul Ferwerda" <ferwerda@somewhere.com> wrote:
                Try replacing the logging calls in the sample LogAuditProvider with
                a
                system.out and see if that helps. I don't remember exactly but it
                seems
                to
                me that I remember seeing a situation where the audit provider was
                called
                to
                log something and I think that the actual logging call caused an audit
                event
                to fire which in turn caused the audit provider to be called...recursion
                ad
                infititum...


                "Sita Mulomudi" <sita_mulomudi@flytecomm.com> wrote in message
                news:3ac4c559@newsgroups.bea.com...
                Hi,
                I have installed my customrealm(accessing oracle database) & am
                running
                the
                security webapp sample that comes with WLS6.0 successfully.But when
                I
                configured
                the CustomLogAuditProvider class(which is also part of the sample
                files
                in
                WLS)the
                sample is not working.The Server is throwing the following exception:

                javax.management.RuntimeOperationsException: RuntimeException thrown
                by
                the getA
                ttribute method of the DynamicMBean for the attribute FileTimeSpan
                at
                com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.j
                ava:1183)
                at
                com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.j
                ava:1151)
                at
                weblogic.management.internal.MBeanProxy.getAttribute(MBeanProxy.java:
                223)
                at
                weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:156)
                at $Proxy3.getFileTimeSpan(Unknown Source)
                at
                weblogic.logging.FileStreamLogger.log(FileStreamLogger.java:169)
                at
                weblogic.management.logging.DomainLogHandler.handleNotification(Domai
                nLogHandler.java:308)
                at
                weblogic.management.internal.MBeanProxy.sendNotification(MBeanProxy.j
                ava:764)
                at
                weblogic.management.internal.BaseNotificationListenerImpl.handleNotif
                ication(BaseNotificationListenerImpl.java:71)
                at
                com.sun.management.jmx.MBeanServerNotificationListener.handleNotifica
                tion(MBeanServerNotificationListener.java:48)
                at
                javax.management.NotificationBroadcasterSupport.sendNotification(Noti
                ficationBroadcasterSupport.java:142)
                at
                weblogic.management.internal.DynamicMBeanImpl.sendNotification(Dynami
                cMBeanImpl.java:742)
                at
                weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:22
                3)
                at
                weblogic.management.logging.LogBroadcaster.log(LogBroadcaster.java:18
                7)
                at weblogic.logging.LogManager.log(LogManager.java:144)
                at
                weblogic.logging.LogOutputStream.error(LogOutputStream.java:63)
                at
                weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:142)
                at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)


                The weblogic.log file reflects the following entries which I
                think
                means the
                configuing of AuditProvider class is OK.
                ####<Mar 30, 2001 9:27:35 AM PST> <Info> <Audit> <SMULOMUDI>
                <examplesServer>
                <main> <system> <> <000000> <[NamingService] check perm:
                acl="weblogic.jndi",
                principal="system", permission="lookup", ALLOW>

                Any help on this would be greatly appreciated.
                Thanks in advance,
                Sita