Mar 9, 2022
“Request-URI Too Long” Error on the Final Screen of WLSDM Wizard
One of the community user getting error on the final screen of WLSDM wizard. The screenshot and logs as below.
####<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)
Solution:
OHS port then use WebLogic AdminServer port which is pointed in below screen capture.
• Go to AdminServer > Protocols > General and increase the “Maximum Message Size” to “100000000”.
• Then click the HTTP section and make sure “Max Post Size” is “-1”.
Finally, activate your changes, restart the AdminServer and try to complete WLSDM Installation Wizard again.
Download WLSDM and start proactive monitoring now!
