Navigation

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

    SOLVED "Request-URI Too Long" error on the final screen of WLSDM wizard

    General Support & Troubleshooting
    oracle weblogic uri wizard wlsdm
    2
    7
    2462
    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.
    • wlcommunityusers
      wlcommunityusers last edited by wlcommunityusers

      Hi WLSDM team,

      I am getting error on the final screen of WLSM wizard. The screenshot and logs as below.

      Using v. 3.4.2

      Err.png

      ####<Oct 1, 2018 3:19:20 AM UTC><SEVERE><WLSDM><BEA-000000><The client has been closed.
      
      java.io.IOException: The client has been closed.
      	at com.sun.jmx.remote.internal.ClientCommunicatorAdmin.restart(ClientCommunicatorAdmin.java:94)
      	at com.sun.jmx.remote.internal.ClientCommunicatorAdmin.gotIOException(ClientCommunicatorAdmin.java:54)
      	at javax.management.remote.rmi.RMIConnector$RMIClientCommunicatorAdmin.gotIOException(RMIConnector.java:1500)
      	at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.getAttribute(RMIConnector.java:907)
      	at sun.reflect.GeneratedMethodAccessor583.invoke(Unknown Source)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      	at java.lang.reflect.Method.invoke(Method.java:498)
      	at weblogic.management.remote.wlx.ClientProvider$WLXRMIConnectorWrapper$1$1.call(ClientProvider.java:703)
      	at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:284)
      	at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:269)
      	at weblogic.management.remote.wlx.ClientProvider$WLXRMIConnectorWrapper$1.invoke(ClientProvider.java:697)
      	at com.sun.proxy.$Proxy257.getAttribute(Unknown Source)
      	at sun.reflect.GeneratedMethodAccessor583.invoke(Unknown Source)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      	at java.lang.reflect.Method.invoke(Method.java:498)
      	at weblogic.management.remote.wlx.ClientProvider$WLXRMIConnectorWrapper$1$1.call(ClientProvider.java:703)
      	at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:284)
      	at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:269)
      	at weblogic.management.remote.wlx.ClientProvider$WLXRMIConnectorWrapper$1.invoke(ClientProvider.java:697)
      	at com.sun.proxy.$Proxy257.getAttribute(Unknown Source)
      	at com.wlsdm.P.O.getProductionModeEnabled(Unknown Source)
      	at com.wlsdm.P.O.isProduction(Unknown Source)
      	at com.wlsdm.J.F.H(Unknown Source)
      	at com.wlsdm.J.D.hasLicense(Unknown Source)
      	at com.wlsdm.H.a$_A.run(Unknown Source)
      	at java.lang.Thread.run(Thread.java:748)
      

      Community Users Case Notes (Diary)

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

        Hi,

        We will check a couple configuration to find and fix the issue:

        • We want to clarify whether is the port 34210 is OHS port or WebLogic AdminServer port? Please let us know. If it is OHS port then use WebLogic AdminServer port which is pointed in below screen capture.

        _1.png

        • Go to AdminServer > Protocols > General and increase the “Maximum Message Size” to “100000000”.

        _2.png

        • Then click the HTTP section and make sure “Max Post Size” is “-1”.

        _3.png

        Finally, activate your changes, restart the AdminServer and try to complete WLSDM Installation Wizard again.

        Regards.

        WLSDM Community Support Team

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

          Hi,

          This is could be a front-end (JavaScript) issue or an HTTP server issue.

          If you are connecting over a HTTP Server or a load balancer to the WebLogic console, please connect directly while completing the WLSDM installation wizard.

          If you are connecting directly to WebLogic console;

          Could you please retry to finish the wizard starting from the first step. This time open your browser developer console and track the JavaScript and network errors.

          Kind Regards…

          WLSDM Community Support Team

          wlcommunityusers 1 Reply Last reply Reply Quote 0
          • wlcommunityusers
            wlcommunityusers @wlsdmsupport last edited by wlcommunityusers

            Hi Support team,

            PFA the screenshot of browser developer console and the url where it is showing error.

            Regards,

            err2.png

            console/WLSDM/data.controller/providerName=SaveWizardMetrics&DASHBOARD_NAME=Deployments&IDS=0,1,2,3,4,5,6,7,8,91,72,73,74,5,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110&0-METRIC=OpenSessionsCurrentCount&1-METRIC=OpenSessionsCurrentCount&2-METRIC=OpenSessionsCurrentCount&3-METRIC=OpenSessionsCurrentCount&4-METRIC=OpenSessionsCurrentCount&5-METRIC=OpenSessionsCurrentCount&6-METRIC=OpenSessionsCurrentCount&7-METRIC=OpenSessionsCurrentCount&8-METRIC=OpenSessionsCurrentCount&9-METRIC=OpenSessionsCurrentCount&10-METRIC=OpenSessionsCurrentCount&11-METRIC=OpenSessionsCurrentCount&12-METRIC=OpenSessionsCurrentCount&13-METRIC=OpenSessionsCurrentCount&14-METRIC=OpenSessionsCurrentCount&15-METRIC=PendingRequests&65-METRIC=PendingRequests&66-METRIC=PendingRequests&67-METRIC=PendingRequests&68-METRIC=StuckThreadCount&105-METRIC=StuckThreadCount&106-METRIC=StuckThreadCount&107-METRIC=StuckThreadCount&108-METRIC=StuckThreadCount&109-METRIC=StuckThreadCount&110-METRIC=StuckThreadCount&0-TYPE_NAME=weblogic.management.runtime.WebAppComponentRuntimeMBean&1-TYPE_NAME=weblogic.management.runtime.WebAppComponentRuntimeMBean&2-TYPE_NAME=weblogic.management.runtime.WebAppComponentRuntimeMBean&3-
            

            Community Users Case Notes (Diary)

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

              Hi,

              Is the URL has belongs to a web server?
              http://hostname:port/

              if it is; could you please access the WebLogic Admin Console directly and try again?

              *Web servers limits the post size with 4096 bytes (most likely).
              **This limit problem occurs only in the wizard.

              Kind Regards…

              WLSDM Community Support Team

              1 Reply Last reply Reply Quote 0
              • wlcommunityusers
                wlcommunityusers last edited by

                Hi Support team,

                It is the same server like others where I earlier did the WLSDM setup.

                I can access the Weblogic admin console directly.

                Regards,

                Community Users Case Notes (Diary)

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

                  Hi,

                  We will check a couple configuration to find and fix the issue:

                  • We want to clarify whether is the port 34210 is OHS port or WebLogic AdminServer port? Please let us know. If it is OHS port then use WebLogic AdminServer port which is pointed in below screen capture.

                  _1.png

                  • Go to AdminServer > Protocols > General and increase the “Maximum Message Size” to “100000000”.

                  _2.png

                  • Then click the HTTP section and make sure “Max Post Size” is “-1”.

                  _3.png

                  Finally, activate your changes, restart the AdminServer and try to complete WLSDM Installation Wizard again.

                  Regards.

                  WLSDM Community Support Team

                  1 Reply Last reply Reply Quote 0
                  • wlcommunityusers
                    wlcommunityusers last edited by

                    Thanks,

                    The point 1 resolved it. OHS was being used here. Using the listen port helped to resolve the issue.

                    Regards,

                    Community Users Case Notes (Diary)

                    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