Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | WS-Notification requests can now be actioned by this WS-Notification service. |
User response | No action required. |
Problem | WS-Notification requests can now be actioned by this WS-Notification service. |
User response | No action required. |
Problem | WS-Notification requests can no longer be actioned by this WS-Notification service on this messaging engine. |
User response | The messaging engine must be restarted before further WS-Notification requests can be actioned by this messaging engine. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | The custom property does not accept the specified value as a valid setting, the property will be ignored |
User response | Correct the configured value of the custom property in the configuration of the WSN Service |
Problem | The call to the remote NotificationProducer could not be completed or the remote broker returned an error. Check the exception for more information. |
User response | If the remote NotificationProducer is not available, wait until it becomes available again before retrying this operation. Alternatively, seek assistance from the administrator of the remote NotificationProducer. |
Problem | The call to the remote NotificationBroker could not be completed or the remote NotificationBroker returned an error. Check the exception for more information. |
User response | This operation will be retried automatically requiring no user intervention. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | The broker is configured to only allow registered publishers to perform the notify operation. |
User response | Ensure that the publisher application registers its intent to notify on this topic and retry the operation. |
Problem | The remote web service was successfully contacted, but responded with a non-transient fault or error condition. This may be due to incorrect configuration of the administered subscriber, or the remote web service. |
User response | The Administrator should resolve the configuration problems and then restart the application server to start the administered subscriber. |
Problem | An unsupported dialect was specified in the topic expression part of a notify message. |
User response | Retry the notify operation using a supported topic dialect. |
Problem | Validation of the topic name with respect to the specified dialect could not be completed. |
User response | Retry the notify operation using a valid topic name for the specified dialect. |
Problem | The topic namespace documents do not allow the specified topic name. |
User response | Examine the stack trace for further information and retry the notify operation using a valid topic name for this configuration. |
Problem | The topic namespace documents do not allow messages of the specified type. |
User response | Examine the stack trace for further information and retry the notify operation using a valid message type for this configuration. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | A subscription request was rejected because the Pull Point Id was invalid. The Pull Point may not have been created or may have terminated asynchronously. |
User response | Recreate the Pull Point and retry the subscription request with the new Pull Point Id |
Problem | A subscription request was rejected by the Notification Broker. |
User response | Examine the stack trace for further information and if appropriate, retry the request. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | A register publisher request was received for a topic namespace, but the topic namespace was unknown to the Notification Broker. |
User response | Retry the register publisher request supplying a valid topic namespace name. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | A Servant has been dispatched to perform an operation on an external Web service but the Control Region Adjunct has timed out waiting for a confirmation that the work was completed. The work may have completed successfully, or not at all. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | The call to the remote NotificationProducer could not be completed or the remote NotificationProducer returned an error. Check the exception for more information. |
User response | This operation will be retried automatically requiring no user intervention. |
Problem | The topic namespace configuration instance documents do not allow the requested topic. |
User response | Either perform the operation on a topic which is permitted by the tree, or alter the topic namespace configuration instance document to permit it. |
Problem | The topic namespace documents do not allow the requested topic. |
User response | Either perform the operation on a topic which is permitted by the tree, or alter the topic namespace document to permit it. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | The publication registration cannot be located. It may not have been created or it may have terminated. |
User response | Retry the request specifying a valid publication registration. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | The publication registration cannot be located. It may not have been created or it may have terminated. |
User response | Retry the request specifying a valid publication registration. |
Problem | A termination time was specified but it was rejected by the Notification Broker. The most likely cause is that the termination time has passed. |
User response | Retry the request specifying a valid termination time. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | The above subscription has expired but an error occurred during the termination. The subscription may not have been fully terminated. |
User response | Examine the stack trace for further information into this failure. It may also be possible to manually destroy this subscription. |
Problem | The subscription failed to be resumed. Message delivery to any Web services registered with this subscription may not re-commence. |
User response | Examine the stack trace for further information into this failure and retry the operation. |
Problem | The subscription cannot be located. It may not have been created or it may have terminated. |
User response | Retry the request specifying a valid subscription. |
Problem | A message was received that matched a subscription but an attempt to notify the Web service failed. Message delivery for this subscription will be temporarily suspended and retried automatically. |
User response | Investigate the cause of the exception. |
Problem | The message received could not be converted into a form that can be encoded into a SOAP message for a Web service and so was not sent. |
User response | No user action. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | An attempt is being made to apply an instance document that appears to refer to a different namespace. |
User response | Apply the document to the correct namespace. |
Problem | The 'targetNamespace' parameter is mandatory in a topic namespace instance configuation document. |
User response | Ensure the document contains a valid 'targetNamespace' attribute. |
Problem | The instance document cannot be parsed as it does not appear to contain a 'TopicNamespace' qualified name value. |
User response | Ensure the document is a valid topic namespace instance document. |
Problem | The instance document cannot be parsed. |
User response | Ensure the document is a valid topic namespace instance document. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | The topic namespace cannot be used until invalid topic namespace instance documents are corrected or removed from the topic namespace configuration. |
User response | Check and resolve previous errors in the log that indicate the problem with the topic namespace instance documents. |
Problem | If more than one topic namespace instance documents are applied to a particular topic namespace then they must not contain conflicting information. |
User response | Correct the conflicting information in the topic namespace instance document and re-apply the document. |
Problem | If more than one topic namespace instance documents are applied to a particular topic namespace then they must not contain conflicting information. |
User response | Correct the conflicting information in the topic namespace instance document and re-apply the document. |
Problem | If more than one topic namespace instance documents are applied to a particular topic namespace then they must not contain conflicting information. |
User response | Correct the conflicting information in the topic namespace instance document and re-apply the document. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | The broker is not configured to support dynamic namespaces. |
User response | Register the namespace with the broker or enable dynamic namespaces. |
Problem | The topic namespace documents do not allow messages of the specified topic name. |
User response | Either modify the topic name to adhere to the topic namespace documents or modify the topic namespace documents to permit this topic name. |
Problem | An attempt to confirm a subscription's existence produced an unexpected outcome. |
User response | Investigate the status of the subscription on the remote system, or delete the local definition. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | When an existing administered subscription is restored during startup the existence of the subscription on the remote publisher is confirmed by sending a RENEW message. The remote system responded with a ResourceUnknownFault. The subscription will be automatically recreated. |
User response | The subscription will be automatically recreated, so no useraction is required. It may be worth investigating the remote system to determine why the subscription was lost. |
Problem | The WS-Topics specification defines the concept of extension topics, however these extensions are not supported by WebSphere Application Server. |
User response | The Administrator must modify the topic namespace document to remove use of extension topics and restart the server. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | The topic specified violates one or more of the conditions describing the correct structure of a topic in the specified dialect. This might be because the topic contains characters that are not permitted in this dialect, or not permitted in a particular position with respect to other characters. |
User response | This condition represents an application error. The application should be modified to use a valid topic syntax. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | The broker will only allow notify operations from administered subscriptions that are recognised by the broker, the broker will attempt to unsubscribe the subscription. |
User response | Ensure that the unsubscribe succeeds or that the notifying application ceases to notify. |
Problem | The broker will only allow notify operations from administered subscriptions that are recognised by the broker. |
User response | Ensure that the notifying application ceases to notify |
Problem | A pull point can only be used by a single subscription at a time. This exception is caused by trying to use a pull point that is already associated with an existing subscription. |
User response | When performing the subscribe operation ensure that the pull point specified is not in use by an existing subscription. |
Problem | A user is not authorized to send to the WPM topic space using the specified topic. |
User response | If the user should have authority to send messages on the given topic then update the users authorization rights for the topic on the given WPM topic space. |
Problem | A user is not authorized to subscribe to the WPM topic space using the specified topic expressions. |
User response | If the user should have authority to subscribe on the given topics then update the users authorization rights for the appropriate topics on the given WPM topic space. |
Problem | A subscription request was denied by the Notification Broker. |
User response | Examine any previous errors in the log for further information. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | The WS-Notification specification requires a valid subscription endpoint reference to be returned in the response to a Subscribe request. The specified application does not conform to the specification. |
User response | The administrator should locate the specified application and take steps to fix the application to be compliant with the WS-Notification specification. |
Problem | The topic namespace cannot be used until topic namespace instance documents have been parsed. This condition may be transient as it may occur if this operation was called before WS-Notification startup has completed. |
User response | Check that the server started successfully and resolve previous errors in the log. Retry the operation. |
Problem | The constructors for the AbsoluteOrRelativeTime class cannot be passed a null value. |
User response | Correct the application code that is calling the constructor, to make sure the value being used is not null. |
Problem | The value for the maximum number of messages to return cannot be negative. |
User response | Correct the application code that is setting this value to make sure the value is greater than or equal to 0. |
Problem | A failure occurred in the initialization of the TopicExpression class. |
User response | 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/. |
Problem | An exception occurred when an instance of the specified schema type or element was being deserialized from a SOAP message. |
User response | 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/. |
Problem | An exception occurred when an instance of the specified class was being serialized into a SOAP message. |
User response | 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/. |
Problem | An instance of the specified schema type or element could not be deserialized from a SOAP message because the instance contained no value. |
User response | 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/. |
Problem | An instance of the specified schema type or element could not be deserialized from a SOAP message because a child element was of the wrong form. |
User response | 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/. |
Problem | An instance of the specified schema type or element could not be deserialized from a SOAP message because the child element was encountered in an incorrect position based on the schema for the message. |
User response | 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/. |
Problem | The Message element in a NotificationMessage must have one and only one child element. |
User response | 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/. |
Problem | The Message element in a NotificationMessage must have one and only one child element. |
User response | 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/. |
Problem | An instance of the specified schema type or element could not be deserialized from a SOAP message because an unexpected element was encountered based on the schema for the message. |
User response | 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/. |
Problem | A NotificationMessage element must contain a Message element. |
User response | 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/. |
Problem | When deserializing a NotificationMessage, an element was encountered that is not allowed by the schema for the message. |
User response | 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/. |
Problem | An invalid value for an xsd:duration (relative time) was encountered. |
User response | Verify that application code is using valid duration values of the form PxYxMxDTxHxMxS where x is a numeric value. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | A Notify operation invocation failed. Previous messages in the log should indicate the cause of the failure. |
User response | Examine any previous errors in the log and retry the operation. |
Problem | The broker does not currently have a notification message stored for the requested topic. |
User response | No action required. This condition is permitted by the WS-Notification specification |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | The SetTerminationTime element in a SetTerminationTime request was missing or empty. |
User response | Verify that the application making the SetTerminationTime request is sending a SOAP message containing a valid SetTerminationTime element |
Problem | The SetTerminationTime element requires either a RequestedTerminationTime or RequestedLifetimeDuration element as child. The RequestedTerminationTime element may specify xsi:nil="true" |
User response | Supply a valid termination time value in the SOAP message. |
Problem | The element found was not expected. |
User response | Correct the application making the SetTerminationTime request to remove the specified element |
Problem | The termination time value must be specified |
User response | Retry the request supplying a termination time. |
Problem | The SetTerminationTime element in a SetTerminationTime request was missing or empty. |
User response | Verify that the application making the SetTerminationTime request is sending a SOAP message containing a valid SetTerminationTime element |
Problem | The SetTerminationTime element requires either a RequestedTerminationTime or RequestedLifetimeDuration element as child. The RequestedTerminationTime element may specify xsi:nil="true" |
User response | Supply a valid termination time value in the SOAP message. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | A register publisher operation failed. Previous messages in the log should indicate the cause of the failure. |
User response | Examine any previous errors in the log and retry the operation. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | The chosen filter type is not supported by the NotificationBroker so the request cannot be fulfilled. |
User response | Modify the application to avoid use of the unsupported filter type. |
Problem | The Administrator deleted a WSN topic namespace configuration record on which this resource depends, so it cannot be reconciled. |
User response | No action required. The failing resource will be deleted. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | An instance of the specified schema type failed to be deserialized from a SOAP message because the required element specified was not found. |
User response | Correct the application producing the SOAP message so that the xml conforms to the required schema. |
Problem | In order for JAX-RPC handlers to be used with outbound requests from a WS-Notification Service, the SIBWS application must be installed each bus member (server or cluster) for which a WS-Notification Service Point has been created. |
User response | Make sure that the SIBWS application has been installed on each bus member (server or cluster) for which a WS-Notification Service Point has been created. |
Problem | The pull points at the broker do not support notifications being sent to them. |
User response | Make sure that publisher applications are not addressing notifications to a pull point endpoint reference. |
Problem | Instances of the specified class must have a non null Dialect value set |
User response | Verify that the application code which created the instance of the class is setting a non null value for the Dialect. |
Problem | The specified schema type requires a Dialect attribute |
User response | Verify that the application producing the SOAP message is correctly configuring the Dialect attribute. |
Problem | A GetResourcePropty request was received which could not be processed. The name of the property requested was unknown to the Web service resource receiving the request. |
User response | Correct the application requesting the property to specify a valid property for the Web service resource. |
Problem | The policy specified in a subscribe request was not recognized by the producer or broker |
User response | Correct the subscribing application to send a request containing a supported policy |
Problem | In order to destroy a pull point, the request must be targetted at the endpoint reference for the pull point. |
User response | Verify that the application making the request is specifying a valid pull point endpoint reference. An endpoint reference for a pull point is returned from a CreatePullPoint operation request. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | The notification producer or broker receiving the subscription request does not support subscriptions which do not contain a filter. |
User response | Modify the subscribing application to specify a filter. |
Problem | An endpoint reference was encountered which did not contain an address. The address is a required field. |
User response | Verify that all applications subscribing to the broker are supplying a valid consumer reference |
Problem | The value of a WS-Notification Base Notification AbsoluteOrRelativeTimeType must be a valid xsd:dateTime or xsd:duration |
User response | Verify that applications sending the AbsoluteOrRelativeTimeType value are using a valid value |
Problem | A bus must be supplied as either a target object or a command parameter. |
User response | Specify either an existing bus as the target object, or the name for a new bus as a command parameter. |
Problem | A bus must be supplied as EITHER the target object OR as a command parameter, but not both. |
User response | Specify either an existing bus as the target object, or the name for a new bus as a command parameter. |
Problem | WS-Notification service names must be unique within a bus context. |
User response | Specify a WS-Notification service name that does not already exist on the target bus. |
Problem | WS-Notification service point names must be unique within each notification service. |
User response | Specify a WS-Notification service point name that does not already exist on the target notification service. |
Problem | WS-Notification topic namespace namespaces must be unique within each notification service. |
User response | Specify a WS-Notification topic namespace instance namespace that does not already exist on the target notification service. |
Problem | A cluster or a node and server must be supplied. |
User response | To specify a cluster endpoint, supply a cluster name but not a node and a server name. To specify a server endpoint, supply a node and a server name, but not a cluster name. |
Problem | The supplied endpoint does not exist. |
User response | Specify an existing endpoint using the cluster or node and server parameters. |
Problem | The channel number supplied is not a valid option. |
User response | To use channel 1, supply "1". To use channel 2, supply "2". |
Problem | An existing endpoint listener name or new endpoint listener data must be supplied. |
User response | To use an endpoint listener name, supply its name. If you are not sure whether a suitable endpoint listener exists, then specify a binding and (optionally) a channel, host and host port. |
Problem | The supplied endpoint listener does not exist. |
User response | Specify an existing endpoint listener that exists on the specified endpoint. |
Problem | The type supplied is not a valid type. |
User response | Specify either "BROKER", "SUB_MGR" or "PUB_REG_MGR". |
Problem | The specified bus parameter does not match the name of an SIBus configuration object. |
User response | Specify the name of an existing SIBus configuration object as the bus parameter. |
Problem | An illegal target and parameter combination was used. |
User response | Supply either a target WS-Notifcation OR bus and name parameters. |
Problem | The requested WS-Notification service could not be found. |
User response | Supply alternative bus and name parameters |
Problem | The requested WS-Notification service point could not be found. |
User response | Supply an alternative WS-Notification service target or an alternative name parameter |
Problem | An illegal target and parameter combination was supplied. |
User response | Supply either a target WS-Notifcation service and the name of a WS-Notifcation service point OR supply a WS-Notification service point target |
Problem | An illegal target object was supplied. Either a WS-Notification service or a WS-Notification service point is required |
User response | Supply either a WS-Notification service or a WS-Notification service point |
Problem | The requested WS-Notification administered subscriber could not be found. |
User response | Supply an alternative WS-Notification service point target or alternative endpoint, dialect, topic or namespace parameters |
Problem | An illegal target and parameter combination was supplied. |
User response | Supply either a target WS-Notifcation service point and endpoint, dialect, topic or namespace parameters OR supply a WS-Notification administered subscriber target |
Problem | An illegal target object was supplied. Either a WS-Notification service point or a WS-Notification administered subscriber is required |
User response | Supply either a WS-Notification service point or a WS-Notification administered subscriber |
Problem | The requested WS-Notification topic namespace could not be found. |
User response | Supply an alternative WS-Notification service target or alternative namespace parameter |
Problem | An illegal target and parameter combination was supplied. |
User response | Supply either a target WS-Notifcation service and namespace parameter OR supply a WS-Notification topic namespace target |
Problem | An illegal target object was supplied. Either a WS-Notification service or a WS-Notification topic namespace is required |
User response | Supply either a WS-Notification service or a WS-Notification topic namespace |
Problem | The requested WS-Notification topic document could not be found. |
User response | Supply an alternative WS-Notification topic namespace target or alternative url parameter |
Problem | An illegal target and parameter combination was supplied. |
User response | Supply either a target WS-Notifcation topic namespace and url parameter OR supply a WS-Notification topic document target |
Problem | An illegal target object was supplied. Either a WS-Notification topic namespace or a WS-Notification topic document is required |
User response | Supply either a WS-Notification topic namespace or a WS-Notification topic document |
Problem | An illegal message reliability parameter was supplied, the allowed values are "ASSURED_PERSISTENT", "RELIABLE_PERSISTENT", "RELIABLE_NONPERSISTENT", "EXPRESS_NONPERSISTENT" and "BEST_EFFORT_NONPERSISTENT" |
User response | Supply either a message reliability parameter of "ASSURED_PERSISTENT", "RELIABLE_PERSISTENT", "RELIABLE_NONPERSISTENT", "EXPRESS_NONPERSISTENT" or "BEST_EFFORT_NONPERSISTENT" |
Problem | The URL supplied for the topic namespace document is invalid. |
User response | Supply a valid URL to use for the topic namespace document. |
Problem | The host defined in the supplied URL for the topic namespace document is unknown. |
User response | Supply a URL containing a known host from which to retrieve a topic namespace document. |
Problem | It was not possible to open a connection to the topic namespace document defined by the supplied URL. |
User response | Supply a valid URL to use for the topic namespace document. |
Problem | An invalid topic namespace was supplied. |
User response | Supply a valid topic namespace. |
Problem | An invalid topic document was supplied. |
User response | Supply the URL for a valid topic document. |
Problem | The cluster supplied contains servers on nodes that are not the version required for WS-Notification configurations. |
User response | Supply a cluster containing servers that are only on nodes that are at least version 6.1. |
Problem | The node supplied is not the correct version required for WS-Notification configurations. |
User response | Supply a node that is at least version 6.1. |
Problem | The topic supplied is not compatible with the selected dialect. When using the SIMPLE dialect only root topics may be specified. When using the CONCRETE dialect wildcards may not be used. |
User response | Change the supplied topic or dialect so that they are compatible. |
Problem | If the message does not give sufficient information, check any previous messages for further information. |
User response | If you are not able to resolve the problem, ask your system administrator to help resolve the problem. |