Explanation | This informational message indicates that the Application Server Axis2 service has been started. |
Action | No action is required. |
Explanation | An error occurred while attempting to load application metadata. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An error occurred while attempting to load application metadata. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
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. |
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. |
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. |
Explanation | The configuration for the application module could not load correctly. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occured. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
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. |
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. |
Explanation | An internal system error has occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
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. |
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. |
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. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An error occurred trying to load Web service related metadata. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | The module's web.xml file may contain syntax errors. |
Action | Ensure that the module's web.xml is correct. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
Explanation | An internal system error occured. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | A single servlet has defined more than one mapping entry. |
Action | Ensure that every servlet has only one servlet mapping defined. |
Explanation | A required parameter was not available on the AxisService. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | Performance metrics for the application module will not be available. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | A WSDL or XSD file could not be located. |
Action | Ensure that the file exists. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The application module configuration information could not be correctly loaded. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
Explanation | The class may contain annotations that are not valid. |
Action | Ensure all annotations are defined correctly. |
Explanation | An internally registered class does not implement the correct interface. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
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. |
Explanation | A Web services cache could not be created. This will not affect the availability of the application. |
Action | No action is required. |
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. |
Explanation | The cache file will not be written. This will not affect the availability of the application. |
Action | No action is required. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | The Web Services Description Language (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. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
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. |
Explanation | This informational message describes the current condition of the outbound HTTP connection pool. |
Action | No user action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
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. |
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. |
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. |
Explanation | Received SSL properties from the security component. The same properties are registered with the event listener. |
Action | No action is required. |
Explanation | The listening host and port have been configured to be associated with each other. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | An unsupported schema for using HTTP transport was found. |
Action | Verify the target endpoint address is valid. |
Explanation | The listed data for host, port, and URI path was used to map to a valid cluster name. |
Action | No action is required. |
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. |
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. |
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. |
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. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
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. |
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. |
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. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | This is an internal error. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
Explanation | This is an internal error. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The servlet required for asynchronous messaging is not available. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | The servlet required for asynchronous messaging could not be initialized. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
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. |
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. |
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. |
Explanation | This is an internal error. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
Explanation | This is an internal error. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
Explanation | This is an internal error. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | This is an internal error. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | The asynchronous servlet is not available to accept asynchronous responses. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | This is an internal error. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | This is an internal error. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | This is an internal error. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | This is an internal error. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | This is an internal error. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | No HTTP status information is available to determine the HTTP response. |
Action | Make sure the target HTTP server is up. |
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. |
Explanation | This is an internal error. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
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. |
Explanation | This is an internal error. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
Explanation | This is an internal error. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | This is an internal error. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | The system runtime was unable to resolve an effective Secure Sockets Layer (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. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
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. |
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. |
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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
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. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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 the wsadmin tool or the administrative console. |
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. |
Explanation | The application module did not initialize successfully. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The Web service related metadata did not load successfully. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | The target URL is not defined in the JMS URL pattern. |
Action | Define the target URL withinthe JMS URL pattern. |
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. |
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. |
Explanation | The JMS request timed out. |
Action | Consider increasing the read/write timeout. Check for network problems. |
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. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
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.. |
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. |
Explanation | None. |
Action | None. |
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. |
Explanation | An error occurred during a JNDI lookup operation. |
Action | Make sure that the JNDI name is correct. |
Explanation | An internal system error occurred. |
Action | Correct the JMS property in the URL. |
Explanation | The specified AxisFault exception occurred. |
Action | Use the detailed information in the original error message to determine how to correct the problem. |
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. |
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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
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. |
Explanation | The configuration of the WSDL reader did not complete sucessfully. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
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. |
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. |
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. |
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. |
Explanation | The specified exception occurred while starting the connection factory. |
Action | Make sure the connection factory exists and is valid. |
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. |
Explanation | The specified exception occurred while starting the connection factory. |
Action | Make sure the connection factory exists and is valid. |
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. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
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. |
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. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
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. |
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. |
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. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
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. |
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. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | An internal system error occurred. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | The inbound request content length could not be determined. |
Action | Consult the logs in your <profile_home>/logs directory for more information. |
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. |
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. |
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> } > |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |