test

Sun Gathering Debug Data for Sun Java System Application Server

ProcedureTo Collect Required Debug Data for Any Application Server Problem

All problems described in this technical note need basic information collected about when the problem occurred and about the system having the problem. Use this task to collect that basic information.

  1. Note the day(s) and time(s) the problem occurred.

  2. Provide a graphical representation of your deployment. Include all hosts and IP addresses, host names, operating system versions, role they perform, and other important systems such as load balancers, firewalls, and so forth.

  3. Note the version of the operating system.

    Solaris OS

    uname -a

    HP-UX

    uname -r

    Linux

    uname -a

    Windows

    C:\Program Files\Common files\Microsoft Shared\MSInfo\msinfo32.exe /report C:\report.txt

  4. Note the patch level.

    Solaris OS

    patchadd -p

    HP-UX

    swlist

    Linux

    rpm -qa

    Windows

    Already provided in the C:\report.txt file above.

  5. Note the version of Application Server.

    If a configured JDK is used instead of the default JDK (usually installed in $AS_HOME/jdk) then provide the output of the command java -version. The Application Server version can be shown with the asadmin version command:


    asadmin version --verbose=true

  6. Create a tar file of the Application Server main domain configuration directory and their node agents.

    This step varies depending on the type of Application Server configuration you are debugging:

    • Domain Administration Server (DAS)

    • Node Agent (lightweight agent that is required on every machine that hosts server instances, including the machine that hosts the DAS)

    • Instance (an individual Application Server instance, either clustered or standalone)

    Note –

    The locations referenced in these instructions are the default locations for Application Server and are provided for illustrative purposes only. If you have started a domain with the --domaindir argument or a node agent with the --agentdir argument, be sure to use your custom directory paths for server-root.

    • DAS

      On the main domain machine:

      Solaris, HP-UX, Linux

      cd server-root/domains/domainname/config

      Create a tar file of the server-rootdomains/domainname/config directory.

      Windows

      cd server-root\config

      Create a zip file of the server-root\config directory.

    • Node Agents

      On the node agent machine:

      Solaris, HP-UX, Linux

      cd server-root/nodeagents/nodeagentname/agent/config

      Create a tar file of the server-root/nodeagents/nodeagentname/agent/config directory.

      Windows

      cd server-root\nodeagents\nodeagentname\agent\config

      Create a zip file of the server-root\nodeagents\nodeagentname\agent\config directory.

    • Instance

      On the instance machine:

      Solaris, HP-UX, Linux

      cd server-root/nodeagents/nodeagentname/instancename/config

      Create a tar file of the server-root/nodeagents/nodeagentname/instancename/config directory.

      Windows

      cd server-root\nodeagents\nodeagentname\instancename\config

      Create a zip file of the server-root\nodeagents\nodeagentname\instancename\config directory.

  7. Get the log files from the Application Server main domain configuration directory and their node agents.

    • DAS

      On the main domain machine:

      Solaris, HP-UX, Linux

      cd server-root/domains/domainame/logs

      Get the access.log and server.log files from the server-root/domains/domainame/logs directory.

      Windows

      cd server-root\domains\domainname\logs

      Get the access.log and server.log files from the server-root\domains\domainname\logs directory.

    • Node Agents

      On the node agent machine:

      Solaris, HP-UX, Linux

      cd server-root/nodeagents/nodeagentname/agent/logs

      Get the server.log file from the server-root/nodeagents/nodeagentname/agent/logs directory.

      Windows

      cd server-root\nodeagents\nodeagentname\agent\logs

      Get the server.log file from the server-root\nodeagents\nodeagentname\agent\logs directory.

    • Instance

      On the instance machine:

      Solaris, HP-UX, Linux

      cd server-root/nodeagents/nodeagentname/instancename/logs

      Get the server.log file from the server-root/nodeagents/nodeagentname/instancename/logs directory.

      Windows

      cd server-root\nodeagents\nodeagentname\instancename\logs

      Get the server.log file from the server-root\nodeagents\nodeagentname\instancename\logs directory.

    Tip –

    If possible, provide just the relevant extracts of log files for the same time period that show the problem, with sufficient context to see what else was occurring during the error occurrence and shortly before. Thus for relatively short log files, send the entire log file, whereas for long-running (hence large) log files, an extract might be more appropriate. In either case, be sure to include all the material from the time of the error as well as at least some lead-in logging from before the error apparently occurred.