WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

  • 1.  Getting ADMU0002E exception

    Posted 24 days ago

    While trying to stop the JVM or check the server status, it prompts for a username and password. If authentication fails, the following exception is thrown:

    ADMU0002E: Exception attempting to process server WasServer01:
               javax.management.JMRuntimeException: ADMN0022E: Access is denied for
               the getState operation on Server MBean because of insufficient or
               empty credentials.

    On the same profile, we have 11 JVMs. Out of these, only one JVM consistently prompts for a username and password.

    Steps I've taken so far to resolve the issue (without success):
    1. Verified the username and password in soap.client.props - everything looks correct.
    2. Performed a clean restart by clearing the temp, wstemp, and config/temp directories.
    Error logs from serverstatus.log
    00000001 AdminTool     A   ADMU0002E: Exception attempting to process server WasServer01: javax.management.JMRuntimeException: ADMN0022E: Access is denied for the getState operation on Server MBean because of insufficient or empty credentials.
            at com.ibm.ws.management.AdminServiceImpl.preInvoke(AdminServiceImpl.java:2514)
            at com.ibm.ws.management.AdminServiceImpl.preInvoke(AdminServiceImpl.java:2317)
            at com.ibm.ws.management.AdminServiceImpl.preInvoke(AdminServiceImpl.java:2103)
            at com.ibm.ws.management.AdminServiceImpl.preInvoke(AdminServiceImpl.java:2076)
            at com.ibm.ws.management.AdminServiceImpl.getAttribute(AdminServiceImpl.java:871)
            at com.ibm.ws.management.connector.AdminServiceDelegator.getAttribute(AdminServiceDelegator.java:141)
            at com.ibm.ws.management.connector.ipc.CallRouter.route(CallRouter.java:194)
            at com.ibm.ws.management.connector.ipc.IPCConnectorInboundLink.doWork(IPCConnectorInboundLink.java:372)
            at com.ibm.ws.management.connector.ipc.IPCConnectorInboundLink$IPCConnectorReadCallback.complete(IPCConnectorInboundLink.java:637)
            at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1833)
            at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:558)
            at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:608)
            at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:985)
            at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1074)
            at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892)


    ------------------------------
    Pavan Kumar Emmidi
    ------------------------------


  • 2.  RE: Getting ADMU0002E exception

    Posted 23 days ago

    Hello Pavan,

      In which version of WAS and OS are you working?

      Please check:
      - In the wasadmin.propeties if your communication is SOAP o SAS.
      - If the credentials a synchronize with DMGR profiles/Dmgr01/properties
      
      Hope this helps.

      Tell us if you need more support
      
    Regards



    ------------------------------
    Gabriel Aberasturi
    Middleware Architect
    Versia Sistemas TI
    ------------------------------

    Original Message


  • 3.  RE: Getting ADMU0002E exception

    Posted 15 days ago

    Hi Gabriel,

    I am working on ND 8.5.5.28, OS - AIX 7.3
    SOAP communication is enabled

    Credentials are in synch with dmgr properties



    ------------------------------
    Pavan Kumar Emmidi
    ------------------------------

    Original Message


  • 4.  RE: Getting ADMU0002E exception

    Posted 23 days ago

    IPCConnector on stacktrace - so it looks like IPC connection ( not SOAP connection).

    So check rather ipc.client.props



    ------------------------------
    Sebastian Tylko
    ------------------------------

    Original Message


  • 5.  RE: Getting ADMU0002E exception

    Posted 15 days ago

    Hi Sebastian,

    Updated credentials in ipc.client.props and able to get server status, which was failing before but didn't understand why only one jvm is using IPC?



    ------------------------------
    Pavan Kumar Emmidi
    ------------------------------

    Original Message


  • 6.  RE: Getting ADMU0002E exception

    Posted 13 days ago

    It must be a difference in connectors configuration of affected server.   

    From console check: 
    Servers -> Websphere application servers -> <serverName> -> Server Infrastructure -> Administration -> Administration services 
    and compare settings (Remote/Local connector:  SOAP Connector vs IPC Connector)

    https://www.ibm.com/docs/en/was/8.5.5?topic=anr-administration-service-settings

    The same you can check in server.xml files for each server - check remoteAdminProtocol & localAdminProtocol entries.



    ------------------------------
    Sebastian Tylko
    ------------------------------

    Original Message


  • 7.  RE: Getting ADMU0002E exception

    Posted 23 days ago

    In addition to Gabriel's response - can you check if you are using security domains so that the one JVM is question is probably using a different user registry? 



    ------------------------------
    Hermann Huebler
    Cloud Architect
    Alpium IT Solutions GmbH
    Vienna
    Austria

    #IBMChampion
    ------------------------------

    Original Message


  • 8.  RE: Getting ADMU0002E exception

    Posted 15 days ago

    Hi Hermann, 

    We are not using any security domains as well as compared WasServer01 & WasServer02 server.xml. Didn't find many differences.



    ------------------------------
    Pavan Kumar Emmidi
    ------------------------------

    Original Message


Related Content