Express (Distributed operating systems), v8.0 > Reference > Messages
WSWS
WSWS7001I: The Axis2 service has been started.
Explanation This informational message indicates that the Application Server Axis2 service has been started. Action No action is required.
WSWS7002E: The following exception occurred: {0}
Explanation An error occurred while attempting to load application metadata. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7003E: The system encountered an internal error: {0}
Explanation An error occurred while attempting to load application metadata. Action 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.
Explanation An internal system error occurred. Action 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.
Explanation An internal system error occurred. Action 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}
Explanation An internal system error occurred. Action 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}
Explanation The application module could not be successfully loaded due to an unexpected error. Action 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}
Explanation The application module could not unload successfully due to unexpected errors. Action 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}
Explanation A configuration could not be created for the application. Web services in the application will not be initialized. Action 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.
Explanation The ibmservices.xml file is not used to identify Web services in a module. Action 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}
Explanation The configuration for the application module could not load correctly. Action 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}
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7013E: The WebContainer service cannot be retrieved for the {0} component.
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7014E: The VariableMap service cannot be retrieved for the {0} component.
Explanation An internal system error occured. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7015E: The Repository service cannot be retrieved for the {0} component.
Explanation An internal system error occurred. Action 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}
Explanation An internal system error occurred. Action 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}
Explanation An internal system error occurred. Action 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}
Explanation An error occured while trying to load the system configuration for a JAX-WS Web service application. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7019E: The {0} module configuration file cannot load correctly.
Explanation The configuration for a Quality of Service (QoS) module could not be loaded from the specified file. Action 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}
Explanation The Quality of Service (QoS) modules will not be engaged due to the error. Action 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}
Explanation An internal system error has occurred. Action 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}
Explanation An internal system error occured when attempting to load Quality of Service (QoS) modules. Action 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.
Explanation The configuration file for a Quality of Service (QoS) cannot be located as a resource. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7024E: The id attribute of the plug-in element for the ThreadContextMigrator extension does not have an assigned value.
Explanation The id attribute of the plug-in element for ThreadContextMigrator extensions is a required value. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7025E: The {0} class did not implement the ThreadContextMigrator interface.
Explanation The class was determined to be a ThreadContextMigrator implementation by the runtime extension mechanism, but it does not implement the ThreadContextMigrator interface. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7026E: The ''ThreadContextMigrator'' plug-ins cannot load correctly because of the following error: {0}
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7027E: JAX-WS Service Descriptions could not be correctly built because of the following error: {0}
Explanation An error occurred trying to load Web service related metadata. Action 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}.
Explanation The module's web.xml file may contain syntax errors. Action 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}
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7030E: The {0} AxisService does not contain an implementation class name.
Explanation The servlet name does not match the Web service's implementation class name. Action 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}
Explanation An internal system error occured. Action 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.
Explanation A single servlet has defined more than one mapping entry. Action Ensure that every servlet has only one servlet mapping defined.
WSWS7033E: The {0} AxisService does not contain {1} parameter.
Explanation A required parameter was not available on the AxisService. Action 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}
Explanation Performance metrics for the application module will not be available. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7035E: The {0} metadata file could not be found.
Explanation A WSDL or XSD file could not be located. Action Ensure that the file exists.
WSWS7036E: The {0} WSDL file cannot be located because of the following error: {1}
Explanation An internal system error occurred. Action 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.
Explanation This message is for informational purposes only. Action No action is required.
WSWS7038E: The Axis Configuration for the {0} application module is null.
Explanation The application module configuration information could not be correctly loaded. Action 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}
Explanation An internal system error occurred. Action 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.
Explanation @WebServiceClient annotation metadata did not correspond to information in the WSDL document. Action 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}
Explanation The class may contain annotations that are not valid. Action 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.
Explanation An internally registered class does not implement the correct interface. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7043E: The ''Axis2ServiceConfigPlugin'' plug-ins cannot load correctly because of the following error: {0}
Explanation An internal system error occurred. Action 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}
Explanation An internal system error occurred. Action 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}
Explanation An internal system error occurred. Action 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}
Explanation A Web service related class file could not be loaded from the module. Action 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}
Explanation A Web service related class could not be loaded or inspected for metadata. Action 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}
Explanation A Web services cache could not be created. This will not affect the availability of the application. Action No action is required.
WSWS7050E: The {0} cache file cannot be loaded correctly because of the following error: {1}
Explanation 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. Action No action is required.
WSWS7051E: The {0} cache file cannot be saved correctly because of the following error: {1}
Explanation The cache file will not be written. This will not affect the availability of the application. Action No action is required.
WSWS7052E: The {0} generated WSDL file could not be read correctly because of the following error: {1}
Explanation An internal system error occurred. Action 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}
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7054E: The WSDL file could not be generated for the {0} Web service implementation class because of the following error: {1}
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7055E: The {0} WSDL file specified by annotations in class {1} cannot be loaded correctly due to the following error: {2}
Explanation The WSDL path could not be resolved or found. Action 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}
Explanation An internal system error occurred. Action 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}
Explanation This may cause unpredictable results when certain Quality of Service (QoS) policies are applied to this client. Action 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}
Explanation The message will not be correctly processed because of the incorrect JAXBContext. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7059E: The {0} class cannot load correctly when creating a JAXBContext.
Explanation The message may not be correctly processed because of an incomplete JAXBContext. Action 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}
Explanation The message will not be processed because of an incorrect JAXBContext. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7061E: The {0} Web service client could not be processed.
Explanation A class with an @WebServiceClient annotation could not be processed and certain administrative features may not be available for this client. Action No action is required.
WSWS7062E: The {0} WSDL file referenced by the @WebServiceClient annotation in the {1} class could not be loaded.
Explanation A class with an @WebServiceClient annotation could not be processed and certain administrative features may not be available for this client. Action 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}
Explanation An internal system error occurred. Action 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}
Explanation An internal system error occurred. Action 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.
Explanation Absolute WSDL references are not allowed in @WebService or @WebServiceProvider annotations according to the JAX-WS specification. Action Either remove the wsdlLocation attribute or modify the value so it refers to a relative location.
WSWS7066E: The {0} WSDL file cannot be displayed due to the following error: {1}
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7067E: The {0} Servlet cannot specify the * character as a URL pattern.
Explanation A servlet cannot be mapped to a non-exact URL pattern. Action Ensure that the URL pattern for the servlet is an exact pattern.
WSWS7068I: The thread {0} is waiting for notification.
Explanation 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. Action 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}
Explanation This informational message describes the current condition of the outbound HTTP connection pool. Action No user action is required.
WSWS7070I: A cookie was received for the {0} HTTP header in the response from the connection to: {1}
Explanation This message is for informational purposes only. Action No action is required.
WSWS7071I: Loading ssl.client.props {0}
Explanation This message is for informational purposes only. Action No action is required.
WSWS7072I: Found programmatically set SSL thread properties = {0} with listener = {1} registered.
Explanation 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. Action 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.
Explanation 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. Action 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.
Explanation The application server SSL runtime failed to resolve for an effective SSL configuration. The system will attempt to default to the JSSE system properties. Action 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.
Explanation Received SSL properties from the security component. The same properties are registered with the event listener. Action No action is required.
WSWS7076I: The {0} listening host and port {1} have been associated.
Explanation The listening host and port have been configured to be associated with each other. Action No action is required.
WSWS7077I: The {0} Endpoint Reference (EPR) has been established.
Explanation This message is for informational purposes only. Action No action is required.
WSWS7078I: Virtual host returned by {0}: {1}
Explanation This message is for informational purposes only. Action No action is required.
WSWS7079I: The Dynamic Work Load Management Client is enabled: {0}
Explanation This message is for informational purposes only. Action No action is required.
WSWS7080E: The following schema for HTTP is not supported: {0}
Explanation An unsupported schema for using HTTP transport was found. Action Verify the target endpoint address is valid.
WSWS7081I: The {1} host, {2} port, and {3} URI path was mapped to the {0} cluster.
Explanation The listed data for host, port, and URI path was used to map to a valid cluster name. Action No action is required.
WSWS7082I: Local cell name: {0}. Mapped cell name from DWLM client: {1}.
Explanation This message provides information about the local and mapped cell names. The mapped cell name can be from a remote cluster. Action 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}
Explanation 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. Action 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.
Explanation If the second query fails, the engine will proceed to next option using default channels. Action 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}
Explanation The identify object was used to map a channelframework endpoint object that can be used later to create an in-process connection. Action 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.
Explanation This message is for informational purposes only. Action No action is required.
WSWS7087E: An integrity problem occurred with the connection pool.
Explanation 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. Action 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.
Explanation 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. Action 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.
Explanation A AxisFault exception has occurred. The connection wait for an opening in the connection pool has been reached and no connection object is available. Action Consider increasing the connection wait timeout and increasing the maximum connections value. Check for network problems.
WSWS7090I: The channel buffer size is {0}.
Explanation This message is for informational purposes only. Action No action is required.
WSWS7091E: The following errors occurred on the channel framework service: {0}
Explanation The channel framework service encountered errors. Action 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.
Explanation The system runtime was unable to obtain the HTTP proxy information to process the proxy connection. Action 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}
Explanation An HTTP response was received that indicates a new location for the target resource. Action 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}
Explanation An incorrect HTTP host value was specified within the URL. This might be an internal error. Action 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}
Explanation An incorrect HTTP port value was specified within the URL. This might be an internal error. Action Make sure that the endpoint location URL contains a valid port number.
WSWS7096E: An unsupported HTTP version is found: {0}
Explanation An unsupported HTTP version is detected. This is an internal error. Action 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
Explanation The default HTTP protocol defined in the Axis2 configuration xml is not valid. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7098E: Both the TransportOut and property MessageContext.TRANSPORT_OUT values are null.
Explanation This is an internal error. Action 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}
Explanation The local copy of the attachment sent with the message could not be deleted. Action 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.
Explanation This is an internal error. Action 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}
Explanation Access to a closed connection is attempted. This might be an internal error. Action Consult the logs in your <profile_home>/logs directory for connection exceptions.
WSWS7102I: The {0} MessageContext object could not be found.
Explanation This message is for informational purposes only. Action No action is required.
WSWS7103I: The required asynchronous response servlet is not available.
Explanation The servlet required for asynchronous messaging is not available. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7104I: The asynchronous response servlet was not correctly initialized due to the following error: {0}
Explanation The servlet required for asynchronous messaging could not be initialized. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7105I: The context ID {0} was received from an unknown asynchronous response.
Explanation A response message was received that was not identifiable by the servlet for processing. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7106I: The port {0} is not valid.
Explanation The port to be initialized is not valid for use. Action 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.
Explanation The host's physical IP address has not been created yet. The EPR cannot be generated until the IP address is set. Action Check the logs in your <profile_home>/logs directory for more information.
WSWS7108W: The {0} attribute is not valid.
Explanation This is an internal error. This is not a valid attribute and is not part of the policy set. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7109E: The {0} unmarshaled object is not a policy object.
Explanation This is an internal error. Action 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}
Explanation This is an internal error. The policy file contained iattributes that were not valid. Action 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}
Explanation This is an internal error. Action 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.
Explanation The value provided for the policy set bindings must be string values. Action Ensure that values set on the policy set bindings are valid.
WSWS7113E: A non {0} object was received for the {1} element.
Explanation This is an internal error. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7114E: An Axis2 MessageContext object was not found in the AsyncResponseContext object.
Explanation This is an internal error. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7115E: The required AsyncResponseServlet is not available.
Explanation The asynchronous servlet is not available to accept asynchronous responses. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7116E: An exception occurred in the asynchronous getRequestBodyBuffers(): {0}
Explanation This is an internal error. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7117E: An exception occurred in the synchronous getRequestBodyBuffers(): {0}
Explanation This is an internal error. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7118E: An exception occurred in the discriminate method: {0}
Explanation This is an internal error. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7119E: An exception occurred during an asynchronous read operation: {0}
Explanation This is an internal error. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7120E: An exception occurred when performing asynchronous operations: {0}
Explanation This is an internal error. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7121E: No HTTP status has been received for the current HTTP response.
Explanation No HTTP status information is available to determine the HTTP response. Action 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}.
Explanation The request sent was a two way invocation and should have gotten a response. Action 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.
Explanation This is an internal error. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7124E: The transport header key is not valid.
Explanation The transport header key does not have a value or has a value that is not valid. Action 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.
Explanation The transport header value does not have a value or has a value that is not valid. Action 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.
Explanation This is an internal error. Action 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.
Explanation The required configuration data could not be found during servlet initialization. Action 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}.
Explanation This is an internal error. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7129E: The SSL client configuration file, ssl.client.props,is not specified due to the following error: {0}
Explanation This is an internal error. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7130E: No SSL configuration is available for the {0} endpoint.
Explanation The system runtime was unable to resolve an effective SSL configuration with the specified endpoint. Action 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'' plug-ins cannot load correctly because of the following error: {0}
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7132E: The id attribute of the plug-in element for the ApplicationContextMigrator extension does not have an assigned value.
Explanation The id attribute of the plug-in element for ApplicationContextMigrator extensions is a required value. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7133E: The {0} class did not implement the ApplicationContextMigrator interface.
Explanation The class was determined to be a ApplicationContextMigrator implementation by the runtime extension mechanism, but it does not implement the ApplicationContextMigrator interface. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7134E: The ibmasyncrsp.ear system application could not be installed due to the following error: {0}.
Explanation The asynchronous response servlet could not be installed to the newly created server. The new server will not be able to send or receive asynchronous messages. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7135E: The following error occurred while attempting to retrieve the com.ibm.websphere.webservices.Constants.RESPONSE_TRANSPORT_PROPERTIES property from the response: {0}
Explanation The property indicated by the RESPONSE_TRANSPORT_PROPERTIES constant will not be available for the client application. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7136E: The system could not find an OperationDescription for the Web service request.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSWS7137W: The system could not correctly load the {0} binding file for the {1} EJB JAR file.
Explanation The binding file for an EJB JAR did not load correctly. If the EJB Jar file contains Web service implementations, it will not load correctly because the server cannot locate the router modules. Action If the EJB JAR contains Web service implementation classes, ensure that the specified binding file is contained in the JAR. Otherwise, no action is required.
WSWS7138E: The system cannot locate an EJB object. An EJB object is expected at dispatcher cleanup.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSWS7139E: The {0} method on the {1} class was not found.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSWS7140E: The server cannot locate the Web service endpoint interface for an EJB file.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSWS7141E: The server cannot locate an AxisService for the Web service request.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSWS7142E: The following error occurred during the invocation of an EJB Web service: {0}
Explanation A Web service request was not successfully invoked on an EJB component. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7143E: The system cannot find an enterprise bean for the Web service request.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSWS7144E: The system could not find an OperationDescription for the {0} operation.
Explanation The request is not processed because an OperationDescription is not found. Action Ensure that the Web service implementation class, service endpoint interface (SEI), or WSDL describes an operation with the given name.
WSWS7145E: More than one OperationDescription was found for the {0} operation.
Explanation The operation cannot be resolved because more than one matching OperationDescription was found in the WSDL file. The WSDl document describing the service must only specify one matching OperationDescription. The server does not support overloaded operations. Action Ensure that the WSDL document describing the Web service does not have overloaded operations.
WSWS7146E: The server cannot retrieve the Transport map service for the {0} component.
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7147E: The system could not locate the endpoint for {0}.
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7148I: The endpoint is currently stopped for {0}.
Explanation The endpoint at this URL is disabled for requests. Other endpoints within the service might still be running. Action To allow the endpoint to receive requests, enable the endpoint through either wsadmin.sh or the administrative console.
WSWS7149E: The {0} ejb-link value for the {1} EJB Web service implementation class did not correspond to an enterprise bean defined in the ejb-jar.xml file for the {2} module.
Explanation The system could not find a valid enterprise bean definition for the Web service implementation class. Action Ensure that the ejb-link value as defined by the name attribute of the @Stateless or @Singleton annotation on the Web service implementation class or specified in the webservices.xml file corresponds to an enterprise bean within the ejb-jar.xml file.
WSWS7150E: The system could not build a runtime configuration for the {0} application module because of the following error: {1}
Explanation The application module did not initialize successfully. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7151E: The {0} parameter cannot be added to the {1} annotation instance because it is not a known parameter.
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7152E: The {0} parameter cannot be obtained from the {1} annotation instance because it is not a known parameter.
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7153E: A null argument was passed to the {0} annotation processor.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSWS7154E: The system could not retrieve the runtime configuration for the {0} annotation processor.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSWS7155E: The system could not correctly build JAX-RPC service descriptions because of the following error: {0}
Explanation The Web service related metadata did not load successfully. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7156E: The {0} JAX-WS Web service implementation class referred to the {1} Service Endpoint Interface (SEI) class, but the SEI class did not have an @WebService annotation.
Explanation According to the JSR-181 specification, if a JAX-WS Web service implementation class refers to an SEI via the @WebService.endpointInterface value, the SEI class must also be annotated with the @WebService annotation. Action Make sure that the class referred to by the @WebService.endpointInterface value in your JAX-WS Web service implementation class contains the @WebService annotation.
WSWS7157E: The {0} JAX-WS Web service implementation class referred to the {1} Service Endpoint Interface (SEI) class, but the SEI class could not be found.
Explanation The @WebService.endpointInterface value on your JAX-WS Web service implementation class must specify a valid SEI class. Action Make sure that the class referred to by the @WebService.endpointInterface value in your JAX-WS Web service implementation class is located in the same application module or the application module's classloader can locate the class.
WSWS7158E: The {0} port-component element was identified as a JAX-RPC port component but was found in the {1} webservice-description element, which also contains JAX-WS port components. Mixing JAX-RPC and JAX-WS port components within the same webservice-description element is not allowed.
Explanation According to the JSR-109 specification, all port components within a webservice-description element must be based on the same type, either JAX-RPC or JAX-WS. Action Within a webservice-description element, all of the port components must be the same type, either JAX-WS or JAX-RPC.
WSWS7159E: The {0} port-component in the {1} webservice-description was identified as a JAX-RPC port component, but it did not contain a value in the service-endpoint-interface element.
Explanation According to the JSR-109 specification, the service-endpoint-interface element must be defined for JAX-RPC port components. Action If the port-component is intended to be a JAX-WS port-component, ensure that at least the implementation class contains the @WebService annotation. If the port component is intended to be a JAX-RPC port component, define the service-endpoint-interface element and ensure that it is contained in a webservice-description element that contains only JAX-RPC port components.
WSWS7160E: The {0} port-component in the {1} webservice-description was identified as a JAX-RPC port component, but the {2} SEI class specified by the service-endpoint-interface element contained the @WebService annotation.
Explanation Annotations may only be used to describe JAX-WS Web service implementations. Action If the port-component is intended to be a JAX-WS port-component, ensure that at least the implementation class contains the @WebService annotation. If the port-component is intended to be a JAX-RPC port-component, ensure the service-endpoint-interface element refers to an SEI class that does not contain annotations.
WSWS7161E: The {0} namespace URI was specififed for the {1} port, but this does not correspond to the {2} target namespace URI for the {3} JAX-WS Web service implementation class.
Explanation According to the JSR-109 specification, the port's namespace URI must match the target namespace URI for a Web service. Action Make sure that the port's namespace URI matches the target namespace URI for the Web service.
WSWS7162E: The target URL is not correctly defined.
Explanation The target URL is not defined in the JMS URL pattern. Action Define the target URL withinthe JMS URL pattern.
WSWS7163E: The JMS endpoint URL is missing one or more of the following required properties: connectionFactory, destination, targetService.
Explanation A JMS endpoint URL string must contain the following properties: connectionFactory, destination, targetService. These properties are used to describe the destination queue or the topic and target service. Action Make sure the JMS URL contains the connection factory, destination and target service properties.
WSWS7164E: Two-way requests are not supported for topic destinations.
Explanation A two-way request/response was invoked for a topic destination. Only one-way requests are supported when using a topic. Action Make sure that any services that use topic destinations contains only one-way operations.
WSWS7165E: The request wait has timed out.
Explanation The JMS request timed out. Action Consider increasing the read/write timeout. Check for network problems.
WSWS7166E: The reply message correlation ID does not match with the request message ID.
Explanation The messageID received from the request must match the reply message correlation ID. Action Make sure the correlation ID of the reply message matches with the request.
WSWS7167E: The input stream of the reply message is not correctly processed.
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7168E: The message type is not valid for the reply message.
Explanation The Web services JMS listener received a JMS message that was not a TextMessage or a BytesMessage. The JMS listener supports only these two JMS message types. Action Make sure that the JMS sender uses the correct JMS message type.
WSWS7169E: The MessageContext was not created correctly.
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7170E: The TargetService is not in the correct format.
Explanation The JMSSender did not set the indicated property on the JMS request message prior to sending the message to the destination queue or topic.This is an internal error. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7171E: The system cannot find the configuration for the JMS request.
Explanation The Web services message-driven bean listener was unable to retrieve a configured server engine during its initialization. Action Consult the logs in your <profile_home>/logs directory for more information..
WSWS7172E: The system encountered a JMS exception: {0}
Explanation A JMS operation did not complete successfully and resulted in the specified JMSException. Action Use the detailed information in the original error message to determine how to correct the problem.
WSWS7173E: The system encountered the following exception: {0}
Explanation None. Action None.
WSWS7174E: The {0} JNDI InitialContext object was not created.
Explanation An error occurred while trying to create a JNDI InitialContext object. Action Use the detailed information in the original error message to determine the problem.
WSWS7175E: The system encountered an naming exception during a JNDI operation: {0}
Explanation An error occurred during a JNDI lookup operation. Action Make sure that the JNDI name is correct.
WSWS7176E: The following exception is encountered in the {0} property in the JMS URL {1}
Explanation An internal system error occurred. Action Correct the JMS property in the URL.
WSWS7177E: The system encountered an AxisFault: {0}
Explanation The specified AxisFault exception occurred. Action Use the detailed information in the original error message to determine how to correct the problem.
WSWS7178E: The transport header key in the JMS request message cannot be processed.
Explanation The transport header key in the JMS request message cannot be processed. Action Ensure that all transport header keys in the JMS request message are in the correct format.
WSWS7179E: The system encountered the following exception during request processing: {0}
Explanation The specified exception occurred during request processing. Action Use the detailed information in the original error message to determine how to correct the problem.
WSWS7181E: The system encountered the following exception when sending the reply message: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSWS7190E: The request message does not include a SOAP message.
Explanation The request message sent by the client did not include a SOAP message to be processed by the server. Action Make sure the client generates and sends a request message that includes a SOAP message.
WSWS7191E: The response message does not include a SOAP message.
Explanation The response message sent by the server did not include a SOAP message to be processed by the client. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7192E: An error occurred attempting to configure the WSDL Reader: {0}
Explanation The configuration of the WSDL reader did not complete sucessfully. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7193E: An error occurred attempting to annotate WSDL definition for the {0} service: {1}
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7194E: An EndpointLifecycleManager instance was not successfully created.
Explanation A EndpointLifecycleManger instance failed to create successfully for an incoming request. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7195E: The metadata for the {0} service reference was not found.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSWS7196E: The {0} service reference on the {1} member in the {2} class specifies the {3} service-ref-type class but other metadata was found for this service reference which specifies the {4} service-ref-type class.
Explanation All metadata that corresponds to the same service reference must be consistent. Action Make sure that all metadata that corresponds to the same service reference according to the JNDI name is consistent and does not specify different values.
WSWS7197E: The {0} service reference on the {1} member in the {2} class specifies the {3} service-interface class but other metadata was found for this service reference which specifies the {4} service-interface class.
Explanation All metadata that corresponds to the same service reference must be consistent. Action Make sure that all metadata that corresponds to the same service reference according to the JNDI name is consistent and does not specify different values.
WSWS7198E: The @HandlerChain annotation specified for the {0} service reference on the {1} member in the {2} class specifies the {3} name. This conflicts with the {4} name that was specified for handler chain information previously associated with this service reference.
Explanation All handler chain metadata that corresponds to the same service reference must be consistent. Action Make sure that all handler chain metadata that corresponds to the same service reference according to the JNDI name is consistent and does not specify different values.
WSWS7199E: The @HandlerChain annotation specified for the {0} service reference on the {1} member in the {2} class specifies the {3} file value. This conflicts with the {4} file value that was specified for handler chain information previously associated with this service reference.
Explanation All handler chain metadata that corresponds to the same service reference must be consistent. Action Make sure that all handler chain metadata that corresponds to the same service reference according to the JNDI name is consistent and does not specify different values.
WSWS7200E: The @WebServiceRef or @Resource annotation on the {0} class does not specify a value for the name or type attribute. For @WebServiceRef or @Resource annotations found at the class level, the name and type attributes are required.
Explanation According to the Java Enterprise Edition 5 Platform specification, if an @WebServiceRef or @Resource annotation is used at the class level, then the name and type attributes are required. Action Make sure that any class level @WebServiceRef or @Resource annotations specify valid name and type attributes.
WSWS7201E: The @WebServiceRef annotation was found on the {0} class, but the type attribute and the value attribute do not specify the same class. If the @WebServiceRef annotation indicates a service type injection, and the value attribute does not specify the javax.xml.ws.Service class, the class specified by the type and value attributes must be the same.
Explanation If an @WebServiceRef annotation is being used for service type injection, the type and value attributes must indicate the same service subclass, or the value attribute must be omitted or specify the javax.xml.ws.Service class. Action Make sure that @WebServiceRef annotations specifying a service type injection have the appropriate type and value attribute values.
WSWS7202E: An @WebServiceRef or @Resource annotation was found on the {0} method in the {1} class, but the method does not follow the standard JavaBeans convention.
Explanation According to the JSR-250 specification, if the @WebServiceRef or @Resource annotation is found on a method, the method must have exactly one parameter, must begin with the set operation, and must have a void return type. Action Make sure that any methods that include an @WebServiceRef or @Resource annotation follow the JavaBans convention.
WSWS7203E: The @WebServiceRef or @Resource annotation was found on the {0} member in the {1} class but the type of injection could not be inferred from either the type attribute or the member type.
Explanation According to the JSR-250 specification, the type attribute is required if the injection type cannot be inferred by the member type the @WebServiceRef or @Resource is annotating. Action Make sure that @WebServiceRef or @Resource annotations specify a type class other than java.lang.Object, or that the type can be inferred from the member it is annotating.
WSWS7204E: The @WebServiceRef annotation was found on the {0} member in the {1} class, but the {2} class specified by the value attribute was not a subclass of javax.xml.ws.Service. If an @WebServiceRef annotation is used for injection of a port, the value attribute must specify a class that is a subclass of javax.xml.ws.Service.
Explanation According to the JSR-224 specification, when the @WebServiceRef annotation is used for injection of a port, the value attribute is required. Specify a class that is a subclass of javax.xml.ws.Service. Action Make sure that @WebServiceRef annotation that requests the injection of a port specifies a class that is a subclass of javax.xml.ws.Service in the value attribute.
WSWS7205E: The @WebServiceRef or @Resource annotation was found on the {0} member in the {1} class, but the type attribute specifies the {2} class that is not compatible with the {3} class of the annotated member.
Explanation According to the JSR-250 specification, the type attribute of the @WebServiceRef or @Resource annotation must be compatible with the type of the member it is annotating. Action Make sure that @WebServiceRef or @Resource annotations specify a type attribute that is compatible with the member type of the annotation.
WSWS7206E: The @WebServiceRef annotation was found on the {0} member in the {1} class, but the type attribute and the value attribute do not specify the same class. If the @WebServiceRef annotation indicates a service type injection, and the value attribute does not specify the javax.xml.ws.Service class, the class specified by the type and value attributes must be the same.
Explanation If an @WebServiceRef annotation is used for service type injection, the type and value attributes must indicate the same service subclass, or the value attribute must be omitted or specify the javax.xml.ws.Service class. Action Make sure that @WebServiceRef annotations specifying a service type injection have the appropriate type and value attribute values.
WSWS7207E: The @WebServiceRef annotation was found on the {0} member in the {1} class, but the value attribute did not specify a class that is a subclass of the javax.xml.ws.Service class. If the @WebServiceRef annotation is used to indicate port injection, the value attribute must specify a class that is a subclass of the javax.xml.ws.Service class.
Explanation If an @WebServiceRef annotation is used for port injection, the value attribute must specify a class that is a subclass of javax.xml.ws.Service and is capable of producing the type of port requested for injection. Action Make sure that @WebServiceRef annotations specifying a port type injection have the appropriate class specified in the value attribute.
WSWS7208E: The @WebServiceRef annotation was found in the {1} class, but the {2} class specified by the value attribute was not a subclass of javax.xml.ws.Service. If the @WebServiceRef type attribute specifies an service endpoint interface (SEI) class, the value attribute must specify a subclass of javax.xml.ws.Service.
Explanation According to the JSR-224 specification, when the @WebServiceRef type attribute specifies an SEI class, the value attribute must specify the javax.xml.ws.Service subclass. Action Make sure that any @WebServiceRef annotation whose type attribute specifies an SEI class has a corresponding value attribute which specifies a subclass of javax.xml.ws.Service.
WSWS7209W: The {0} service reference in the {1} module is missing either the service QName or WSDL file location attribute. This may cause unpredictable results when this service reference is requested.
Explanation Fully specify the metadata for service references using annotations or deployment descriptors. Action Make sure that metadata for service references is fully specified using either annotations or deployment descriptors.
WSWS7210E: The {0} internal service class was not found.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSWS7211E: The {0} application client file was not processed due to the following error: {1}
Explanation An error occurred while attempting to obtain the metadata in the application client file. Action Enable application client tracing for further information about the error.
WSWS7212E: A {0} class-level service reference was found which specifies the {1} service-ref-type class but another service reference was found which specifies the {2} service-ref-type class.
Explanation All metadata that corresponds to the same service reference must be consistent. Action Make sure that all metadata that corresponds to the same service reference according to the JNDI name is consistent and does not specify different values.
WSWS7213E: A {0} class-level service reference was found which specifies the {1} service-interface class but another service reference was found which specifies the {2} service-interface class.
Explanation All metadata that corresponds to the same service reference must be consistent. Action Make sure that all metadata that corresponds to the same service reference according to the JNDI name is consistent and does not specify different values.
WSWS7214E: The @HandlerChain annotation specified for the {0} class-level service reference specifies the {1} name. This conflicts with the {2} name that was specified for handler chain information previously associated with this service reference.
Explanation All handler chain metadata that corresponds to the same service reference must be consistent. Action Make sure that all handler chain metadata that corresponds to the same service reference according to the JNDI name is consistent and does not specify different values.
WSWS7215E: The @HandlerChain annotation specified for the {0} class-level service reference specifies the {1} file value. This conflicts with the {2} file value that was specified for handler chain information previously associated with this service reference.
Explanation All handler chain metadata that corresponds to the same service reference must be consistent. Action Make sure that all handler chain metadata that corresponds to the same service reference according to the JNDI name is consistent and does not specify different values.
WSWS7216E: The following error occured during a JNDI lookup operation for the {0} connection factory : {1}
Explanation The specified exception occurred while starting the connection factory. Action Make sure the connection factory exists and is valid.
WSWS7217E: The following error occurred while starting the JMS Async Response Message Listener: {0}
Explanation The specified exception occurred while starting the JMS Async Response Message Listener. Action Use the detailed information in the original error message to determine how to correct the problem.
WSWS7218E: The following error occurred while stopping the JMS Async Message Listener: {0}
Explanation The specified exception occurred while starting the connection factory. Action Make sure the connection factory exists and is valid.
WSWS7219I: The {0} context ID was received from an unknown asynchronous response.
Explanation A response message was received that was not identifiable by the JMS Listener for processing. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7220E: A JAX-WS handler instance was not created because the handler class is null.
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7221E: An instance of the {0} JAX-WS handler class was not created due to the following error: {1}.
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7222E: Injection targets were not retrieved due to the following error: {0}.
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7223E: The module metadata was not available after injection meatdata was created.
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7224E: The {0} service reference in the {1} module was identfied as a JAX-WS style service-reference, but the service-interface element specifies the {2} class that is not a subclass of javax.xml.ws.Service.
Explanation For JAX-WS service references, the service-interface value must specify a subclass of javax.xml.ws.Service. Action Make sure that the JAX-WS service-interface class is a subclass of javax.xml.ws.Service. Modify the service-ref entry for the appropriate module and service reference.
WSWS7225E: The {0} service reference in the {1} module specifies a javax.xml.ws.Service class type in the service-interface and service-ref-type elements, but the class names do not match. If both element types specify a javax.xml.ws.Service class type, they must specify the same class.
Explanation If the service-interface and service-ref-type values both specify a subclass of javax.xml.ws.Service, the class specified by both elements must be the same. Action Make sure that the class specified by both elements is the same when the service-interface and service-ref-type values specify a subclass of javax.xml.ws.Service. Modify the service-ref entry for the appropriate module and service reference.
WSWS7226E: The {0} service reference in the {1} module was identfied as a JAX-RPC style service-reference, but the service-interface element specifies the {2} class which is not a subclass of javax.xml.rpc.Service.
Explanation For JAX-RPC service references, the service-interface value must specify a subclass of javax.xml.rpc.Service. Action Make sure that the JAX-RPC service-interface class is a subclass of javax.xml.rpc.Service. Modify the service-ref entry for the appropriate module and service reference.
WSWS7227E: No methods were found for the {0} EJB Web service endpoint class.
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7228E: The required {0} property in the inbound JMS request message is incorrect.
Explanation The JMSSender did not set the correct property on the JMS request message prior to sending the message to the destination queue or topic. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7229E: The required {0} property is missing in the inbound JMS request message.
Explanation The JMSSender did not set the indicated property on the JMS request message prior to sending the message to the destination queue or topic. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7230E: The required {0} property is missing in the inbound JMS request message.
Explanation The JMSSender did not set the indicated property on the JMS request message prior to sending the message to the destination queue or topic. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7231E: The required {0} property is incorrect in the inbound JMS request message.
Explanation The JMSSender did not set the correct version on the JMS request message prior to sending the message to the destination queue or topic. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7232E: A response was not written to the output stream because a message formatter was not found.
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7233E: The {0} JAX-WS application handler class did not load correctly because of the following error: {1}.
Explanation A class that was specified as a JAX-WS application handler could not be loaded. Action Make sure that the JAX-WS application handler class is available to the application module.
WSWS7234E: The {0} class was specified as a JAX-WS application handler, but it is not a javax.xml.ws.handler.Handler type.
Explanation A class that was specified as a JAX-WS application handler class was not a valid type. Action Make sure that any classes specified as JAX-WS application handler classes are a javax.xml.ws.handler.Handler type.
WSWS7235E: The {0} web service implementation in an EJB module could not be invoked because a target method could not be found.
Explanation A target method could not be found for the web service request. Action If the endpoint is an implementation of javax.xml.ws.Provider, make sure that there is a method named 'invoke'. Otherwise, make sure that at least one method is exposed by the Web service endpoint.
WSWS7236E: Internal error. A response from a web service endpoint in an EJB module could not be processed because an endpoint manager could not be located.
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7237E: Internal error. An instance of the {0} web service implementation class could not be located.
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7238E: Web service references specified in the {0} module in the {1} application could not be correctly processed due to the following error {2}.
Explanation Web service references indicated in a deployment descriptor within the module caused an error during processing. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7239E: The web service metadata for the {0} module in the {1} application could not be processed correctly due to the following error {2}.
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7240E: Annotation metadata for the @Resource or @WebServiceRef annotation in the {0} class could not be merged due to the following error: {1}
Explanation An error occurred attempting to merge annotation metadata with deployment descriptor metadata. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7241E: Annotation metadata for the @Resource or @WebServiceRef annotation on the {0} member in the {1} class could not be merged due to the following error: {2}
Explanation An error occurred attempting to merge annotation metadata with deployment descriptor metadata. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7242E: An @Resource annotation was found in the {0} class that specified a JAX-RPC service reference but a service-ref with the {1} service-ref-name was not defined in the deployment descriptor.
Explanation @Resource annotations used to specify JAX-RPC service references must correspond to a service-ref element defined in the deployment descriptor. Action Make sure that the @Resource annotation name attribute matches the value of a service-ref-name element within the deployment descriptor.
WSWS7243E: Validation of the @Resource or @WebServiceRef annotation in the {0} class failed due to the following error: {1}
Explanation An error occurred attempting to validate annotation metadata specified in a class. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7244E: Validation of the @Resource or @WebServiceRef annotation on the {0} member in the {1} class failed due to the following error: {2}
Explanation An error occurred attempting to validate annotation metadata specified in a class. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7245E: An @Resource or @WebServiceRef annotation on the {0} member in the {1} class specifies the {2} type which is not compatible with the {3} type targetted for injection.
Explanation The class type indicated by the method level annotation is not compatible with the method parameter type. Action Make sure that the annotation specifies a type that is compatible with the method parameter type.
WSWS7246E: An @Resource or @WebServiceRef annotation was found on the {0} field in the {1} class, but the field is declared as final. This is not allowed by the Java Enterpise Editon 5 Platform Specification.
Explanation Annotations that specify injection may not be placed on fields declared as final. Action Make sure that annotations specifying injection are not used on fields declared as final.
WSWS7247E: An @WebServiceRef annotation was found on the {0} class but neither the type nor the value attribute referred to a javax.xml.ws.Service class type. Either the type or value attribute must refer to a java.xml.ws.Service class type.
Explanation According to JSR-224, if the @WebServiceRef annotation is used at the class level, a javax.xml.ws.Service class type must be specified. Action Make sure that @WebServiceRef annotations at the class level specify a javax.xml.ws.Service class type in either the value or type attribute.
WSWS7248E: An @WebServiceRef annotation was found on the {0} member in the {1} class but neither the type nor the value attribute referred to a javax.xml.ws.Service class type. Either the type or value attribute must refer to a java.xml.ws.Service class type.
Explanation According to JSR-224, if the @WebServiceRef annotation is used at the class level, a javax.xml.ws.Service class type must be specified. Action Make sure that @WebServiceRef annotations at the class level specify a javax.xml.ws.Service class type in either the value or type attribute.
WSWS7249E: Could not find the Endpoint Manager MBean for the application {0}, module {1}.
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7250E: Web service metadata for the JAX-WS Web service cannot be completed because the {0} class indicated by a deployment descriptor in the {1} module cannot be located.
Explanation A class specified in a deployment descriptor within the module cannot be located. Action Make sure that all classes specified in the module's deployment descriptors are visible to the module.
WSWS7251E: The {0} ejb-link value was specified by the {1} port-component in the webservices.xml within the {2} module, but an enterprise bean with that name was not found.
Explanation A port-component defined an ejb-link value that did not correspond to an enterprise bean defined in the module. Action Make sure that the ejb-link value matches a valid enterprise bean name within the module.
WSWS7252E: The {0} servlet-link value was specified by the {1} port-component in the webservices.xml within the {2} module, but a servlet with that name was not found.
Explanation A port-component defined a servlet-link value that did not correspond to an servlet defined in the module. Action Make sure that the servlet-link value matches a valid servlet name within the module.
WSWS7253E: The {0} service-endpoint-interface class specified by the webservices.xml in the {1} module cannot be located.
Explanation The class specified in the service-endpoint-interface element could not be loaded. Action Make sure that the class specified in the service-endpoint-interface element of the webservices.xml is visible to the module.
WSWS7254E: Client binding information for the {0} module in the {1} application could not be processed due to the following error: {2}.
Explanation Client binding information for the module will not be available due to the error. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7255E: Client binding information for the {0} application could not be processed due to the following error: {1}.
Explanation Client binding information for the application modules will not be available due to the error. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7256E: The {0} custom handler did not define a phase, or it defined a phase which is not allowed for custom handlers.
Explanation Custom handlers can only be inserted into the phases allowed by the runtime. Action Make sure that all custom handlers define a phase which is allowed by the runtime.
WSWS7257E: Some operations for service {0} do not have a configured SSL policy set.
Explanation If an SSL policy set is configured for one or more operations within a service, then all operations within that service must also be configured with an SSL policy set. Within the set of operations for a particular service, either all of the operations must be configured with an SSL policy set, or none of them should be configured with an SSL policy set. Note that the operations do not have to be configured with the same SSL policy set. Operations may be configured with different SSL policy sets. Action Make sure that all operations belonging to a service are either all configured with an SSL policy set, or make sure that none of them are configured with an SSL policy set.
WSWS7258E: WSDL files for the {0} module will not be generated due to the following error: {1}
Explanation JAX-WS Web services in the module will not be available because WSDL files could not be generated. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7259E: The {0} service-endpoint-interface class was defined in the webservices.xml for the {1} JAX-WS implementation class, but an @WebService annotation was not found on the service-endpoint-interface class.
Explanation According to the JSR-181 specification, JAX-WS SEI classes must be annotated with the @WebService annotation. Action Make sure that all JAX-WS SEI classes have an @WebService annotation.
WSWS7260E: The system encountered an error retrieving the inbound request content length.
Explanation The inbound request content length could not be determined. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7261E: Web services configuration information was not available for an incoming request.
Explanation The incoming request cannot be processed because the configuration is not available for the request. Action Consult the logs in your <profile_home>/logs directory for more information.
WSWS7262E: Web services metadata cache could not be generated for the {0} application due to the following error: {1}.
Explanation The web services engine encountered the specified error while it was generating the metadata cache for the application; therefore, the generation of the metadata cache failed. Action Consult the error information contained in the application server log files to determine the cause of the error.
WSWS7263E: The following exception occured: {0}
The previous error might have been caused by a lack of system resources due to server is too busy processing multiple requests.
Explanation One reason for the IOException might have been caused because the server is too busy. Action Configuring the persist read timeout to be higher than the default 30 secs can fix this problem. The persist read can be configured in the admin GUI as follows: Server > Application Servers > {Server Name} > Web Container Transport Chains > {Chain Name} > {Channel Name: <HTTP Channel> } >
WSWS7264E: The @WebServiceRef annotation incorrectly specified the 'lookup' attribute in addition to other attributes.
Explanation The @WebServiceRef annotation was found on a class, method, or field which specified the 'lookup' attribute as well as other attributes. When the 'lookup' attribute is specified on the @WebServiceRef annotation, then only the 'name' attribute can also specified on the annotation. Action If you would like to use the 'lookup' attribute on the @WebServiceRef annotation, then remove all other attributes except for the 'name' attribute.
WSWS7265E: The previous error occurred on the @WebServiceRef annotation which was specified on the following injection target: {0}
Explanation This message is simply providing more information about the previous error message to aid the user in resolving the problem. Action Please see the previous error message for more information on how to correct the problem.
WSWS7266E: An error occurred while processing the @WebServiceRef or @Resource annotation which was specified on the following injection target: {0}
Explanation This message indicates the injection target which contains the incorrect @WebServiceRef or @Resource annotation. Action Please see the nested exception for the specific reason for this error.
WSWS7270W: Transport property {0} is invalid and cannot be processed.
Explanation The specified transport property was found in the request transport property Map but was not valid and could not be added to the JMS or HTTP request message. This could be because the value was not of a supported datatype or the property name was not a valid non-empty string. Action Make sure that the request transport property Map is constructed correctly and that the transport property is of a supported datatype.
WSWS7271E: The JMS endpoint URL is missing one or more of the following required properties: jndiConnectionFactoryName, targetService.
Explanation A JMS endpoint URL string must contain the following properties: jndiConnectionFactoryName, targetService. These properties are used to describe the jndi connection factory and target service. Action Make sure the JMS URL contains the jndiConnectionFactoryName and targetService properties.
WSWS7272E: The endpoint address URL is not of JMS type.
Explanation A Web services request was made which involves the JMS transport, but the request does not start with jms or jms:jndi for the JMS endpoint address URL. Action Make sure that the request contains a valid JMS endpoint address URL. If this request was invoked within the Web Services Gateway, make sure the proper configuration has been done.
WSWS7273E: The required {0} property was not present in the inbound JMS request message.
Explanation The JMSSender did not set the indicated property on the JMS request message prior to sending the message to the destination queue or topic. This is an internal error. Action Make sure that the JMS Message contains a valid SOAPJMS_requestURI property set.
WSWS7274E: The inbound JMS request URL is not in the correct format.
Explanation The format of the inbound JMS request URL {0} is not correct. Action Make sure that the inbound JMS request URL is in the correct format.
WSWS7275E: The inbound JMS request URI {1} contains target Service {0}.
Explanation The inbound JMS request URI contained target Service prior to sending the message to the destination queue or topic. Action Make sure that the inbound JMS request URI does not contain Target Service.
WSWS7276E: The charset {0} in contentType header does not match with XML encoding statement {1} sent to the request queue.
Explanation The charset parameter is specified in content type header and it does not match the encoding value from the supplied XML Action Make sure that the charset matches between contentType header and XML encoding statement.