Failure in setting RemoteAnonymousRMIT3Enabled/RemoteAnonymousRMIIIOPEnabled flag to false through WLST in all WLS on Azure VM Offers
gnsuryan opened this issue · 2 comments
Failure in setting RemoteAnonymousRMIT3Enabled/RemoteAnonymousRMIIIOPEnabled flag to false through WLST in all WLS on Azure VM Offers
The following exception is thrown, when trying to set RemoteAnonymousRMIT3Enabled and RemoteAnonymousRMIIIOPEnabled to false using WLST
The exception when trying to activate the WLST changes.
Activating all your changes, this may take a while ...
The edit lock associated with this edit session is released once the activation is completed.
WLST lost connection to the WebLogic Server that you were connected to.
This may happen if the server was shut down or partitioned.
You will have to re-connect to the server once the server is available.
Disconnected from weblogic server: admin
This Exception occurred at Wed Jul 20 13:29:12 UTC 2022.
java.lang.RuntimeException: weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException
Error occurred while performing disconnect : Error while Activating changes. : weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException
Use dumpStack() to view the full stacktrace :
Failed to DisableRemoteAnonymousRequests for domain adminDomain
The fix has been tested with all the three offers - Admin Only, Cluster & Dynamic Cluster and found working fine.
The following changes have been made to fix the issue.
- Remove use of WLST to set the RemoteAnonymousRMISettings
- Use WDT (WebLogic Deployment tool) - modelHelp utility to check if the RemoteAnonymousRMISettings related attributes are available as MBeans
- If available, then modify the WDT Domain yaml file to set the RemoteAnonymousRMISettings to false
- If not available, no change is required in the WDT Domain yaml file