Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An exception was thrown by the security component. |
Action | See the accompanying error messages for further information. |
Explanation | All messages that reference the reliable messaging sequence must provide proof-of-possession of the security token. |
Action | Ensure that the originator of the message is using an appropriate security configuration. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | When attempting the operation "writeOutstandingSequenceMessagesToBuffer" the sequence identifier was not found. |
Action | Ensure the sequence exists in the administrative console for the application. |
Explanation | It is not permitted to reallocate messages from one Web services Reliable Messaging sequence to another if the sequence contains application response messages for a two-way operation. |
Action | Ensure the sequence is a request sequence. |
Explanation | A managed quality of service (QOS) configuration is not supported in the client container. The WS-ReliableMessaging storage manager could not be started. |
Action | Configure the application to use a policy set that specifies an unmanaged quality of service (QOS). |
Explanation | A managed quality of service (QOS) configuration requires a policy set binding in order to initialize. |
Action | Configure a policy set binding for the application. |
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 | 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 attempt has been made to use the Web services reliable messaging managed quality of service, but the messaging engine is unavailable. |
Action | Ensure that the correct messaging engine and bus names are being specified and check that the messaging engine has been started. |
Explanation | An attempt has been made to use the Web services reliable messaging managed quality of service, but the messaging engine is unavailable. |
Action | Ensure that the correct messaging engine and bus names are being specified and check that the messaging engine has been started. This message is a warning and attempts to connect to the messaging engine will be made |
Explanation | When using the managed persistent or the managed non-persistent quality of service for reliable messaging, the application needs to be bound to a messaging engine and bus. |
Action | Check that the reliable messging bindings for the application have been defined and contain a valid bus and bus member. |
Explanation | The unmanaged non-persistent quality of service for reliable messaging cannot be associated with an application running inside an application server hosted on a Z-series machine. |
Action | For applications running inside an application server on a Z-series machine, use a managed persistent or managed non-persistent quality of service. |
Explanation | A binding was supplied that contained one or more attributes that were not recognised. |
Action | Check each attribute specified in the binding and ensure that it is a valid WS-ReliableMessaging binding attribute. |
Explanation | A policy type was supplied that contained one or more attributes that were not recognised. |
Action | Check each attribute specified in the policy type and ensure that it is a valid WS-ReliableMessaging policy type attribute. |
Explanation | A Webservices reliable messaging policy was supplied that was not recognised. The supported policy type versions are http://schemas.xmlsoap.org/ws/2005/02/rm/policy and http://docs.oasis-open.org/ws-rx/wsrmp/200702 |
Action | Check that the Webservices reliable messaging policy being used contains a supported policy version. |
Explanation | The parameter specified must not be null when calling the specified method. |
Action | Update the application to provide a non-null value for the specified parameter. |
Explanation | The supplied parameter value for clientObject is not a known type. The clientObject needs to be an instance of either a JAX-WS Dispatch or a dynamic proxy client. |
Action | Ensure that the parameter value supplied to the method call is either a instance of the Dispatch class, or an instance of the dynamic proxy. |
Explanation | The target provider endpoint URI must not be null when trying to establish a new Web services reliable messaging sequence. |
Action | Update the application to provide a non-null value for the target provider endpoint URI in the WSRMSequenceProperties. |
Explanation | A call has been made to the API method "waitUntilSequenceCompleted" which can not complete as there is a transaction for the specified sequence which has not been committed. This is normally due to the application being installed inside the EJB container and using container managed transactions. In this case the invoke for the target endpoint and "waitUntilSequenceCompleted" can not occur inside the same transaction. |
Action | Ensure that all transactions are committed prior to invoking "waitUntilSequenceCompleted". |
Explanation | An application has tried to use Web services reliable messaging, but reliable messaging is not enabled for this application. |
Action | Assign a Web services reliable messaging policy set to the application. |
Explanation | An application has tried to use a Web services reliable messaging sequence, but no sequence has been found between this application and the target endpoint URI. The client might have previously terminated the sequence, the sequence might have timed out, or the sequence is non-persistent and the client application has been restarted. |
Action | Use the administrative console to check the status of the Web services reliable messaging sequence for the application. |
Explanation | An application has tried to use a Web services reliable messaging sequence that has previously been terminated. The client might have previously terminated the sequence, the sequence might have timed out, or the sequence is non-persistent and the client application has been restarted. |
Action | Use the administrative console to check the status of the Web services reliable messaging sequence for the application. |
Explanation | An application has attempted to use a Web services reliable messaging sequence that has previously been closed. The client might have previously closed the sequence. |
Action | Use the administrative console to check the status of the Web services reliable messaging sequence for the application. |
Explanation | An application has attempted to create a Web services reliable messaging sequence to a target endpoint URI for which a sequence already exists. The client might have previously created the sequence. |
Action | Use the administrative console to check the status of the Web services reliable messaging sequence for the application. |
Explanation | The closeSequence request is only supported in Version 1.1 of the reliable messaging specification. The application is using Version 1.0 of the specification so no action is undertaken in the reliable messaging runtime. |
Action | Either remove the call to closeSequence from the application, or update the policy set to use Version 1.1 of the reliable messaging specification. |
Explanation | Certain message exchange patterns, such as two-way request-reply messaging, do not support transactional updates to the Web services reliable messaging storage manager. |
Action | Check the message exchange pattern that is used for the specified service and ensure that transactional updates are supported. |
Explanation | Transactional sends enlist the Web services reliable messaging storage manager in the application's transactional context. If your application does not have a transactional context then this cannot be done. |
Action | Either ensure your application has a transactional context at the time of putting or change to a non-transactional put. |
Explanation | Transactional sends enlist the Web services reliable messaging storage manager in the application's transactional context, but can only do this if the application's configuration selects a managed store. |
Action | Either change to managedPersitent or managedNonPersistent quality of service or change the application to perform non transactional sends. |
Explanation | If the message does not give sufficient information, check the accompanying messages. |
Action | See the accompanying error messages for further information. |