Problem | This informational message indicates that the WebSphere Application Server Axis2 service has been started. |
User response | No action is required. |
Problem | An error occurred while attempting to load application metadata. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | An error occurred while attempting to load application metadata. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | An internal system error occurred. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | An internal system error occurred. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | An internal system error occurred. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | The application module could not be successfully loaded due to an unexpected error. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | The application module could not unload successfully due to unexpected errors. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | A configuration could not be created for the application. Web services in the application will not be initialized. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | The ibmservices.xml file is not used to identify Web services in a module. |
User response | An application defined as a Web service must be annotated with the @WebService or @WebServiceProvider annotations. |
Problem | The configuration for the application module could not load correctly. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | An internal system error occurred. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | An internal system error occurred. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | An internal system error occured. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | An internal system error occurred. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | An internal system error occurred. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | An internal system error occurred. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | An error occured while trying to load the system configuration for a JAX-WS Web service application. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | The configuration for a Quality of Service (QoS) module could not be loaded from the specified file. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | The Quality of Service (QoS) modules will not be engaged due to the error. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | An internal system error has occurred. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | An internal system error occured when attempting to load Quality of Service (QoS) modules. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | The configuration file for a Quality of Service (QoS) cannot be located as a resource. |
User response | Ensure that the WebServices Feature Pack and all of its components were successfully installed. |
Problem | The id attribute of the plugin element for ThreadContextMigrator extensions is a required value. |
User response | Ensure that the WebServices Feature Pack and all of its components were successfully installed. |
Problem | The class was determined to be a ThreadContextMigrator implementation by the runtime extension mechanism, but it does not implement the ThreadContextMigrator interface. |
User response | Ensure that the WebServices Feature Pack and all of its components were successfully installed. |
Problem | An internal system error occurred. |
User response | Ensure that the WebServices Feature Pack and all of its components were successfully installed. |
Problem | An error occurred trying to load Web service related metadata. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | The module''s web.xml file may contain syntax errors. |
User response | Ensure that the module''s web.xml is correct. |
Problem | An internal system error occurred. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | The servlet name does not match the Web service''s implementation class name. |
User response | If the optional servlet and its mapping are defined in the module''s web.xml, the servlet name must be the same as the Web service''s implementation class name. |
Problem | An internal system error occured. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | A single servlet has defined more than one mapping entry. |
User response | Ensure that every servlet has only one servlet mapping defined. |
Problem | A required parameter was not available on the AxisService. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | Performance metrics for the application module will not be available. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | A WSDL or XSD file could not be located. |
User response | Ensure that the file exists. |
Problem | An internal system error occurred. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | This message is for informational purposes only. |
User response | No action is required. |
Problem | The application module configuration information could not be correctly loaded. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | An internal system error occurred. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | @WebServiceClient annotation metadata did not correspond to information in the WSDL document. |
User response | Ensure that the name attribute maps to a valid service within the WSDL file. Also ensure that the targetNamespace attribute and the wsdlLocation attribute are correct. |
Problem | The class may contain annotations that are not valid. |
User response | Ensure all annotations are defined correctly. |
Problem | An internally registered class does not implement the correct interface. |
User response | Ensure that the WebServices Feature Pack and all of its components were successfully installed. |
Problem | An internal system error occurred. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | An internal system error occurred. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | An internal system error occurred. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | A Web service related class file could not be loaded from the module. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | A Web service related class could not be loaded or inspected for metadata. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | A Web services cache could not be created. This will not affect the availability of the application. |
User response | No action is required. |
Problem | The Web services cache could not be loaded. The metadata will be built from other sources, and this will not affect the availability of the application. |
User response | No action is required. |
Problem | The cache file will not be written. This will not affect the availability of the application. |
User response | No action is required. |
Problem | An internal system error occurred. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | An internal system error occurred. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | An internal system error occurred. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | The Web Services Description Language (WSDL) path could not be resolved or found. |
User response | Ensure that the WSDL file exists and that the path is correct and that the annotation''s wsdlLocation attribute is correct. |
Problem | An internal system error occurred. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | This may cause unpredictable results when certain Quality of Service (QoS) policies are applied to this client. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | The message will not be correctly processed because of the incorrect JAXBContext. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | The message may not be correctly processed because of an incomplete JAXBContext. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | The message will not be processed because of an incorrect JAXBContext. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | A class with an @WebServiceClient annotation could not be processed and certain administrative features may not be available for this client. |
User response | No action is required. |
Problem | A class with an @WebServiceClient annotation could not be processed and certain administrative features may not be available for this client. |
User response | Ensure that the wsdlLocation attribute in the @WebServiceClient annotation contains a correct file path. |
Problem | An internal system error occurred. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | An internal system error occurred. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | Absolute WSDL references are not allowed in @WebService or @WebServiceProvider annotations according to the JAX-WS specification. |
User response | Either remove the wsdlLocation attribute or modify the value so it refers to a relative location. |
Problem | An internal system error occurred. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | A servlet cannot be mapped to a non-exact URL pattern. |
User response | Ensure that the URL pattern for the servlet is an exact pattern. |
Problem | The connection pool is full and the current thread is waiting for openings. The runtime might wait for an extended time if the network is busy. |
User response | If the wait is too long, consider specifying a connection wait timeout, increasing the number of maximum connections, or both. Check for network problems. |
Problem | This informational message describes the current condition of the outbound HTTP connection pool. |
User response | No user action is required. |
Problem | This message is for informational purposes only. |
User response | No action is required. |
Problem | This message is for informational purposes only. |
User response | No action is required. |
Problem | The runtime has found SSL properties programmatically set on the current thread. The same properties are registered with the event listener. SSL properties that are set programmatically always have the highest precedence. |
User response | If this is not the intended result, update the application to not programmatically set the properties prior to invocation. |
Problem | Based on the JAX-RPC model, the SSL configuration alias or SSL certificate alias can be specified and might have been found from the message''s context. The information is used for the SSL connection of the current invocation. However, there may not be a value for each alias if the alias has never been specified. |
User response | If this is not the intended result, update the application to not set the properties prior to invocation. See the Information Center for more information. |
Problem | The application server SSL runtime failed to resolve for an effective SSL configuration. The system will attempt to default to the JSSE system properties. |
User response | Make sure that the SSL configuration is properly set for this invocation. See the Information Center regarding the precedence rules for securing communications using SSL. |
Problem | Received SSL properties from the security component. The same properties are registered with the event listener. |
User response | No action is required. |
Problem | The listening host and port have been configured to be associated with each other. |
User response | No action is required. |
Problem | This message is for informational purposes only. |
User response | No action is required. |
Problem | This message is for informational purposes only. |
User response | No action is required. |
Problem | This message is for informational purposes only. |
User response | No action is required. |
Problem | An unsupported schema for using HTTP transport was found. |
User response | Verify the target endpoint address is valid. |
Problem | The listed data for host, port, and URI path was used to map to a valid cluster name. |
User response | No action is required. |
Problem | This message provides information about the local and mapped cell names. The mapped cell name can be from a remote cluster. |
User response | No action is required. |
Problem | This exception might occur because of a timing problem caused by the asynchronous operation performed by the Unified Clustering Framework (UCF). The web services engine will attempt to query from the UCF again. |
User response | No action is required. |
Problem | If the second query fails, the engine will proceed to next option using default channels. |
User response | If Unified Clustering is needed, this is an error. See the trace.log file located in the <profile_home>/logs directory for clustering errors. |
Problem | The identify object was used to map a channelframework endpoint object that can be used later to create an in-process connection. |
User response | No action is required. |
Problem | This message is for informational purposes only. |
User response | No action is required. |
Problem | The number of connections being used for the current connection group is more than the allocated maximum number of connections available for the connection group. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | The connection pool is full and the current thread is waiting for openings for the specified amount of time. If no opening becomes available, a "Connection timed out" exception might result. |
User response | If the exception occurs, consider increasing the maximum connections value for the connection pool, and increasing the connection wait timeout value to wait for openings in the pool. Check for network problems. |
Problem | A WebServicesFault exception has occurred. The connection wait for an opening in the connection pool has been reached and no connection object is available. |
User response | Consider increasing the connection wait timeout and increasing the maximum connections value. Check for network problems. |
Problem | This message is for informational purposes only. |
User response | No action is required. |
Problem | The channel framework service encountered errors. |
User response | See the logs in the <profile_home>/logs directory for errors reported by the channel framework service. |
Problem | The system runtime was unable to obtain the HTTP proxy information to process the proxy connection. |
User response | Make sure the HTTP or HTTPS proxy information is configured correctly. See the Information Center to learn how to configure the HTTP or HTTP proxy information. |
Problem | An HTTP response was received that indicates a new location for the target resource. |
User response | See the Information Center to learn about how to accept the automatic redirection for a target resource to a new location. |
Problem | An incorrect HTTP host value was specified within the URL. This might be an internal error. |
User response | Make sure that the endpoint location URL contains a valid host name. |
Problem | An incorrect HTTP port value was specified within the URL. This might be an internal error. |
User response | Mkae sure that the endpoint location URL contains a valid port number. |
Problem | An unsupported HTTP version is detected. This is an internal error. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | The default HTTP protocol defined in the Axis2 configuration xml is invalid. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | This is an internal error. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | The local copy of the attachment sent with the message could not be deleted. |
User response | Manually delete the local copy of the attachment from a temporary directory if the file is no longer needed. |
Problem | This is an internal error. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | Access to a closed connection is attempted. This might be an internal error. |
User response | Consult the logs in your <profile_home>/logs directory for connection exceptions. |
Problem | This message is for informational purposes only. |
User response | No action is required. |
Problem | The servlet required for asynchronous messaging is not available. |
User response | Make sure that the Feature Pack for Web Services was installed correctly and that your profile has been augmented correctly. |
Problem | The servlet required for asynchronous messaging could not be initialized. |
User response | Make sure that the Feature Pack for Web Services was installed correctly and that your profile has been augmented correctly. |
Problem | A response message was received that was not identifiable by the servlet for processing. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | The port to be initialized is not valid for use. |
User response | Check the server''s channel configuration to make sure a valid port is being used. |
Problem | The host''s physical IP address has not been created yet. The EPR cannot be generated until the IP address is set. |
User response | Check the logs in your <profile_home>/logs directory for more information. |
Problem | This is an internal error. This is an invalid attribute that is not part of the policy set. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | This is an internal error. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | This is an internal error. The policy file contained invalid attributes. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | This is an internal error. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | The value provided for the policy set bindings must be string values. |
User response | Ensure that values set on the policy set bindings are valid. |
Problem | This is an internal error. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | This is an internal error. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | The asynchronous servlet is not available to accept asynchronous responses. |
User response | Consult the logs in your <profile_home>/logs directory for more information and make sure that your profile has been successfully augmented with the Feature Pack for Web Services profile template. |
Problem | This is an internal error. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | This is an internal error. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | This is an internal error. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | This is an internal error. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | This is an internal error. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | No HTTP status information is available to determine the HTTP response. |
User response | Make sure the target HTTP server is up. |
Problem | The request sent was a two way invocation and should have gotten a response. |
User response | Consult the logs in your <profile_home>/logs directory for more information and make sure the required service is available. |
Problem | This is an internal error. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | The transport header key does not have a value or has an invalid value. |
User response | Make sure any custom transport headers defined are valid. Consult the logs in your <profile_home>/logs directory for more information. |
Problem | The transport header value does not have a value or has an invalid value. |
User response | Make sure any custom transport headers defined are valid. Consult the logs in your <profile_home>/logs directory for more information. |
Problem | This is an internal error. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | The required configuration data could not be found during servlet initialization. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | This is an internal error. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | This is an internal error. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |
Problem | The system runtime was unable to resolve an effective Secure Sockets Layer (SSL) configuration with the specified endpoint. |
User response | Make sure SSL configuration is correctly set for this endpoint. See the Information Center regarding the rules for securing communications using SSL. |
Problem | An internal system error occurred. |
User response | Ensure that the WebServices Feature Pack and all of its components were successfully installed. |
Problem | The id attribute of the plugin element for ApplicationContextMigrator extensions is a required value. |
User response | Ensure that the WebServices Feature Pack and all of its components were successfully installed. |
Problem | The class was determined to be a ApplicationContextMigrator implementation by the runtime extension mechanism, but it does not implement the ApplicationContextMigrator interface. |
User response | Ensure that the WebServices Feature Pack and all of its components were successfully installed. |
Problem | The asynchronous response servlet could not be installed to the newly created Web Services Feature Pack server. The new server will not be able to send or receive asynchronous messages. |
User response | Ensure that the WebServices Feature Pack and all of its components were successfully installed. |
Problem | The property indicated by the RESPONSE_TRANSPORT_PROPERTIES constant will not be available for the client application. |
User response | Consult the logs in your <profile_home>/logs directory for more information. |