6 Replies Latest reply: Jun 15, 2010 1:38 PM by mikereiche RSS

    UndeclaredThrowableException while undeploying ALDSP project (ALDSP 3.2)

    657004
      Hi,

      while undeploying ALDSP project from ALDSP cluster, I'm getting in the AdminServer output:

      <2009-01-06 13:58:48 CET> <Critical> <Management> <BEA-141190> <The commit phase of the configuration update failed with an exception:
      weblogic.descriptor.DescriptorUpdateFailedException: one or more registered update listeners reported activation problems.
      The following failures occurred:
      -- java.lang.reflect.UndeclaredThrowableException


      at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:247)
      at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:361)
      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
      at weblogic.security.service.SecurityManager.runAs(Unknown Source)
      at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:356)
      Truncated. see log file for complete stacktrace

      However, the project seems to be undeployed fine, can it bring any negative consequences?
        • 1. Re: UndeclaredThrowableException while undeploying ALDSP project (ALDSP 3.2
          mikereiche
          I can't tell if the exception is from the ALDSP undeployment. If it is - and the commit failed like it says - that would imply that the undeploy did not take place - but you would have figured that out. Can you post the stack trace from the server log? You'll find it in something like - <domain>/servers/<servername>/logs/<servername>.log

          A common problem with deploy/undeploy failing is that there is another lock - usually from the WLS console or ALDSP console.

          - Mike
          • 2. Re: UndeclaredThrowableException while undeploying ALDSP project (ALDSP 3.2
            657004
            I repeated undeployment and the result is the same. I made sure that another lock did not take place. Here goes the result from the AdminServer.log:

            ####<2009-01-06 17:26:41 CET> <Info> <ALDSP> <bespin> <AdminServer> <Thread-101> <weblogic> <> <> <1231259201074> <BEA-000000> <ResourceManagement> <DSPAuditEvent timestamp: Tue Jan 06 17:26:41 CET 2009 severity: INFORMATION id: ResourceManagement:33:Tue Jan 06 17:26:41 CET 2009 {                                                                                                                                                                                            

            common/application {
            user: weblogic
            eventkind: dataspace
            server: AdminServer
            }

            admin/dataspace {
            operation: delete
            }

            admin/dataspace {
            name: ResourceManagement
            }

            common/time {
            timestamp: Tue Jan 06 17:26:41 CET 2009
            duration: 29
            }

            }>
            ####<2009-01-06 17:26:44 CET> <Info> <J2EE Deployment SPI> <bespin> <AdminServer> <Thread-101> <<WLS Kernel>> <> <> <1231259204518> <BEA-260121> <Initiating undeploy operation for application, ResourceManagement_request_handlers [archive: null], to clava .>
            ####<2009-01-06 17:26:53 CET> <Info> <Deployer> <bespin> <AdminServer> <Thread-101> <<WLS Kernel>> <> <> <1231259213944> <BEA-149038> <Initiating Task for ResourceManagement_request_handlers : [Deployer:149026]remove application ResourceManagement_request_handlers on clava.>
            ####<2009-01-06 17:27:12 CET> <Critical> <Management> <bespin> <AdminServer> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231259232564> <BEA-141190> <The commit phase of the configuration update failed with an exception:
            weblogic.descriptor.DescriptorUpdateFailedException: one or more registered update listeners reported activation problems.
            The following failures occurred:
            -- java.lang.reflect.UndeclaredThrowableException


            at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:247)
            at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:361)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
            at weblogic.security.service.SecurityManager.runAs(Unknown Source)
            at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:356)
            at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
            at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:63)
            at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:223)
            at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:125)
            at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
            at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:466)
            at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:720)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
            >
            ####<2009-01-06 17:27:48 CET> <Info> <Deployer> <bespin> <AdminServer> <[ACTIVE] ExecuteThread: '21' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231259268189> <BEA-149074> <Successfully completed deployment task: [Deployer:149026]remove application ResourceManagement_request_handlers on clava.>
            ####<2009-01-06 17:27:58 CET> <Info> <ConfigFwk> <bespin> <AdminServer> <Thread-101> <weblogic> <> <> <1231259278782> <BEA-390100> <Session AUTO_SESSION is being activated>
            ####<2009-01-06 17:28:16 CET> <Notice> <ALDSP> <bespin> <AdminServer> <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1231259296198> <BEA-000000> <ResourceManagement> <Audit stopped.>
            ####<2009-01-06 17:28:16 CET> <Info> <ConfigFwk> <bespin> <AdminServer> <Thread-101> <weblogic> <> <> <1231259296831> <BEA-390102> <Session AUTO_SESSION was activated successfully>
            • 3. Re: UndeclaredThrowableException while undeploying ALDSP project (ALDSP 3.2)
              mikereiche
              There is a CR with a similar stack trace - CR345555 - indicating that the exception can be ignored (the application was being undeployed twice). I believe there are patches to avoid the stack trace. You can open a case with customer support if you want to find out about patches.

              There is a CR with the same stack trace - CR357710 - it says it is not readily reproducible.
              • 4. Re: UndeclaredThrowableException while undeploying ALDSP project (ALDSP 3.2)
                657004
                Mike, thanks for your response.

                I noticed this exception few days ago and I've been using ALDSP for a few months, so something must really be bad with reproducibility of this error. But if it can be ignored, then I'm satisfied with your answer. Thanks!
                • 5. Re: UndeclaredThrowableException while undeploying ALDSP project (ALDSP 3.2)
                  AbidPir
                  You can ask for a WLI patch against the bug 8187236 from support.

                  Cheers!
                  • 6. Re: UndeclaredThrowableException while undeploying ALDSP project (ALDSP 3.2)
                    mikereiche
                    Right. 8187236 is the bug number that CR345555 was converted to when Oracle acquired BEA. Support can look it up by either the bug number or the CR number.