[AIX Solaris HP-UX Linux Windows][IBM i]

Application Server start or restart problems

If a server process does not start or starts with errors, the following topics might help you to diagnose the problem.

Installation program completes successfully, but an application server does not start, or starts with errors

Note: 這個主題參照一或多個應用程式伺服器日誌檔。 此外,在分散式和 IBM® i 系統上,另外也建議您可以配置伺服器來使用「高效能可延伸記載 (HPEL)」日誌和追蹤基礎架構,而不使用 SystemOut.log、SystemErr.log, trace.log 及 activity.log 檔案。HPEL 與原生 z/OS® 記載機能也可以一起使用。如果您使用 HPEL,則可以從伺服器設定檔 bin 目錄,利用 LogViewer 指令行工具來存取您所有的日誌和追蹤資訊。請參閱有關利用 HPEL 疑難排解應用程式的資訊,以取得更多使用 HPEL 的相關資訊。
  • Browse the Application Server log files for clues. The log files are located by default in:
    • [Linux][AIX HP-UX Solaris]profile_root/logs/server_name/SystemErr.log and SystemOut.log
    • [Windows]profile_root\logs\server_name\SystemErr.log and SystemOut.log
    • [IBM i]profile_root/logs/server_name/SystemErr.log and SystemOut.log
    Several applications deployed on an application server or node can take time to start. Browse the SystemOut.log periodically and look at the most recent updates to see if the server is still starting up.
  • [Linux][AIX HP-UX Solaris]The tail -f profile_root/ logs/server_name/SystemOut.log command is a convenient way to watch the progress of the server.
  • Look for any errors or warnings relating to specific resources with the module, such as web modules, enterprise beans and messaging resources. If you find any, examine the application server configuration file for the configuration settings of that resource. Then restart the server to see if this component causes the problem.

    [AIX Solaris HP-UX Linux Windows]For example, in a base or non-distributed configuration on Windows systems, browse profile_root\config\cells/ApplicationServerCell\nodes\node_name\servers\server_name\server.xml, and examine the XML tags for the properties of that resource. Change its initialState value from START to STOP.

    [IBM i]For example, browse profile_root/config/cells/ApplicationServerCell/nodes/node_name/servers/server_name/server.xml, and examine the XML tags for the properties of that resource. Change its initialState value from START to STOP.

  • Look up any error or warning messages in the message reference table by clicking the Reference view of the information center navigation and expanding Messages in the navigation tree.
  • After you create an application server, you must synchronize the nodes before saving the configuration settings for the new server. If you do not synchronize the nodes, your new server might not start.
    1. On the Applications server page listing all of your application server, click Preferences.
    2. Select Synchronize changes with Nodes, if it is not already selected.
    3. Click Apply and then click Application servers to return to your list of application servers.
    4. Click Save to save the configuration settings for the new server.
  • Verify that the logical name that you specified to appear on the console for your application server does not contain invalid characters like: - / \ : * ? " < > and leading or trailing spaces.
  • If you are using Apache Derby and receive an ERROR XSDB6: Another instance of Apache Derby might have already booted the database databaseName error when starting the application server, consult the topic Data access problems for more information.
  • [AIX Solaris HP-UX Linux Windows]When using a non-root user ID to run application servers, verify that:
    • The non-root user has write access to the app_server_root/temp directory.
    • The JVM has write access to app_server_root/config/plugin-cfg.xml file.
    • The non-root user has access to the logs directory.
  • [IBM i]When using a user profile other than QEJBSVR to run an application server, verify that:
    • The user profile has QEJBSVR specified as its group profile.
    • QEJBSVR is the owner of all files and directories under the profile_root directory. You can use the following command in a Qshell session to set QEJBSVR as the owner:
      chown -R QEJBSVR profile_root
  • The application server might not start in the restricted mode. You can configure an application server to allow or restrict access to internal server classes. The default is to allow access. If access is restricted, the server might not start. If the application server does not start in Restrict mode, change the access to internal classes to Allow.

An error message might appear in the SystemOut.log after restarting an application server

The following error message might appear in the SystemOut.log after restarting an application server:
The socket bind failed for host hostname and port portnumber.  The port may already be in use.

This problem might occur if the network is slow, and the port listed in the message text did not finish listening when the application was stopped and restarted.

To verify that this is the problem, check the port status.

To correct this problem, wait for a few minutes after stopping the server:
  1. [AIX Solaris HP-UX Linux Windows]Verify that no ports are listening. Use the command:
    netstat -a 
  2. [IBM i]Verify that no ports are listening. Use this CL command:
    NETSTAT *CNN
  3. Restart the server

Message "DiscoveryService.sendQuery" exception appears in the FFDC log file

When you start a deployment manager, the deployment manager attempts to discover any configured node agents within its cell. If the deployment agent does not discover the node agents in the cell, it writes an exception to the first failure data capture (FFDC) log file for each node agents that the deployment manager does not discover. If the node agents are not suppose to be running, you can ignore the exception. If the node agents are suppose to be running, the FFDC log file might contain additional information that will help you determine why the deployment manager cannot discover the node agents even though the node agents are suppose to be running.

[IBM i]

The server does not restart on IBM i after applying WebSphere Application Server Version 8.5.0.1

If the server does not restart on IBM i after applying 8.5.0.1, you might receive the following message: "CWWKE0044E: There is no write permission for server directory."

This error occurs only on IBM i when started with OS integration and using the QEJBSVR user.

You can temporarily resolve this by wrapping an invocation of the server command with a script that deletes the contents of the <serverName>/workarea/.sCommandAuth directory.

「IBM 支援中心」提供各種文件和工具,節省收集解決問題所需資訊的時間。在開啟問題報告之前,請先參閱 Support 頁面:

指出主題類型的圖示 參照主題



時間戳記圖示 前次更新: July 9, 2016 8:10
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-base-dist&topic=rtrb_appsrvstart
檔名:rtrb_appsrvstart.html