WebSphere Process Server messages     Operating Systems: All supported

WSWS

WSWS7001I: The Axis2 service has been started.
Problem This informational message indicates that the WebSphere Application Server Axis2 service has been started.
User response No action is required.
WSWS7002E: The following exception occurred: {0}
Problem An error occurred while attempting to load application metadata.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7003E: The system encountered an internal error: {0}
Problem An error occurred while attempting to load application metadata.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7004E: The Performance Monitoring Infrastructure (PMI) services cannot be correctly loaded for the {0} application module.
Problem An internal system error occurred.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7005E: The Performance Monitoring Infrastructure (PMI) services cannot be correctly unloaded for the {0} application module.
Problem An internal system error occurred.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7006E: The {0} component could not be initialized because of the following error: {1}
Problem An internal system error occurred.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7007E: The {0} application module cannot be loaded correctly because of the following error: {1}
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.
WSWS7008E: The {0} application module cannot unload correctly because of the following error: {1}
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.
WSWS7009E: A configuration could not be correctly created for the {0} application module. The following error occurred: {1}
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.
WSWS7010E: The {0} application module contains an ibmservices.xml file. This file is not used to configure Web services.
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.
WSWS7011E: The configuration for the {0} application module cannot load correctly. The following error occurred: {1}
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.
WSWS7012E: The {0} component cannot be correctly started because of the following error: {1}
Problem An internal system error occurred.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7013E: The WebContainer service cannot be retrieved for the {0} component.
Problem An internal system error occurred.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7014E: The VariableMap service cannot be retrieved for the {0} component.
Problem An internal system error occured.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7015E: The Repository service cannot be retrieved for the {0} component.
Problem An internal system error occurred.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7016E: The Quality of Service (QoS) modules cannot load correctly on the server because of the following error: {0}
Problem An internal system error occurred.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7017E: The Quality of Service (QoS) modules did not load correctly on the client because of the following error: {0}
Problem An internal system error occurred.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7018E: The {0} Axis2 global configuration file cannot load correctly because of the following error: {1}
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.
WSWS7019E: The {0} module configuration file cannot load correctly.
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.
WSWS7020E: The configuration files for Quality of Service (QoS) modules could not be correctly located because of the following error: {0}
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.
WSWS7021E: A Quality of Service (QoS) module could not be correctly loaded because of the following error: {0}
Problem An internal system error has occurred.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7022E: The Quality of Service (QoS) configuration files for the application module cannot load correctly from the file list because of the following error: {0}
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.
WSWS7023W: The Quality of Service (QoS) module cannot load correctly because of a null URL.
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.
WSWS7024E: The id attribute of the plugin element for the ThreadContextMigrator extension does not have an assigned value.
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.
WSWS7025E: The {0} class did not implement the ThreadContextMigrator interface.
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.
WSWS7026E: The ''ThreadContextMigrator'' plugins cannot load correctly because of the following error: {0}
Problem An internal system error occurred.
User response Ensure that the WebServices Feature Pack and all of its components were successfully installed.
WSWS7027E: JAX-WS Service Descriptions could not be correctly built because of the following error: {0}
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.
WSWS7028E: The Axis Object Model (OM) structure could not be built from the web.xml file because of the following error: {0}.
Problem The module''s web.xml file may contain syntax errors.
User response Ensure that the module''s web.xml is correct.
WSWS7029E: A URL could not be established for the Web service because of the following error: {0}
Problem An internal system error occurred.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7030E: The {0} AxisService does not contain an implementation class name.
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.
WSWS7031E: The {0} application module did not process correctly because of the following error: {1}
Problem An internal system error occured.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7032E: The {0} servlet contains more than one servlet mapping, which is a violation of the JSR 109 specification.
Problem A single servlet has defined more than one mapping entry.
User response Ensure that every servlet has only one servlet mapping defined.
WSWS7033E: The {0} AxisService does not contain {1} parameter.
Problem A required parameter was not available on the AxisService.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7034E: The Performance Monitoring Infrastructure (PMI) Handler cannot be invoked because of the following error: {0}
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.
WSWS7035E: The {0} metadata file could not be found.
Problem A WSDL or XSD file could not be located.
User response Ensure that the file exists.
WSWS7036E: The {0} Web Services Description Language (WSDL) file cannot be located because of the following error: {1}
Problem An internal system error occurred.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7037I: The {0} URL pattern was configured for the {1} servlet located in the {2} web module.
Problem This message is for informational purposes only.
User response No action is required.
WSWS7038E: The Axis Configuration for the {0} application module is null.
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.
WSWS7039E: Policy sets could not be loaded correctly into the Axis Configuration for service {0} because of the following error: {1}
Problem An internal system error occurred.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7040E: In the {1} class, the {0} service name specified by the @WebServiceClient annotation cannot be found in the {2} Web Service Description Language (WSDL) file.
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.
WSWS7041E: The @WebServiceClient annotation of the {0} class contains an incorrect value and the following error occurred: {1}
Problem The class may contain annotations that are not valid.
User response Ensure all annotations are defined correctly.
WSWS7042E: The {0} class was declared as an implementation of the Axis2ServiceConfigPlugin interface, but the class does not implement the interface.
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.
WSWS7043E: The ''Axis2ServiceConfigPlugin'' plugins cannot load correctly because of the following error: {0}
Problem An internal system error occurred.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7044E: The Axis2 runtime objects cannot be configured using the Axis2ServiceConfigPlugin implementation {0}: {1}
Problem An internal system error occurred.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7045E: The ConfigurationContext for the {0} application module cannot be created correctly because of the following error: {1}
Problem An internal system error occurred.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7046E: The {0} class cannot load correctly because of the following error: {1}
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.
WSWS7047E: The URL for the {0} super class cannot load correctly because of the following error: {1}
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.
WSWS7048E: The {0} cache file cannot be created correctly because of the following error: {1}
Problem A Web services cache could not be created. This will not affect the availability of the application.
User response No action is required.
WSWS7050E: The {0} cache file cannot be loaded correctly because of the following error: {1}
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.
WSWS7051E: The {0} cache file cannot be saved correctly because of the following error: {1}
Problem The cache file will not be written. This will not affect the availability of the application.
User response No action is required.
WSWS7052E: The {0} generated WSDL file could not be read correctly because of the following error: {1}
Problem An internal system error occurred.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7053E: A generated schema file could not be read correctly because of the following error: {0}
Problem An internal system error occurred.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7054E: The Web Services Description Language (WSDL) file could not be generated for the {0} Web service implementation class because of the following error: {1}
Problem An internal system error occurred.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7055E: The {0} Web Services Description Language (WSDL) file specified by annotations in class {1} cannot be loaded correctly due to the following error: {2}
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.
WSWS7056E: The {0} schema file cannot be displayed because of the following error: {1}
Problem An internal system error occurred.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7057E: The client ConfigurationContext could not be saved correctly because of the following error: {0}
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.
WSWS7058E: A JAXBContext could not be created correctly because of the following error: {0}
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.
WSWS7059E: The {0} class cannot load correctly when creating a JAXBContext.
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.
WSWS7060E: A ClassLoader could not be found to create a JAXBContext for the package name: {0}
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.
WSWS7061E: The {0} Web service client could not be processed.
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.
WSWS7062E: The {0} Web Services Description Language (WSDL) file referenced by the @WebServiceClient annotation in the {1} class could not be loaded.
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.
WSWS7063E: An error occurred when determining if an unknown endpoint is processable using the UnknownEPRResolverPlugin implementation {0}: {1}
Problem An internal system error occurred.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7064E: The configuration context for an unknown endpoint cannot be retrieved using the UnknownEPRConfigCtxtLoaderPlugin implementation {0}: {1}
Problem An internal system error occurred.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7065E: The {0} Web service implementation class refers to the absolute Web Services Description Language (WSDL)location {1} using annotations.
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.
WSWS7066E: The {0} Web Services Description Language (WSDL) file cannot be displayed due to the following error: {1}
Problem An internal system error occurred.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7067E: The {0} Servlet cannot specify the * character as a URL pattern.
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.
WSWS7068I: The thread {0} is waiting for notification.
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.
WSWS7069I: Current pool size: {0}. Connections-in-use size: {1}. Configured pool size: {2}
Problem This informational message describes the current condition of the outbound HTTP connection pool.
User response No user action is required.
WSWS7070I: A cookie was received for the {0} HTTP header in the response from the connection to: {1}
Problem This message is for informational purposes only.
User response No action is required.
WSWS7071I: Loading ssl.client.props {0}
Problem This message is for informational purposes only.
User response No action is required.
WSWS7072I: Found programmatically set SSL thread properties = {0} with listener = {1} registered.
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.
WSWS7073I: Found SSL configuration alias = {0} and SSL certificate alias = {1} from the message context.
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.
WSWS7074W: The SSL configuration could not be correctly resolved. The system will explicitly request the JSSE properties from the security''s JSSEHelper.
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.
WSWS7075I: The JSSEHelper from security returns the {0} SSL properties with listener = {1} registered.
Problem Received SSL properties from the security component. The same properties are registered with the event listener.
User response No action is required.
WSWS7076I: The {0} listening host and port {1} have been associated.
Problem The listening host and port have been configured to be associated with each other.
User response No action is required.
WSWS7077I: The {0} Endpoint Reference (EPR) has been established.
Problem This message is for informational purposes only.
User response No action is required.
WSWS7078I: Virtual host returned by {0}: {1}
Problem This message is for informational purposes only.
User response No action is required.
WSWS7079I: The Dynamic Work Load Management Client is enabled: {0}
Problem This message is for informational purposes only.
User response No action is required.
WSWS7080E: The following schema for HTTP is not supported: {0}
Problem An unsupported schema for using HTTP transport was found.
User response Verify the target endpoint address is valid.
WSWS7081I: The {1} host, {2} port, and {3} URI path was mapped to the {0} cluster.
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.
WSWS7082I: Local cell name: {0}. Mapped cell name from DWLM client: {1}.
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.
WSWS7083W: The Web services engine will attempt to query again from the Unified Clustering Framework, due to the following error: {0}
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.
WSWS7084W: A second query from the Unified Clustering Framework has failed. No ChannelTarget object is returned from the Unified Clustering Framework.
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.
WSWS7085I: The {0} ChannelFramework EndPoint object is mapped, using the Identity object of {1}
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.
WSWS7086I: The {0} outbound connection object has expired. The elapsed time from the last access to the object is {1} millieseconds.
Problem This message is for informational purposes only.
User response No action is required.
WSWS7087E: An integrity problem occurred with the connection pool.
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.
WSWS7088I: The {0} current thread is going to wait {1} milliseconds for notification.
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.
WSWS7089I: The connection wait has timed out.
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.
WSWS7090I: The channel buffer size is {0}.
Problem This message is for informational purposes only.
User response No action is required.
WSWS7091E: The following errors occurred on the channel framework service: {0}
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.
WSWS7092E: The HTTP(S) proxy information for the proxy connection was not received.
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.
WSWS7093W: The HTTP response redirected the target resource to a new location: {0}
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.
WSWS7094E: An incorrect {0} HTTP host value was specified within the URL {1}
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.
WSWS7095E: An incorrect {0} HTTP port value was specified within the URL {1}
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.
WSWS7096E: An unsupported HTTP version is found: {0}
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.
WSWS7097E: The {0} parameter can have values of only HTTP/1.0 or HTTP/1.1
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.
WSWS7098E: Both the TransportOut and property MessageContext.TRANSPORT_OUT values are null.
Problem This is an internal error.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7099E: The attachment was not correctly deleted due to the following error: {0}
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.
WSWS7100E: {0} has not been set.
Problem This is an internal error.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7101W: A connection is attempted with an outbound connection object that is already marked to be closed: {0}
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.
WSWS7102I: The {0} MessageContext object could not be found.
Problem This message is for informational purposes only.
User response No action is required.
WSWS7103I: The required asynchronous response servlet is not available.
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.
WSWS7104I: The asynchronous response servlet was not correctly initialized due to the following error: {0}
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.
WSWS7105I: The context ID {0} was received from an unknown asynchronous response.
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.
WSWS7106I: The port {0} is not valid.
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.
WSWS7107I: The host address {0} has not been established yet. An endpoint reference (EPR)cannot be generated.
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.
WSWS7108W: The {0} attribute is not valid.
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.
WSWS7109E: The {0} unmarshaled object is not a policy object.
Problem This is an internal error.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7110E: The policy file was not successfully validated due to the following error: {0}
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.
WSWS7111E: The policy file was not marshaled correctly due to the following error: {0}
Problem This is an internal error.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7112E: The {0} element received an object that is not a string object.
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.
WSWS7113E: A non {0} object was received for the {1} element.
Problem This is an internal error.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7114E: An Axis2 MessageContext object was not found in the AsyncResponseContext object.
Problem This is an internal error.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7115E: The required AsyncResponseServlet is not available.
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.
WSWS7116E: An exception occurred in the asynchronous getRequestBodyBuffers(): {0}
Problem This is an internal error.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7117E: An exception occurred in the synchronous getRequestBodyBuffers(): {0}
Problem This is an internal error.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7118E: An exception occurred in the discriminate method: {0}
Problem This is an internal error.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7119E: An exception occurred during an asynchronous read operation: {0}
Problem This is an internal error.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7120E: An exception occurred when performing asynchronous operations: {0}
Problem This is an internal error.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7121E: No HTTP status has been received for the current HTTP response.
Problem No HTTP status information is available to determine the HTTP response.
User response Make sure the target HTTP server is up.
WSWS7122E: This request is not a one-way request and should have yielded a response from {0}.
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.
WSWS7123E: No HTTPConnection object was returned from the outbound connection pool.
Problem This is an internal error.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7124E: The transport header key is not valid.
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.
WSWS7125E: The transport header value with key {0} is not valid.
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.
WSWS7126E: The server module metadata in the Axis servlet for the {0} module could not be retrieved.
Problem This is an internal error.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7127E: The configuration context in the Axis servlet for the {0} module could not be retrieved.
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.
WSWS7128E: The acknowledgement was not correctly sent due to the following error: {0}.
Problem This is an internal error.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7129E: The Secure Sockets Layer (SSL) client configuration file, ssl.client.props,is not specified due to the following error: {0}
Problem This is an internal error.
User response Consult the logs in your <profile_home>/logs directory for more information.
WSWS7130E: No Secure Sockets Layer (SSL) configuration is available for the {0} endpoint.
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.
WSWS7131E: The ''ApplicationContextMigrator'' plugins cannot load correctly because of the following error: {0}
Problem An internal system error occurred.
User response Ensure that the WebServices Feature Pack and all of its components were successfully installed.
WSWS7132E: The id attribute of the plugin element for the ApplicationContextMigrator extension does not have an assigned value.
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.
WSWS7133E: The {0} class did not implement the ApplicationContextMigrator interface.
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.
WSWS7134E: The ibmasyncrsp.ear system application could not be installed due to the following error: {0}.
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.
WSWS7135E: The following error occurred while attempting to retrieve the com.ibm.websphere.webservices.Constants.RESPONSE_TRANSPORT_PROPERTIES property from the response: {0}
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.
Reference topic    

Terms of Use | Feedback

Last updated: Jun 13, 2009 1:00:35 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.websvcs.resources.websvcsMessages.html

© Copyright IBM Corporation 2006, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)