Navigation

    Best APM Solution for Oracle WebLogic Server & FMW Product Family
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Download

    SOLVED wlsdm exception when install

    General Support & Troubleshooting
    wlsdm weblogic
    3
    7
    1848
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      neuron last edited by

      Hi,

      I got this exception when i restart the admin server. After it can not reach the admin console. It is a domain enviroment with 4 managed server.
      WebLogic Server Version: 12.2.1.1.0 with Java 1.8
      The agents work correct (as i saw the manages server log files)

      ####<2020.02.19., 11:55:42,786 DE CET> <[ACTIVE] ExecuteThread: ‘0’ for queue: ‘weblogic.kernel.Default (self-tuning)’> <> <> <1582109742786> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] >
      ####<2020.02.19., 11:55:42,793 DE CET> <[ACTIVE] ExecuteThread: ‘0’ for queue: ‘weblogic.kernel.Default (self-tuning)’> <> <> <1582109742793> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <Servlet: “wlsdm-background” failed to preload on startup in Web application: “console”.
      java.lang.NoSuchMethodError: com.vopm.backend.ConfigController.setEnabled(Z)V
      at com.wlsdm.U.A.D(StartupProcess.java:145)
      at com.wlsdm.U.A.fire(StartupProcess.java:97)
      at com.wlsdm.U.L.init(StartupServlet.java:43)
      at javax.servlet.GenericServlet.init(GenericServlet.java:244)
      at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:343)
      at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:294)
      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:326)
      at weblogic.security.service.SecurityManager.runAsForUserCode(SecurityManager.java:197)
      at weblogic.servlet.provider.WlsSecurityProvider.runAsForUserCode(WlsSecurityProvider.java:203)
      at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:71)
      at weblogic.servlet.internal.StubSecurityHelper.initServletInstance(StubSecurityHelper.java:99)
      at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:87)
      at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:71)
      at weblogic.servlet.internal.StubLifecycleHelper.(StubLifecycleHelper.java:57)
      at weblogic.servlet.internal.StubLifecycleHelper.(StubLifecycleHelper.java:31)
      at weblogic.servlet.internal.ServletStubImpl.initStubLifecycleHelper(ServletStubImpl.java:673)
      at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:612)
      at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:2054)
      at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:2031)
      at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1920)
      at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3091)
      at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1849)
      at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:882)
      at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:360)
      at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:356)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
      at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:138)
      at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124)
      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:233)
      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:228)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
      at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:78)
      at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:52)
      at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:754)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
      at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:264)
      at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:66)
      at weblogic.application.services.BackgroundDeploymentManagerService$2.next(BackgroundDeploymentManagerService.java:486)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
      at weblogic.application.services.BackgroundDeploymentManagerService$BackgroundDeployAction.run(BackgroundDeploymentManagerService.java:396)
      at weblogic.application.services.BackgroundDeploymentManagerService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentManagerService.java:458)
      at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:666)
      at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:348)
      at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333)
      at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:54)
      at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
      at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:640)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:406)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:346)

      ####<2020.02.19., 11:55:42,803 DE CET> <[ACTIVE] ExecuteThread: ‘0’ for queue: ‘weblogic.kernel.Default (self-tuning)’> <> <> <1582109742803> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <Destroying application-scoped data source java:comp/DefaultDataSource, created for Application consoleapp, Module null.>
      ####<2020.02.19., 11:55:42,813 DE CET> <[ACTIVE] ExecuteThread: ‘0’ for queue: ‘weblogic.kernel.Default (self-tuning)’> <> <> <1582109742813> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <Error deploying Internal Application: weblogic.application.ModuleException: java.lang.NoSuchMethodError: com.vopm.backend.ConfigController.setEnabled(Z)V
      weblogic.application.utils.StateChangeException: weblogic.application.ModuleException: java.lang.NoSuchMethodError: com.vopm.backend.ConfigController.setEnabled(Z)V
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:58)
      at weblogic.application.services.BackgroundDeploymentManagerService$BackgroundDeployAction.run(BackgroundDeploymentManagerService.java:396)
      at weblogic.application.services.BackgroundDeploymentManagerService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentManagerService.java:458)
      at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:666)
      at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:348)
      at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333)
      at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:54)
      at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
      at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:640)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:406)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:346)
      Caused By: weblogic.application.ModuleException: java.lang.NoSuchMethodError: com.vopm.backend.ConfigController.setEnabled(Z)V
      at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:140)
      at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124)
      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:233)
      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:228)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
      at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:78)
      at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:52)
      at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:754)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
      at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:264)
      at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:66)
      at weblogic.application.services.BackgroundDeploymentManagerService$2.next(BackgroundDeploymentManagerService.java:486)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
      at weblogic.application.services.BackgroundDeploymentManagerService$BackgroundDeployAction.run(BackgroundDeploymentManagerService.java:396)
      at weblogic.application.services.BackgroundDeploymentManagerService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentManagerService.java:458)
      at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:666)
      at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:348)
      at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333)
      at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:54)
      at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
      at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:640)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:406)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:346)
      Caused By: java.lang.NoSuchMethodError: com.vopm.backend.ConfigController.setEnabled(Z)V
      at com.wlsdm.U.A.D(StartupProcess.java:145)
      at com.wlsdm.U.A.fire(StartupProcess.java:97)
      at com.wlsdm.U.L.init(StartupServlet.java:43)
      at javax.servlet.GenericServlet.init(GenericServlet.java:244)
      at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:343)
      at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:294)
      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:326)
      at weblogic.security.service.SecurityManager.runAsForUserCode(SecurityManager.java:197)
      at weblogic.servlet.provider.WlsSecurityProvider.runAsForUserCode(WlsSecurityProvider.java:203)
      at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:71)
      at weblogic.servlet.internal.StubSecurityHelper.initServletInstance(StubSecurityHelper.java:99)
      at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:87)
      at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:71)
      at weblogic.servlet.internal.StubLifecycleHelper.(StubLifecycleHelper.java:57)
      at weblogic.servlet.internal.StubLifecycleHelper.(StubLifecycleHelper.java:31)
      at weblogic.servlet.internal.ServletStubImpl.initStubLifecycleHelper(ServletStubImpl.java:673)
      at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:612)
      at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:2054)
      at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:2031)
      at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1920)
      at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3091)
      at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1849)
      at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:882)
      at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:360)
      at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:356)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
      at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:138)
      at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124)
      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:233)
      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:228)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
      at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:78)
      at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:52)
      at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:754)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
      at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:264)
      at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:66)
      at weblogic.application.services.BackgroundDeploymentManagerService$2.next(BackgroundDeploymentManagerService.java:486)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
      at weblogic.application.services.BackgroundDeploymentManagerService$BackgroundDeployAction.run(BackgroundDeploymentManagerService.java:396)
      at weblogic.application.services.BackgroundDeploymentManagerService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentManagerService.java:458)
      at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:666)
      at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:348)
      at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333)
      at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:54)
      at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
      at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:640)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:406)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:346)

      M 1 Reply Last reply Reply Quote 0
      • wlsdmsupport
        WLSDM Support last edited by

        SOLUTION:
        The agent.jar was in the lib folder. The lib folder was on classpath.
        I repaced the agent.jar. This solved the issue.

        Thanks a lot.

        WLSDM Community Support Team

        1 Reply Last reply Reply Quote 0
        • M
          maas @neuron last edited by

          Hi @neuron,

          I think you installed the wlsdm.war file as a deployment.

          Please check your installation:

          https://wlsdm.com/docs/README#IV.Installation
          …

          • Add wlsdm_agent.jar to managed servers’ JVM Arguments ${JAVA_OPTIONS}*
          • Copy wlsdm.war file to WebLogic domain’s console-ext folder
          1 Reply Last reply Reply Quote 0
          • N
            neuron last edited by

            Hi Maas,

            unfortunately no. I followed the installation steps.
            I did not install as deployment, i placed the war file into the domain console-ext folder (where the WLSDM folder is).

            M 1 Reply Last reply Reply Quote 0
            • M
              maas @neuron last edited by

              Hi @neuron,

              What is your exact (full) WLSDM version?

              wlsdm_agent.jar/META-INF/MANIFEST.MF

              image.png

              1 Reply Last reply Reply Quote 0
              • N
                neuron last edited by

                Hi Maas,

                I use the latest version, i downloaded it yesterday.
                The agent’s works
                <Wed Feb 19 12:00:22 CET 2020>
                , the problem is with the war file, when the admin server starts.

                Here is the agent’s manifest header:
                Manifest-Version: 1.0
                Ant-Version: Apache Ant 1.9.4
                Created-By: yGuard Bytecode Obfuscator 2.5.2
                Built-By: WLSDM Builder | wlsdm.com
                Premain-Class: com.wlsdm.C.A.A
                WLSDM-Version: v3.7.2-b3423
                Built-On: 2019.05.11
                Boot-Class-Path: lib/javassist.jar lib/gson-2.8.5.jar
                Agent-Class: com.wlsdm.C.A.A
                Built-At: 09:59:52 AM VET
                Can-Redefine-Classes: true
                Main-Class: com.wlsdm.C.A.A
                Can-Retransform-Classes: true
                Build-Id: true

                1 Reply Last reply Reply Quote 0
                • wlsdmsupport
                  WLSDM Support last edited by

                  Hi @neuron,

                  Could you mail us for below informations with your official account to [email protected] please?

                  -OS and OS version
                  -Full Java version
                  -Full WebLogic version
                  -Are you using WebLogic partition?
                  -Installed FMW productions

                  Regards.

                  WLSDM Community Support Team

                  1 Reply Last reply Reply Quote 0
                  • wlsdmsupport
                    WLSDM Support last edited by

                    SOLUTION:
                    The agent.jar was in the lib folder. The lib folder was on classpath.
                    I repaced the agent.jar. This solved the issue.

                    Thanks a lot.

                    WLSDM Community Support Team

                    1 Reply Last reply Reply Quote 0
                    • 1 / 1
                    • First post
                      Last post

                    WLSDM: Native WebLogic Monitoring & Diagnostics

                    Copyright © 2021 WLSDM Community & Support Portal | WLSDM.COM | WLSDM Blog