IBM Support

An application server that is registered to an administrative agent might have a corrupted or unusable profile

Troubleshooting


Problem

An application server that is registered to an administrative agent can have a corrupted or unusable profile. If your application server profile becomes corrupted or unusable and it is registered to an administrative agent, you might not be able to unregister the application server with the []deregisterNode[] command. The profile still exists in the list of profiles to select in the administrative agent console even though you cannot use the application server.

Diagnosing The Problem

When attempting to unregister a profile that is in the administrative agent /bin directory, a null pointer exception can result. If you receive the null pointer exception, the process to unregister the application server from the administrative agent has failed. Error messages that are similar to the following occur in the error log files:



ADMU0116I: Tool information is being logged in file
           C:\Program Files\IBM\WebSphere\AppServer70\profiles\
           AdminAgent01\logs\deregisterNode.log
ADMU0128I: Starting tool with the AdminAgent01 profile
ADMU0211I: Error details may be seen in the file:
           C:\Program Files\IBM\WebSphere\AppServer70\profiles\
           AdminAgent01\logs\deregisterNode.log
ADMU0113E: Program exiting with error:
           com.ibm.websphere.management.exception.
           AdminException:
           java.lang.NullPointerException, resulting from:
           java.lang.NullPointerException
ADMU1211I: To obtain a full trace of the failure, use the
           -trace option.
ADMU0211I: Error details may be seen in the file: C:\Program
           Files\IBM\WebSphere\AppServer70\profiles\
           AdminAgent01\logs\deregisterNode.log

Resolving The Problem

    Complete the following steps to resolve this issue:
    1. Attempt to unregister the application server node with the deregisterNode command. For more information on the dergisterNode command, see the Information Center for IBM WebSphere Application Server Version 7.0. If the unregistering process fails, go to the administrative agent /bin directory to start the wsadmin tool and complete the following steps:
      1. On the command line, issue the following command from the administrative agent /bin directory: wsadmin

      2. Issue the following command:

        $AdminConfig list ManagedNode

        Find the node name in the list of the profile that you are removing. Copy and paste the node name into the command in the next step.

      3. Issue the following wsadmin commands:
        (The set command is split on three lines for publication.)
        set mn isthmusNode09(cells/mymachineCell01/managednodes/mymachineNode01| managednode.xml#ManagedNode_1215721275640
        $AdminConfig remove $mn
        $AdminConfig save
        quit

    2. Restart the administrative agent. The profile should be removed from the administrative agent. To restart the administrative agent, access the /bin directory of the administrative agent profile and issue the following commands:

      stopServer adminagent
      startServer adminagent

    3. Use the manageprofiles command to delete the corrupted application server profile.

Related Information

Release notes for Version 7.0

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Administrative Console (all non-scripting)","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.0","Edition":"Base;Express;Network Deployment","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 June 2018

UID

swg21317144

Page Feedback