WebSphere

 

Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows

 

Troubleshoot the cluster

If you experience a problem with the operation of IBM® WebSphere® Portal Express, refer to the Search the product documentation for a solution of the WebSphere Portal Express information center to determine whether it is a known problem for which a workaround might exist. You can also review a list of problems addressed by interim fixes and service packs at the Support site: http://www.ibm.com/software/genservers/portalexpress/support/. Be sure to also look at Technotes section on the WebSphere Portal Express support site for any additional known issues and workarounds which might have been identified after the initial release.

WebSphere Portal Express uses and depends on the IBM WebSphere Application Server infrastructure. Often an underlying issue in WebSphere Application Server can affect WebSphere Portal Express, so it can be helpful to monitor the WebSphere Application Server support site for known issues, fixes, and workarounds.

For information related to specific components, see the appropriate troubleshooting topic:

 

Problem: "Error 503: Failed to load target servlet [portal]" received when attempting to access WebSphere Portal Express

After federating a WebSphere Portal Express node and then attempting to access the WebSphere Portal Express, you might receive an "Error 503: Failed to load target servlet [portal]" message in the browser. In addition a message similar to the following message is generated in the WebSphere Portal Express log file: 

2004.09.15 11:18:08.428 E com.ibm.wps.engine.Servlet init   EJPFD0016E: Initialization of service failed. - StackTrace follows...
Solution: When this error occurs, it could indicate that you have not updated the deployment manager configuration for the new WebSphere Portal Express node. To perform this update...

  1. Ensure that the CellName property in the wpconfig.properties file is set for the new WebSphere Portal Express.

    • Specify the name of the cell to which the WebSphere Portal Express node belongs.

    • The cell name can be identified by the was_config_root/cells/cell directory on the node, where cell indicates the cell to which the node belongs.

  2. Update the deployment manager configuration for the new WebSphere Portal Express:

    The post-portal-node-federation-configuration task requires complete and accurate database information in the wpconfig_dbdomain.properties file. Before running the task, ensure that the database properties are correct and that password values are specified.

 

WebSphere Portal Express does not start due to missing class file: com/ibm/wps/services/puma/AccessBean

When attempting to access a WebSphere Portal Express cluster for the first time through an external Web server, you might receive an Error 503 response. In addition, the following messages are generated in the WebSphere Portal Express log file: 

com.ibm.hrl.pse.portlets.WebScannerManager getSecretKeyFromCredentialVault java.lang.NoClassDefFoundError: com/ibm/wps/services/puma/AccessBean

 

Solution: This problem can occur when the PortalAdminID property values specified for each node do not match and you enabled security with an LDAP registry. In this situation, the value of PortalAdminID is the fully-qualified distinguished name (DN) of the WebSphere Portal Express administrator. Because the DN is case sensitive, differences in case between PortalAdminID values on the various nodes can cause a problem.

For example, the error can be generated if you have two nodes in the cluster with the following values for PortalAdminId in the wpconfig.properties files:

To correct this problem, ensure that you have used the proper case for the value of the PortalAdminId property and that the property values match on each node in the cluster.

 

addNode command fails with "doMergeConfig failed" error

When attempting to federate a WebSphere Portal Express node, the addNode command might fail with the following error: 

ADMU0040E: Exception on MBean invocation ...
...
com.ibm.websphere.management.exception.AdminException: doMergeConfig failed
This error is caused in turn by a "Too many open files" error. Solution: Increase the number of files that you can open at the same time by using the ulimit command, as described on the WebSphere Application Server support site:
The addNode command with portal installed on node fails with error ADMU0040E MBeanException "doMergeConfig failed" caused by "Too many open files"

 

Performance in cluster degraded due to insufficient threads in default thread pool

To confirm that the thread pool capacity is contributing to any performance issues, verify whether the Tivoli Performance Viewer provided with WebSphere Application Server shows the Percent Maxed metric to remain consistently in the double digits.

Solution: Increase the maximum number of threads allocated for the default thread pool. For specific instructions, refer to the WebSphere Application Server information center:

 

Network error causes cluster install to fail

Problem: A network error that interrupts the connection between the deployment manager and the node can cause your cluster installation to fail. The following is an example of a network error although you may receive a different error depending on where the network error occurs: 

[wsadmin] WASX7017E: Exception received while running file "/opt/IBM/Portal/PortalServer/config/was/wp_ModifyEarAttributesWpsJndiWpsDs.jacl"; exception information: com.ibm.websphere.management.exception.ConnectorException [wsadmin] org.apache.soap.SOAPException: [SOAPException: faultCode=SOAP-ENV:Client; msg=Broken pipe; targetException=java.net.SocketException: Broken pipe]
Solution: The installation program cannot detect the network error and recover. Therefore, run the task that fails manually or uninstall the cluster and then reinstall.

 

Global settings cannot be set in a cluster by using the XML configuration interface

Problem: The XML configuration interface fails with the following error when you try to set global settings in a clustered environment. 

<status element="[global-settings]" result="failed">    
    <message id="EJPXA0043E">com.ibm.wps.command.xml.XmlCommandException: 
                 EJPXA0043E: An error occurred while creating or updating the resource. 
                 [global-settings]</message>     
    <message id="EJPEB0002E">com.ibm.wps.command.CommandException: 
                 EJPEB0002E: An exception occurred.</message>      
    <message>java.security.PrivilegedActionException: java.lang.NullPointerException</message>
</status>

 

Cause: The global settings are stored in the WebSphere Application Server (WAS). For changes to the global settings a WAS API call is invoked. During this call the following exception is thrown in the clustered environment: 

Caused by: java.lang.NullPointerException 	
     at  at com.ibm.wps.services.ServiceHelper$4.run(Unknown Source) 	
     at  at com.ibm.ws.security.auth.distContextManagerImpl.runAs(distContextManagerImpl.java:2782)
     ... 43 more

Solution

To configure these settings, configure them directly in the administrative console, or use the normal configuration task update-properties.

 

Cluster member startup does not complete due to "Waiting for HAManager" error

When attempting to start a cluster member, the startup process appears to be suspended and does not complete, and the SystemOut.log file displays the following error: 

CWRLS0030W: Waiting for HAManager to activate recovery processing for local WebSphere server

The high availability manager for WebSphere Application Server is unable to establish communication due to a port conflict on the DCS_UNICAST_ADDRESS port used by the cluster member.

Solution: Complete the following steps to correct this problem:

  1. Log in to the deployment manager's administrative console.

  2. Click Servers > Application Servers, and select the server that corresponds to the cluster member that is failing to start.

  3. Click Ports, and then click DCS_UNICAST_ADDRESS.

  4. Modify the port number to a unique port number.

  5. Click Apply, and save your configuration changes.

  6. Restart the cluster member.

 

Parent topic:

Search the product documentation for a solution