Resolve "java.lang.reflect.InvocationTargetException ADMU3002E ADMU3007E ADMU0111E" when attempting to stop WebSphere dmgr

Home > Search
  by

When issuing the stopManager.sh (Linux) or stopManager.bat (Windows) command to stop the WebSphere Deployment Manager (dmgr), the console displays the following.

~]# ./stopManager.sh
ADMU3100I: Reading configuration for server: dmgr
java.lang.reflect.InvocationTargetException
Caused by: java.lang.NullPointerException

 

The following errors should appear in the was_home/profiles/your_profile/logs/dmgr/stopServer.log.

ADMU3002E: Exception attempting to process server dmgr
ADMU3007E: Exception java.lang.reflect.UndeclaredThrowableException
ADMU0111E: Program exiting with error: java.lang.reflect.UndeclaredThrowableException

 

These errrors mean that the username and password being used to stop the dmgr is not a valid username and password. To put this another way, the username and password being used does not exist in WebSphere users. We know that this is due to the username and password being invalid because if a valid username and password were used, the dmgr would be stopped, or a different message like the one displayed below would appear in the console.

ADMU0111E: Program exiting with error: javax.management.JMRuntimeException: 
ADMN0022E: Access is denied for the stop operation on Server MBean because of insufficient or empty credentials.
ADMU4113E: Verify that username and password information is correct. 
           If running tool from the command line, pass in correct -username and -password. 
           Alternatively, update the <conntype>.client.props file.

 

If the -user your_username -password your_password options were used with the stopManager.sh / stopManager.bat command, you may have simply mistyped the username and password.

~]# ./stopManager.sh -user your_username -password your_password

 

If the -user your_username -password your_password options were not used with the stopManager.sh / stopManager.bat command, then the username and password in the soap.client.props file will be used. You will want to ensure that the soap.client.props has the username and password of a WebSphere user

~]# cat was_home/profiles/your_profile/properties/soap.client.props
com.ibm.SOAP.loginUserid=your_username
com.ibm.SOAP.loginPassword=your_password

 

These errors do not mean that the user lacks the permission to issue the stopManager.sh / stopManage.bat command. A different set of errors appear when a valid username and password are being used, but the user lack the appropriate permissions to stop the dmgr.



Add a Comment




We will never share your name or email with anyone. Enter your email if you would like to be notified when we respond to your comment.




Please enter in the box below so that we can be sure you are a human.




Comments