Navigation

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

    SOLVED Unable to complete WLSDM configuration

    General Support & Troubleshooting
    2
    9
    415
    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.
    • P
      PrasadTerala last edited by fevzi.korkutata-wlsdmteam

      HI, Getting below error while configuring wlsdm.

      ####<Mar 15, 2024 3:50:11 AM CDT><SEVERE><WLSDM><BEA-000000><For input string: "9223372036854775808"
      
      java.lang.NumberFormatException: For input string: "9223372036854775808"
      
      1 Reply Last reply Reply Quote 0
      • fevzi.korkutata-wlsdmteam
        M.Fevzi Korkutata - WLSDM Team last edited by

        I think you are accessing the WebLogic / WLSDM console through a webserver (OHS, Apache, Nginx… etc.). If yes, please complete WLSDM Wizard installation directly access to console with “WebLogic Admin Server IP: Port”. Do not put any other proxy system such as LoadBalancer, Web server… etc. After direct access to WLSDM console, you would be able to complete the wizard wihout any problem.

        M.Fevzi Korkutata
        WLSDM Product Manager

        P 1 Reply Last reply Reply Quote 0
        • P
          PrasadTerala last edited by fevzi.korkutata-wlsdmteam

          complete log… Is this any license issue?

          ####<Mar 6, 2024 7:28:26 AM CST><INFO><WLSDM><BEA-000000><Initializing the WLSDM properties...>
          ####<Mar 6, 2024 7:28:34 AM CST><INFO><WLSDM><BEA-000000><Setting-up the WLSDM Database...>
          ####<Mar 6, 2024 7:28:41 AM CST><INFO><WLSDM><BEA-000000><WLSDM console deployed successfully. Version: v3.9.2-b4318>
          ####<Mar 6, 2024 7:28:41 AM CST><INFO><WLSDM><BEA-000000><WLSDM garbage collection monitoring initialized successfully.>
          ####<Mar 6, 2024 7:28:41 AM CST><INFO><WLSDM><BEA-000000><WLSDM metric monitoring initialized successfully.>
          ####<Mar 6, 2024 7:28:41 AM CST><INFO><WLSDM><BEA-000000><WLSDM health monitoring initialized successfully.>
          ####<Mar 6, 2024 7:28:41 AM CST><INFO><WLSDM><BEA-000000><WLSDM performance monitoring initialized successfully.>
          ####<Mar 6, 2024 7:28:41 AM CST><INFO><WLSDM><BEA-000000><WLSDM back-end monitoring initialized successfully.>
          ####<Mar 6, 2024 7:28:41 AM CST><INFO><WLSDM><BEA-000000><WLSDM data archiver initialized successfully.>
          ####<Mar 6, 2024 7:28:41 AM CST><INFO><WLSDM><BEA-000000><WLSDM custom DevOps MBean handler initialized successfully.>
          ####<Mar 6, 2024 7:28:41 AM CST><INFO><WLSDM><BEA-000000><WLSDM job scheduler initialized successfully.>
          ####<Mar 6, 2024 7:29:11 AM CST><WARNING><WLSDM><BEA-000000><Has No Valid License. Caused by null/wrong license info.>
          ####<Mar 6, 2024 7:29:12 AM CST><SEVERE><WLSDM><BEA-000000><For input string: "9223372036854775808"
          
          java.lang.NumberFormatException: For input string: "9223372036854775808"
                  at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
                  at java.lang.Long.parseLong(Long.java:596)
                  at java.lang.Long.valueOf(Long.java:803)
                  at com.wlsdm.monitoring.beans.DiskSpaceRuntimePopulator.doLocale(DiskSpaceRuntimePopulator.java:135)
                  at com.wlsdm.monitoring.beans.DiskSpaceRuntimePopulator.run(DiskSpaceRuntimePopulator.java:70)
                  at com.wlsdm.monitoring.beans.GlobalPopulatorControl$Executer.run(GlobalPopulatorControl.java:49)
                  at java.lang.Thread.run(Thread.java:750)
          
          fevzi.korkutata-wlsdmteam 1 Reply Last reply Reply Quote 0
          • fevzi.korkutata-wlsdmteam
            M.Fevzi Korkutata - WLSDM Team @PrasadTerala last edited by fevzi.korkutata-wlsdmteam

            @prasadterala

            Hi Prasad,

            There are two errors available in here. One is license issue; for that please raise a support ticket through our support system if you have an active enterprise support subscription.

            The second one which is “NumberFormatException” might be something about your WebLogic domain or VM server disk mount settings. WLSDM is received a value which is not excepted as usual based on your domain.

            Is there any screen capture or detail about your error? In which step you are facing this error? We need to reproduce your case to be able to give you support about your issue.

            Kind Regards…

            M.Fevzi Korkutata
            WLSDM Product Manager

            P 1 Reply Last reply Reply Quote 0
            • P
              PrasadTerala @fevzi.korkutata-wlsdmteam last edited by

              @fevzi-korkutata-wlsdmteam Thanks Fevzi, for your response. We are still exploring WLSDM so we are still on trial license. Since it is trial license why are we getting invalid license error?

              Issue happens at the Monitoring and diagnostics setup (step 8).

              P fevzi.korkutata-wlsdmteam 3 Replies Last reply Reply Quote 1
              • P
                PrasadTerala @PrasadTerala last edited by

                @prasadterala wlsdm-error.PNG

                1 Reply Last reply Reply Quote 0
                • fevzi.korkutata-wlsdmteam
                  M.Fevzi Korkutata - WLSDM Team @PrasadTerala last edited by

                  @prasadterala said in Unable to complete WLSDM configuration:

                  @fevzi-korkutata-wlsdmteam Thanks Fevzi, for your response. We are still exploring WLSDM so we are still on trial license. Since it is trial license why are we getting invalid license error?

                  Issue happens at the Monitoring and diagnostics setup (step 8).

                  Then ignore the license issue, that’s not your case indeed.

                  Try not to select backend monitoring while trying to complete wizard. Then you can add further backend monitoring settings after wizard completion.

                  M.Fevzi Korkutata
                  WLSDM Product Manager

                  1 Reply Last reply Reply Quote 0
                  • fevzi.korkutata-wlsdmteam
                    M.Fevzi Korkutata - WLSDM Team @PrasadTerala last edited by

                    @prasadterala

                    Additionally, which OS are you using? Please reply back the exact OS version.

                    M.Fevzi Korkutata
                    WLSDM Product Manager

                    1 Reply Last reply Reply Quote 0
                    • fevzi.korkutata-wlsdmteam
                      M.Fevzi Korkutata - WLSDM Team last edited by

                      I think you are accessing the WebLogic / WLSDM console through a webserver (OHS, Apache, Nginx… etc.). If yes, please complete WLSDM Wizard installation directly access to console with “WebLogic Admin Server IP: Port”. Do not put any other proxy system such as LoadBalancer, Web server… etc. After direct access to WLSDM console, you would be able to complete the wizard wihout any problem.

                      M.Fevzi Korkutata
                      WLSDM Product Manager

                      P 1 Reply Last reply Reply Quote 0
                      • P
                        PrasadTerala @fevzi.korkutata-wlsdmteam last edited by

                        @fevzi-korkutata-wlsdmteam Thanks much Fevzi. Bypassing loadbalancer url, I’m able to complete the configuration.

                        Regards,
                        T N Prasad

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

                        WLSDM: Native WebLogic Monitoring & Diagnostics

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