Troubleshooting Web servers

 

Troubleshooting Web servers

 

+

Search Tips   |   Advanced Search

 

  1. Problem: Some pages are not available when using Microsoft IIS 6.0
  2. Problem: configureWeb_server_name command fails on UNIX

 

Problem: Some pages are not available when using Microsoft IIS 6.0

When attempting to access some pages using Internet Information Server 6.0, you might receive an HTTP 400 - Bad Request error.

Solution: Update the value of the UrlSegmentMaxLength key in the registry. Refer to the INF: Http.sys Registry Settings for IIS for more details on updating Web server settings in the registry.

Attention: Incorrectly editing the registry could severely damage the system, requiring us to reinstall the operating system. Before making changes to the registry, you should back up any critical data.

  1. Open the Registry Editor...

    Start | Run regedit

  2. Locate the key...

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters

  3. Create a value named UrlSegmentMaxLength, with a type of DWORD and a value of 0 to indicate an unbounded length.

  4. Exit the Registry Editor by clicking File > Exit, and restart the Windows operating system.

 

Problem: configureWeb_server_name command fails on UNIX

When configuring a Web server on some UNIX systems, the configureWeb_server_name.sh command might fail, with an error similar to the following: 

Configuration save is not complete, exception = com.ibm.ws.scripting.ScriptingException: 
    com.ibm.websphere.management.exception.ConfigServiceException: 
        com.ibm.websphere.management.exception.ConnectorException:
ADMC0009E: The system failed to make the SOAP RPC call: invoke WASX7309W: No "save" was performed before the script "configureWebserverDefinition.jacl" 
    exited; configuration changes will not be saved.

Solution: Increase the timeout value for the type of connection you are using:

  • SOAP connection: Edit the file was_profile_root/properties/soap.client.properties, and increase the value for the com.ibm.SOAP.requestTimeout property to 6000. The value is in seconds.

  • RMI connection: Edit the file was_profile_root/properties/sas.client.props, and increase the value for the com.ibm.CORBA.requestTimeout property to 6000. The value is in seconds.