WebSphere Application Server 4.x Plugin Error Messages
 Technote (FAQ)
 
Problem
What do the error messages for the WAS 4.x Plugin mean?
 
Solution
Initialization Cause/Resolution
  • Message: ws_common: websphereUpdateConfig: Failed to create the parser object for %s
  • Cause: The creation of the config parser failed. The only reason you would see this is if memory allocation failed (malloc returned NULL).
  • Resolution: Reboot the machine and try again.
  • Message: ws_common: websphereUpdateConfig: Failed parsing the plugin config file
  • Cause: A syntax error in the config file or some invalid setting in the config file. Other messages should be printed out prior to this one that will help lead you to the problem.
  • Resolution: Check the previous messages and fix the problems associated with them
.
  • Message: ws_common: websphereUpdateConfig: Failed to open log: %s
  • Cause: The log file that the plugin uses to write errors to failed to be opened. This could be because an invalid path was entered or the user the webserver is running as doesn't have the permissions needed to open or write to the path being used.
  • Resolution: Check the setting in the plugin config file to make sure that the path is valid. If you have a valid path there ensure the user the webserver is running under has the necessary permissions for the log file to be created/opened for writing.
  • Message: ws_common: websphereGetConfigFilename: Failed to open registry: %s
  • Cause: WIN32 only. The windows registry could not be opened or the key we are trying to read from does not exist.
  • Resolution: Add the key to the registry by hand will solve this problem but other keys WebSphere needs are also likely to be missing/corrupted so other problems are likely to occur.
  • Message: ws_common: websphereGetConfigFilename: Failed to get keysize or keysize too long: %d for confFile: %d
  • Cause: The value of the key we are reading could be determined or the lengh of the path to the config file is too long.
  • Resolution: The value of the key must be less than 255 in order to fit in the static buffer the plugin uses to store the path to the config file.
  • Message: ws_common: websphereGetConfigFilename: Failed to read the key: %s
  • Cause: The attempt to read the value of the key failed.
  • Resolution: I wouldn't expect to see this message since the registry would have been opened at this point and the length of the key determined without error.
  • Message: ws_common: websphereGetConfigFilename: Failed to close registry
  • Cause: The key either got corrupted or was deleted since we opened it.
  • Resolution: Not sure.
  • Message: ws_common: websphereGetConfigFilename: Config file path too long: %d for confFile: %d
  • Cause: UNIX only. The path with WASHOME plug /config/plugin-cfg.xml is too long to fit in the static buffer the plugin uses to store the path to the config file.
  • Resolution: Shorten the installation path of WebSphere.
  • Message: ws_common: websphereInit: no configuration filename specified
  • Cause: No config file was given for the plugin to initialize.
  • Resolution: Shouldn't ever see this since other checks are done prior to make sure that we have the name of the config file.
  • Message: ws_common: websphereInit: strdup() of config file failed
  • Cause: The actual call to strdup failed. This is essentially a memory allocation failure which would mean you have bigger problems then the plugin not working.
  • Resolution: Reboot the machine and try again.
  • Message: ws_common: websphereInit: Failed to create the mutex
  • Cause: The creation of the mutex failed. This is a memory allocation failure. (call to malloc failed)
  • Resolution: Reboot the machine and try again.
  • Message: ws_common: websphereInit: Failed to load the config file
  • Cause: Something in the loading of the configuration went wrong. Possible problems could be the file doesn't exist or a syntax error in the config file.
  • Resolution: Previous error messages should help determine the reason the config file failed to load.
  • Message: ws_common: websphereBeginRequest: Config reloading FAILED; using old config
  • Cause: The plugin attempted to reload the config file because it had changed recently but the reload failed. The plugin will continue using the old configuration until the new configuration can be loaded successfully.
  • Resolution: Previous error messages will help determine the reason that the config file load failed.
  • Message: ws_list: listAddToTail: Failed to create list element
  • Cause: Memory Allocation Failure
  • Resolution: Reboot the machine and try again.
  • Message: ws_property: propertyCreate: Failed to create property
  • Cause: Memory Allocation Failure
  • Resolution: Reboot the machine and try again.
  • Message: ws_route: routeCreate: Failed to create route
  • Cause: Memory Allocation Failure
  • Resolution: Reboot the machine and try again.
  • Message: ws_route: routeSetVhostGroup: Attempted to set a NULL vhost group for route
  • Cause: The name used for the virtual host group in the route does not match the name for any of the virtual host groups you have defined in your configuration.
  • Resolution: Check to make sure the name of the vhost group isn't misspelled in any of your route definitions.
  • Message: ws_route: routeSetUriGroup: Attempted to set a NULL uri group for route
  • Cause: The name used for the uri group in the route does not match the name for any of the uri groups you have defined in your configuration.
  • Resolution: Check to make sure the name of the uri group isn't misspelled in any of your route definitions.
  • Message: ws_route: routeSetServerGroup: Attempted to set a NULL server group for route
  • Cause: The name used for the server group in the route does not match the name for any of the server groups you have defined in your configuration.
  • Resolution:
  • Message: ws_server: serverAddTransport: Failed to initialize server address
  • Cause: The creation of the server address failed. The DNS server is down or the IP address could not be found on the network.
  • Resolution: Try putting the IP address of the machine in the transport definition. Check to see if you can ping whatever value you have defined. If you can't then figure out what the problem is.
  • Message: ws_server: serverAddTransport: Failed to initialize security
  • Cause: The GSK initialization failed. Could be seen if the GSK wasn't installed on the machine or if the install of the GSK was bad. GSK Initialization parameters are incorrect.
  • Resolution: Ensure that the correct GSK version is installed. Check other error messages previous to this one to help determine what exactly went wrong.
  • Message: ws_transport: transportCreate: Failed to create transport
  • Cause: Memory Allocation Failure
  • Resolution: Reboot machine and try again.
  • Message: ws_transport: transportCreate: Failed to create properties list
  • Cause: Memory Allocation Failure
  • Resolution: Reboot machine and try again.
  • Message: ws_transport: transportCreate: Failed to create streams queue
  • Cause: Memory Allocation Failure
  • Resolution: Reboot machine and try again.
  • Message: ws_transport: transportCreate: Failed to create streams queue mutex
  • Cause: Memory Allocation Failure
  • Resolution: Reboot machine and try again.
  • Message: ws_transport: transportInitializeSecurity: Keyring wasn't set
  • Cause: The keyring wasn't set for this transport and we attempted to initialize the GSK without a keyring.
  • Resolution: Check the syntax of the transport in the plugin configuration. It could be that you ended the transport element prematurely and the plugin hadn't read in the properties needed for the GSK to initialize successfully.
  • Message: ws_transport: transportInitializeSecurity: No stashfile or keyring password given
  • Cause: Either the stashfile wasn't set or the password for the keyring and the plugin attempted to initialize the GSK without a keyring.
  • Resolution: Check the syntax of the transport in the plugin configuration. It could be that you ended the transport element prematurely and the plugin hadn't read in the properties needed for the GSK to initialize successfully.
  • Message: ws_transport: transportInitializeSecurity: Failed to initialize security
  • Cause: The GSK initialization failed. Could be seen if the GSK wasn't installed on the machine or if the install of the GSK was bad. GSK Initialization parameters are incorrect.
  • Resolution: Ensure that the correct GSK version is installed. Check other error messages previous to this one to help determine what exactly went wrong.
  • Message: ws_transport: transportSetServerAddress: unable to resolve host name: %s
  • Cause: The hostname given in the plugin configuration could not be resolved.(call to gethostbyname() failed)
  • Resolution: Ensure that DNS is functioning correctly. If you can't ping the value in the plugin configuration the plugin won't resolve the hostname either. Try putting in the IP address and see if that solves the problem.
  • Message: ws_uri: uriCreate: Failed to create uri
  • Cause: Memory Allocation Failure
  • Resolution: Reboot the machine and try again.
  • Message: ws_uri_group: uriGroupCreate: Failed to create uri group
  • Cause: Memory Allocation Failure
  • Resolution: Reboot the machine and try again.
  • Message: ws_vhost: vhostCreate: Failed to create vhost
  • Cause: Memory Allocation Failure
  • Resolution: Reboot the machine and try again.
  • Message: ws_vhost_group: vhostGroupCreate: Failed to create vhost group
  • Cause: Memory Allocation Failure
  • Resolution: Reboot the machine and try again.
  • Message: ws_config: configGetVhostGroup: Failed to find vhost group for %s
  • Cause: A virtual host group with the given name is not defined. Could be a typo or the user just forgot to define the vhost group.
  • Resolution: Fix the typo or define a virtual host group with the specified name.
  • Message: ws_config: configGetUriGroup: Failed to find uri group for %s
  • Cause: A uri group with the specified name is not defined. Could be a typo or the user just forgot to define the uri group.
  • Resolution: Fix the typo or define a uri group with the specified name.
  • Message: ws_config: configGetServerGroup: Failed to find server group for %s
  • Cause: A server group with the specified name is not defined. Could be a typo or the user just forgot to define the server group.
  • Resolution: Fix the typo or define a server group with the specified name.
  • Message: ws_config_parser: configParserParse: Failed to create the sxpParser object for %s
  • Cause: Memory Allocation Error or the file failed to be opened.
  • Resolution: Check the permissions of the config file and ensure the user the webserver is running under has the authority to open the config file for reading.
  • Message: ws_config_parser: websphereUpdateConfig: Failed to parse the config file %s
  • Cause: Syntax error or bad parameters in the config file.
  • Resolution: Check previous messages to determine exactly what the problem is and fix that issue.
  • Message: ws_config_parser: resolveConfigRoutes: Failed to set the vhost group
  • Cause: The given vhost group was not actually defined in the config file.
  • Resolution: Fix the typo or define the vhost in the config file.
  • Message: ws_config_parser: resolveConfigRoutes: Failed to set the uri group
  • Cause: The given uri group was not actually defined in the config file.
  • Resolution: Fix the typo or define the uri group in the config file.
  • Message: ws_config_parser: resolveConfigRoutes: Failed to set the server group
  • Cause: The given server group was not actually defined in the config file.
  • Resolution: Fix the typo or define the server group in the config file.
  • Message: lib_security: updateOSLibpath: Setting the LIBPATH for GSK failed.
  • Cause: Memory Allocation Failure
  • Resolution: Reboot the system and try again.
  • Message: lib_security: updateOSLibpath: Setting the LIBPATH for GSK failed, could not append /usr/opt/ibm/gskkm/lib.
  • Cause: Memory Allocation Failure
  • Resolution: Reboot the system and try again.
  • Message: lib_security: updateOSLibpath: Setting the LD_LIBRARY_PATH for GSK failed.
  • Cause: Memory Allocation Failure
  • Resolution: Reboot the system and try again.
  • Message: lib_security: updateOSLibpath: Setting the LD_LIBRARY_PATH for GSK failed, could not append /usr/lib.
  • Cause: Memory Allocation Failure
  • Resolution: Reboot the system and try again.
  • Message: lib_security: updateOSLibpath: Setting the LD_LIBRARY for GSK failed.
  • Cause: Memory Allocation Failure
  • Resolution: Reboot the system and try again.
  • Message: lib_security: updateOSLibpath: Setting the LD_LIBRARY for GSK failed, could not append /usr/lib.
  • Cause: Memory Allocation Failure
  • Resolution: Reboot the system and try again.
  • Message: lib_security: updateOSLibpath: Setting the SHLIB_PATH for GSK failed.
  • Cause: Memory Allocation Failure
  • Resolution: Reboot the system and try again.
  • Message: lib_security: updateOSLibpath: Setting the SHLIB_PATH for GSK failed, could not append /usr/lib.
  • Cause: Memory Allocation Failure
  • Resolution: Reboot the system and try again.
  • Message: lib_security: loadSecurityLibrary: Failed to load gsk library
  • Cause: The GSK isn't installed or is installed incorrectly. (call to dlopen() failed)
  • Resolution:
  • Message: lib_security: loadSecurityLibrary: gsk_environment_open function undefined
  • Cause: The function name couldn't be found in the library. Incorrect version of the GSK is installed.
  • Resolution: Install the correct version of the GSK.
  • Message: lib_security: loadSecurityLibrary: gsk_environment_close function undefined
  • Cause: The function name could not be resolved. Incorrect version of the GSK installed.
  • Resolution: Install the correct version of the GSK.
  • Message: >lib_security: loadSecurityLibrary: gsk_environment_init function undefined
  • Cause: The function name could not be resolved. Incorrect version of the GSK installed.
  • Resolution: Install the correct version of the GSK.
  • Message: lib_security: loadSecurityLibrary: gsk_environment_init function undefined
  • Cause: The function name could not be resolved. Incorrect version of the GSK installed.
  • Resolution: Install the correct version of the GSK.
  • Message: lib_security: loadSecurityLibrary: gsk_secure_soc_open function undefined
  • Cause: The function name could not be resolved. Incorrect version of the GSK installed.
  • Resolution: Install the correct version of the GSK.
  • Message: lib_security: loadSecurityLibrary: gsk_secure_soc_init function undefined
  • Cause: The function name could not be resolved. Incorrect version of the GSK installed.
  • Resolution: Install the correct version of the GSK.
  • Message: lib_security: loadSecurityLibrary: gsk_secure_soc_close function undefined
  • Cause: The function name could not be resolved. Incorrect version of the GSK installed.
  • Resolution: Install the correct version of the GSK.
  • Message: lib_security: loadSecurityLibrary: gsk_secure_soc_read function undefined
  • Cause: The function name could not be resolved. Incorrect version of the GSK installed.
  • Resolution: Install the correct version of the GSK.
  • Message: lib_security: loadSecurityLibrary: gsk_secure_soc_write function undefined
  • Cause: The function name could not be resolved. Incorrect version of the GSK installed.
  • Resolution: Install the correct version of the GSK.
  • Message: lib_security: loadSecurityLibrary: gsk_attribute_set_numeric_value function undefined
  • Cause: The function name could not be resolved. Incorrect version of the GSK installed.
  • Resolution: Install the correct version of the GSK.
  • Message: lib_security: loadSecurityLibrary: gsk_attribute_get_numeric_value function undefined
  • Cause: The function name could not be resolved. Incorrect version of the GSK installed.
  • Resolution: Install the correct version of the GSK.
  • Message: lib_security: loadSecurityLibrary: gsk_attribute_set_buffer function undefined
  • Cause: The function name could not be resolved. Incorrect version of the GSK installed.
  • Resolution: Install the correct version of the GSK.
  • Message: lib_security: loadSecurityLibrary: gsk_attribute_get_buffer function undefined
  • Cause: The function name could not be resolved. Incorrect version of the GSK installed.
  • Resolution: Install the correct version of the GSK.
  • Message: lib_security: loadSecurityLibrary: gsk_strerror function undefined
  • Cause: The function name could not be resolved. Incorrect version of the GSK installed.
  • Resolution: Install the correct version of the GSK.
  • Message: lib_security: loadSecurityLibrary: gsk_attribute_set_callback function undefined
  • Cause: The function name could not be resolved. Incorrect version of the GSK installed.
  • Resolution: Install the correct version of the GSK.
  • Message: lib_security: initializeSecurity: Unable to load security library
  • Cause: Either couldn't open the GSK library or at least 1 of the functions we tried to resolve the in library failed to get resolved.
  • Resolution: Check previous error messages and fix those.
  • Message: lib_security: initializeSecurity: Failed to set gsk environment
  • Cause: Failed to set the keyring or the stashfile in the GSK environment.
  • Resolution: Check the plugin configuration and make sure the settings in the properties of the transports are correct.
  • Message: lib_security: initializeSecurity: Failed to initialize GSK environment
  • Cause: The enviroment could not be initialized successfully. Bad keyfile, stashfile, or password given to the transport.
  • Resolution: Check previous messages and the parameters specified in the transport properties in the plugin configuration.
  • Message: lib_security: logSSLError: str_security (gsk error %d): %s
  • Cause: Generic error message allowing us to see what the return code from the GSK was.
  • Resolution: Hope that the error code from the GSK offers some suggestions on what the problem might be.
  • Message: lib_security_config: htsecurityConfigCreate: Failed to create security config object
  • Cause: Memory Allocation Failure
  • Resolution: Reboot the machine and try again.
  • Message: lib_sxp: sxpParse: File Lexer returned NULL. line %d of %s
  • Cause: The file lexer reached the end of the file unexpectedly.
  • Resolution: Check the syntax of the config file to make sure it is proper.
  • Message: lib_sxp: sxpParse: Expected '<' token; got '%s'. line %d of %s
  • Cause: The state machine of the plugin parser came across unexpected input in the plugin configuration file.
  • Resolution: Remove the unexpected text.
  • Message: lib_sxp: sxpParse: Expected first dash of comment start; got '%s'. line %d of %s
  • Cause: The state machine of the plugin parser was expecting the other part of a comment but found something else.
  • Resolution: Fix the syntax of the comment.
  • Message: lib_sxp: sxpParse: Expected second dash of comment start; got '%s'. line %d of %s
  • Cause: The state machine of the plugin parser was expecting the other part of a comment but found something else.
  • Resolution: Fix the syntax of the comment.
  • Message: lib_sxp: sxpParse: Expected comment end; got '%s'. line %d of %s
  • Cause: The state machine of the plugin parser was expecting the other part of a comment but found something else.
  • Resolution: Fix the syntax of the comment.
  • Message: lib_sxp: sxpParse: Start element returned FALSE for %s. line %d of %s
  • Cause: The call for starting the element failed and returned false.
  • Resolution: Check previous error messages to help narrow down what exactly might be the problem.
  • Message: lib_sxp: sxpParse: Expected '=' token; got '%s'. line %d of %s
  • Cause: The state machine of the plugin parser came across unexpected text.
  • Resolution: Fix the syntax of the plugin config file.
  • Message: lib_sxp: sxpParse: End element returned FALSE for %s. line %d of %s
  • Cause: The call for ending the element failed and returned false.
  • Resolution: Check the previous error messages to help narrow down what exactly might be the problem.
  • Message: lib_sxp: sxpParse: Expected '>' token or %s; got '%s'. line %d of %s
  • Cause: The state machine of the plugin parser came across unexpected text.
  • Resolution: Fix the syntax of the plugin config file.
  • Message: lib_sxp: sxpParse: Expected '>' token; got '%s'. line %d of %s
  • Cause: The state machine of the plugin parser came across unexpected text.
  • Resolution: Fix the syntax of the plugin config file.
  • Message: mod_app_server_http: as_create_config: memory allocation failed
  • Cause: Memory Allocation Failure
  • Resolution: Reboot the machine and try again.
  • Message: mod_app_server_http: as_init: unable to get module config
  • Cause: The apache module config was not found.
  • Resolution: Don't know why you would ever see this.
  • Message: mod_app_server_http: as_init: unable to initialize websphere
  • Cause: WebSphere Initialization failed.
  • Resolution: Check previous error messages to help narrow down the problem.
  • Message: iis_plugin: GetFilterVersion: Failed to get the config file
  • Cause: The path to the plugin config file could not be found in the registry.
  • Resolution: Fix the registry so that the path to the config file is specified.
  • Message: iis_plugin: GetFilterVersion: Failed to initialize websphere
  • Cause: WebSphere Initialization failed.
  • Resolution: Check previous error messages to help narrow down the problem.
  • Message: ns_plugin: as_init: unable to initialize websphere
  • Cause: WebSphere Initialization failed.
  • Resolution: Check previous error messages to help narrow down the problem.
  • Message: domino5_plugin: FilterInit: Failed to get the config file
  • Cause: The path to the plugin config file could not be found in the registry.
  • Resolution: Fix the registry so that the path to the config file is specified.
  • Message: domino5_plugin: FilterInit: Failed to initialize WebSphere
  • Cause: WebSphere Initialization failed.
  • Resolution: Check previous error messages to help narrow down the problem.
  • Request Processing Cause/Resolution
  • Message: ws_common: websphereHandleRequest: Request Info URI is NULL
  • Cause: Sanity check to make sure the url isn't NULL.
  • Resolution: If the url is NULL then the request isn't valid anyways.
  • Message: ws_common: websphereFindServerGroup: Failed to get the server group
  • Cause: The route we determined we should use didn't have a server group.
  • Resolution: This should be caught during initialization of the plugin configuration so this message should never be seen.
  • Message: ws_common: websphereCreateClient: Failed to create the client
  • Cause: Memory Allocation Failure
  • Resolution: Reboot the machine and try again.
  • Message: ws_common: websphereCreateClient: Failed to get the headers
  • Cause: The request headers could not be read in by the plugin.
  • Resolution: The request is probably invalid so the fix is to send a valid request.
  • Message: ws_common: websphereCreateClient: Failed to add special headers
  • Cause: An error occured adding the special headers.
  • Resolution: The function never fails so this message can't be seen.
  • Message: ws_common: websphereCreateClient: POST request with no content-length
  • Cause: The POST request had no content-length so the plugin doesn't know how much data to read from the client.
  • Resolution: Fix the request so that it has a content-length.
  • Message: ws_common: websphereGetStream: Failed to get a socket, OS err=%d
  • Cause: Socket creation failed. The system is out of socket descriptors.
  • Resolution: There is a socket descriptor leak somewhere and the machine should be rebooted.
  • Message: ws_common: websphereGetStream: Failed to connect to app server, OS err=%d
  • Cause: The plugin could not connect to the app server.(connect() call failed)
  • Resolution: The application server is down or is so busy that it can't handle anymore requests.
  • Message: ws_common: websphereGetStream: Could not open stream
  • Cause: The creation of the stream failed. In the case of a secure stream it could be the result of either the plugin not liking the certificate presented by the app server or if the app server is using client authentication the server may not like the certificate presented by the plugin.
  • Resolution: Ensure that the kdb/jks files being used in by the plugin/app server trust the signer of eachothers certificates.
  • Message: ws_common: websphereExecute: Failed to create the stream
  • Cause: Stream creation failed.
  • Resolution: Check previous error messages to help narrow down what the problem might be.
  • Message: ws_common: websphereExecute: Failed to write with a new stream; App Server may have gone down during write
  • Cause: The write of the request to the app server failed.
  • Resolution: The app server may have gone down while the request was being written or closed the connection causing the write to fail.
  • Message: ws_common: websphereExecute: Failed to read from a new stream; App Server may have gone down during read
  • Cause: The read of the response from the app server failed.
  • Resolution: The app server may have gone down while the response was being read or closed the connection causing the read to fail.
  • Message: ws_common: websphereFindTransport: Unable to find a transport
  • Cause: The server that we attempted to send the request to did not have a transport defined.
  • Resolution: Define a transport to be used when routing requests to this server.
  • Message: ws_common: websphereParseCloneID: Failed to allocate space for clone id from pool
  • Cause: Memory Allocation Failed
  • Resolution: Reboot the machine and try again.
  • Message: ws_common: websphereFindServer: Failed to find a server
  • Cause: A server to handle the request could not be found. It could be that all servers have been marked down and the plugin doesn't have any available to handle the request.
  • Resolution: Bring the app server back up so the plugin can route requests to it.
  • Message: ws_common: websphereHandleRequest: Failed to begin the request
  • Cause: Initialization and checking of the plugin request structure failed.
  • Resolution: Check previous error messages to help narrow down the source of the problem.
  • Message: ws_common: websphereHandleRequest: Failed to create the client
  • Cause: Memory Allocation Failure
  • Resolution: Reboot the machine and try again.
  • Message: ws_common: websphereHandleRequest: Failed to find a server
  • Cause: A server to handle the request could not be found. It could be that all servers have been marked down and the plugin doesn't have any available to handle the request.
  • Resolution: Bring the app server back up so the plugin can route requests to it.
  • Message: ws_common: websphereHandleRequest: Failed to find a transport
  • Cause: The server that we attempted to send the request to did not have a transport defined.
  • Resolution: Define a transport to be used when routing requests to this server.
  • Message: ws_common: websphereHandleRequest: Failed to execute the transaction to '%s'; will try another one
  • Cause: The plugin failed to either write the request or read the response from the application server so it will see if there is another one defined in the server group and try that one.
  • Resolution: Check the app server that the failure occurred to and see if the machine needs to be rebooted or the app server restarted.
  • Message: ws_common: websphereHandleRequest: Failed to find an app server to handle this request
  • Cause: No app server could be found to handle the request. All servers could be marked down.
  • Resolution: Check previous error messages to determine which app server appear to be down and bring them back up.
  • Message: ws_common: websphereHandleRequest: Failed to reply to the browser
  • Cause: The response failed to be sent back to the browser successfully.
  • Resolution: The client hit the stop button or clicked on another linking causing the connection to be closed.
  • Message: ws_common: websphereHandleRequest: Failed to end the config request
  • Cause: An error occured cleaning up some of the plugin request structures at the end of the request.
  • Resolution: This function never returns in error so this message shouldn't ever be seen.
  • Message: ws_server: serverSetFailoverStatus: Marking %s down
  • Cause: The plugin has determined that the specified server is down and has marked it accordingly. It will retry the server in 60 seconds or whatever the specified RetryInterval is for the server group.
  • Resolution: Check the app server to make sure that it hasn't gone down. It could be that it is so busy it can't handle anymore requests.
  • Message: ws_server_group: serverGroupGetServerIterator: group %s server %d of %d is NULL
  • Cause: The server we are trying to use is NULL.
  • Resolution: This should be caught during initialization so this message shouldn't be seen.
  • Message: ws_server_group: serverGroupGetServer: group %s server %d of %d is NULL
  • Cause: The server we are trying to use is NULL.
  • Resolution: This should be caught during initialization so this message shouldn't be seen.
  • Message: ws_server_group: serverGroupFindCloneID: Null clone ID for %s
  • Cause: The server group appears to be using session affinity but the clone id to be used for the specified server can't be found.
  • Resolution: Regen the plugin config so that the clone id can be defined by the app server.
  • Message: ws_server_group: serverGroupNextRoundRobinServer: Failed to find a server; all could be down
  • Cause: The server group that the plugin determined the request should be routed to either contains no servers or all of them are currently marked down.
  • Resolution: Check to make sure the ServerGroup has servers defined for it or look in the log to see if the servers in that group have been marked down recently.
  • Message: ws_transport: transportStreamEnqueue: Tried to enqueue a NULL stream
  • Cause: Just a sanity check to make sure the stream object isn't NULL before we put it on the queue.
  • Resolution: Shouldn't see this message unless a bug has been introduced into the code.
  • Message: lib_htrequest: htrequestCreate: Failed to create request object
  • Cause: Memory Allocation Failure
  • Resolution: Reboot the machine and try again.
  • Message: lib_htrequest: htrequestWrite: Failed to read the first line of the continue response
  • Cause: We are expecting a 100 Continue response from the app server before the request content is sent over to the app server and we didn't read it.
  • Resolution: Shouldn't see this message unless a bug has been introduced on the app server side.
  • Message: lib_htrequest: htrequestWrite: Failed to read correct number of args for continue response
  • Cause: We are expecting a 100 Continue response from the app server before the request content is sent over to the app server sent the response line in the wrong format.
  • Resolution: Shouldn't see this message unless a bug has been introduced on the app server side.
  • Message: lib_htrequest: htrequestWrite: Read %d; not sending the post content
  • Cause: The plugin expected to read more bytes then it actually did based on the content length in the request headers.
  • Resolution: Determine why the client is calculating the content length incorrectly.
  • Message: lib_htresponse: htresponseGetContentBlock: Failed to allocate the content block
  • Cause: Memory Allocation Failure
  • Resolution: Reboot the machine and try again.
  • Message: lib_htresponse: htresponseGetChunk: Failed to allocate the chunk
  • Cause: Memory Allocation Failure
  • Resolution: Reboot the machine and try again.
  • Message: lib_htresponse: htresponseGetChunk: Failed to read the length of the chunk
  • Cause: The app server is sending back an invalid chunked transfer response.
  • Resolution: This error should only be seen if a bug has been introduced on the app server side.
  • Message: lib_htresponse: htresponseGetChunk: Failed to read the length of the chunk after extra blank line
  • Cause: The app server is sending back an invalid chunked transfer response.
  • Resolution: This error should only be seen if a bug has been introduced on the app server side.
  • Message: lib_htresponse: htresponseGetChunk: Failed to scan the chunk length line
  • Cause: The app server is sending back an invalid chunked transfer response.
  • Resolution: This error should only be seen if a bug has been introduced on the app server side.
  • Message: lib_stream: openStream: Failed to create stream
  • Cause: Memory Allocation Failure
  • Resolution: Reboot the machine and try again.
  • Message: lib_stream: openStream: Failed in r_gsk_secure_soc_open: %s(gsk rc = %d)
  • Cause: Call to the GSK failed.
  • Resolution: The return code from the GSK should give you some clues as to what went wrong.
  • Message: lib_stream: openStream: Failed in r_gsk_attribute_set_numeric_value: %s(gsk rc = %d)
  • Cause: Call to the GSK failed.
  • Resolution: The return code from the GSK should give you some clues as to what went wrong.
  • Message: lib_stream: openStream: Failed in r_gsk_secure_soc_init: %s(gsk rc = %d)
  • Cause: Call to the GSK failed.
  • Resolution: The return code from the GSK should give you some clues as to what went wrong.
  • Message: lib_stream: destroyStream: Failed in r_gsk_secure_soc_close: %s(gsk rc = %d)
  • Cause: Call to the GSK failed.
  • Resolution: The return code from the GSK should give you some clues as to what went wrong.
  • Message: mod_app_server_http: cb_get_headers: Skipping header name '%s'; This is a restricted WebSphere header
  • Cause: The request came in with one of the special headers that the plugin will normally add to the request and by default the plugin removes those from the request for security reasons.
  • Resolution: Could be a sign of a hacker trying to attach the system. If the user doesn't want the headers to be removed they can set the RemoveSpecialHeaders attribute for the ServerGroup(s) they don't want the removed from to false.
  • Message: iis_plugin: getServerVariable: Failed to extract server variable: %s
  • Cause: Failure to extract a variable needed by the plugin from ISAPI.
  • Resolution: This error would only be seen if the plugin was running on an unsupported version of IIS.
  • Message: iis_plugin: cb_get_headers: Skipping header name '%s'; This is a restricted WebSphere header
  • Cause: The request came in with one of the special headers that the plugin will normally add to the request and by default the plugin removes those from the request for security reasons.
  • Resolution: Could be a sign of a hacker trying to attach the system. If the user doesn't want the headers to be removed they can set the RemoveSpecialHeaders attribute for the ServerGroup(s) they don't want the removed from to false.
  • Message: iis_plugin: cb_get_headers: Unknown state parsing headers: |%s|
  • Cause: The state machine used to parse the headers entered an unknown state.
  • Resolution: Will only be seen if a bug is introduced into the plugin code.
  • Message: iis_plugin: cb_get_headers: Failed to parse and set headers: |%s|
  • Cause: The parsing of the request headers failed for some reason.
  • Resolution: Unlikely to see this message unless bad headers are being sent in the request.
  • Message: ns_plugin: cb_get_headers: No headers from the client
  • Cause: The client didn't send any headers with the request.
  • Resolution: Figure out why the client isn't sending any headers.
  • Message: ns_plugin: cb_get_headers: Skipping header name '%s'; This is a restricted WebSphere header
  • Cause: The request came in with one of the special headers that the plugin will normally add to the request and by default the plugin removes those from the request for security reasons.
  • Resolution: Could be a sign of a hacker trying to attach the system. If the user doesn't want the headers to be removed they can set the RemoveSpecialHeaders attribute for the ServerGroup(s) they don't want the removed from to false.
  • Message: ns_plugin: cb_get_headers: Unknown state parsing headers: |%s|
  • Cause: The state machine used to parse the headers entered an unknown state.
  • Resolution: Will only be seen if a bug is introduced into the plugin code.
  • Message: ns_plugin: cb_get_headers: Failed to parse and set headers: |%s|
  • Cause: The parsing of the request headers failed for some reason.
  • Resolution: Unlikely to see this message unless bad headers are being sent in the request.
  • Message: domino5_plugin: domino_parse_headers: Can't parse headers with length 0
  • Cause: The plugin failed to extract the headers from DSAPI.
  • Resolution: The client didn't send any request headers for the plugin to parse.
  • Message: domino5_plugin: domino_parse_headers: Skipping header name '%s'; This is a restricted WebSphere header
  • Cause: The request came in with one of the special headers that the plugin will normally add to the request and by default the plugin removes those from the request for security reasons.
  • Resolution: Could be a sign of a hacker trying to attach the system. If the user doesn't want the headers to be removed they can set the RemoveSpecialHeaders attribute for the ServerGroup(s) they don't want the removed from to false.
  • Message: domino5_plugin: domino_parse_headers: Unknown state parsing headers: |%s|
  • Cause: The state machine used to parse the headers entered an unknown state.
  • Resolution: Will only be seen if a bug is introduced into the plugin code.
 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Plug-in
Operating system(s): HP-UX
Software version: 4.0
Software edition:
Reference #: 1078803
IBM Group: Software Group
Modified date: Dec 12, 2002