WebSphere Process Server messages     Operating Systems: All supported

CWSJN

CWSJN0001E: Unexpected implementation class received: {0}
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/.
CWSJN0002E: A start or stop event was driven for messaging engine {0} on bus {1} before it had been registered.
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/.
CWSJN0003E: An internal error occurred: {0}.
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/.
CWSJN0006I: The WS-Notification service {0} has successfully reconciled the configuration state on messaging engine {1} and is available for use.
Problem WS-Notification requests can now be actioned by this WS-Notification service.
User response No action required.
CWSJN0007I: The WS-Notification service {0} has successfully created the configuration state on messaging engine {1} and is available for use.
Problem WS-Notification requests can now be actioned by this WS-Notification service.
User response No action required.
CWSJN0008I: The WS-Notification service {0} on messaging engine {1} is no longer available for use because the messaging engine has been stopped.
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.
CWSJN0009E: The WS-Notification service {0} on messaging engine {1} failed to start due to the following exception: {2}
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/.
CWSJN0011E: An internal error occurred: Unexpected configuration information was passed to the WS-Notification component. The data was: {0}.
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/.
CWSJN0013E: An internal error occurred: The configuration file {0} could not be located due to {1}.
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/.
CWSJN0015W: Custom property {0} on WSN Service {2} cannot be configured to the value {1}
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
CWSJN1001E: An attempt was made to unsubscribe from a remote NotificationProducer located with endpoint {0} but the operation could not be completed due to {1}.
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.
CWSJN1002W: An attempt was made to subscribe to a remote NotificationProducer located with endpoint {0} but the operation could not be completed. This operation will be retried automatically in {1} seconds. The operation failed due to {2}.
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.
CWSJN1003E: An illegal argument was passed to the Broker Service Handler in field ''{0}''. The argument was {1}.
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/.
CWSJN1004E: An attempt was made to perform a notify operation using WSN Service {0} on topic {1} but the broker is configured to require notification registration and no registration has been received for this topic. The producer''s endpoint reference was {2}. The IP address of the client was {3}
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.
CWSJN1005W: An attempt was made to subscribe to a remote NotificationProducer located with endpoint {0} but the subscribe failed due to a non-transient fault. This operation will not be retried. The operation failed due to {1}.
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.
CWSJN1006E: An attempt was made to perform a notify operation with topic expression {0} but this could not be completed as the topic dialect was not recognised. The producer''s endpoint reference was {1}. The IP address of the client was {2}. The exception was {3}.
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.
CWSJN1007E: An attempt was made to perform a notify operation with topic expression {0} but this could not be completed as the topic name was invalid with respect to the topic dialect. The producer''s endpoint reference was {1}. The IP address of the client was {2}. The exception was {3}.
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.
CWSJN1008E: An attempt was made to perform a notify operation with topic expression {0} but this could not be completed as the configuration of the topic namespace documents prevents this. The producer''s endpoint reference was {1}. The IP address of the client was {2}. The exception was {3}.
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.
CWSJN1009E: An attempt was made to perform a notify operation with topic expression {0} but this could not be completed as the configuration of the topic namespace documents prevents messages of this type. The producer''s endpoint reference was {1}.
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.
CWSJN1010E: An internal error occurred: An attempt was made to load topic namespace document {0} but the document could not be found. The exception was {1}.
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/.
CWSJN1011W: An internal error occurred: An attempt was made to remove topic namespace document {0} but an error occurred. The exception was {1}.
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/.
CWSJN1012E: An illegal argument was passed to a TopicNamespaceImpl in field ''{0}''. The argument was {1}.
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/.
CWSJN1013E: An attempt was made to create a subscription specifying to use a Pull Point with id {0} but the Pull Point does not exist. The exception was {1}.
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
CWSJN1014E: An attempt to create a subscription failed due to {0}.
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.
CWSJN1015E: An attempt to reconnect a persisted subscription failed due to {0}.
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/.
CWSJN1016E: An attempt to reconnect a persisted publisher registration failed due to {0}.
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/.
CWSJN1018E: An attempt to restore a persisted administered subscription failed due to {0}.
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/.
CWSJN1024E: An attempt was made to register a publisher on a topic {0} in a namespace {1} which has not been defined.
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.
CWSJN1026E: An internal error occurred: Data could not be sent to an external Web service as the Servant Region dispatcher could not deliver the request to an appropriate Servant due to {0}.
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/.
CWSJN1027E: No acknowledgement was received from a Servant Region when communicating with an external Web service.
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/.
CWSJN1028E: An internal error occurred: A response was received from a Servant Region but the response was not of the expected type: {0}.
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/.
CWSJN1029W: An attempt was made to perform an operation on a remote NotificationProducer located with endpoint {0} but the operation could not be completed. This operation will be retried automatically in {1} seconds. The operation failed due to {2}.
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.
CWSJN1030W: The topic ''{0}'' is not valid in namespace ''{1}'' because the topic node ''{2}'' is marked as final and does not declare ''{3}'' as a child.
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.
CWSJN1031W: The topic ''{0}'' is not valid in namespace ''{1}'' because the topic namespace is marked as final and does not declare ''{3}'' as a root child.
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.
CWSJN1032E: An internal error occurred: Unable to write publisher registration to the persistent message store due to {0}.
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/.
CWSJN1034E: An internal error occurred: Publisher registration version mis-match when restoring from the persistent message store. The version was {0}.
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/.
CWSJN1035E: An internal error occurred: An exception occurred destroying a publication registration. The exception was {0}.
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/.
CWSJN1036E: A request was issued using a publication registration with id {0}, but the publication registration does not exist.
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.
CWSJN1037E: An internal error occurred: An exception occurred destroying a pull point. The exception was {0}.
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/.
CWSJN1038E: An internal error occurred: An exception occurred creating a pull point. The exception was {0}.
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/.
CWSJN1039E: A request was issued using a publication registration with id {0}, but the publication registration does not exist.
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.
CWSJN1040E: An invalid termination time was specified: {0}.
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.
CWSJN1041E: An illegal argument was passed to the Service Point in field ''{0}''. The argument was {1}.
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/.
CWSJN1042E: An attempt was made to terminate subscription {0} but this failed due to {1}.
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.
CWSJN1043E: An attempt was made to resume subscription {0} but this failed due to {1}.
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.
CWSJN1044E: A request was issued against a subscription with id {0}, but the subscription does not exist.
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.
CWSJN1045W: An attempt was made to deliver a message to an external Web service that was received under subscription {0} but the operation failed due to {1}.
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.
CWSJN1046W: A message was received on a topic space that matched a subscription {0}. However, the message type {1} was not suitable for a Web service application and has not been sent.
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.
CWSJN1047E: An internal error occurred: Subscription version mis-match when restoring from the persistent message store. The version was {0}.
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/.
CWSJN1048E: An illegal argument was passed to the Timer Services in field ''{0}''. The argument was {1}.
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/.
CWSJN1049E: The document contains a definition for the namespace ''{0}''. This cannot be applied to the namespace ''{1}''
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.
CWSJN1050E: The instance document does not define a 'targetNamespace' attribute.
Problem The 'targetNamespace' parameter is mandatory in a topic namespace instance configuation document.
User response Ensure the document contains a valid 'targetNamespace' attribute.
CWSJN1051E: An attempt was made to parse a topic namespace instance document but the document does not appear to be a valid instance document.
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.
CWSJN1052E: An attempt was made to parse a topic namespace instance document but the parsing failed due to {0}
Problem The instance document cannot be parsed.
User response Ensure the document is a valid topic namespace instance document.
CWSJN1053E: An internal error occurred: No ''name'' attribute was found in the XML node {0}.
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/.
CWSJN1054W: An attempt was made to perform an operation on topic space {0} but the topic namespace has been marked ''inactive'' due to errors processing one or more topic namespace documents.
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.
CWSJN1055E: An attempt was made to apply an additional topic namespace instance document to namespace {0} but the ''final'' attribute on the entire namespace conflicts with other documents that have already been applied.
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.
CWSJN1056E: An attempt was made to apply an additional topic namespace instance document to namespace {0} but the ''final'' attribute on node {1} conflicts with other documents that have already been applied.
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.
CWSJN1057E: An attempt was made to apply an additional topic namespace instance document to the namespace but the ''final'' attribute on node {0} conflicts with other documents that have already been applied.
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.
CWSJN1058E: An internal error occurred: Service point {0} already exists.
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/.
CWSJN1059E: An internal error occurred: Topic namespace {0} already exists.
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/.
CWSJN1060E: An attempt was made to reference a dynamic namespace, {0}, dynamic namespaces are not supported on this broker
Problem The broker is not configured to support dynamic namespaces.
User response Register the namespace with the broker or enable dynamic namespaces.
CWSJN1061E: An attempt was made to perform an operation with topic expression {0} but this could not be completed as the configuration of the topic namespace documents prevent this topic.
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.
CWSJN1062E: The attempt to renew the administered subscription {0} was rejected with the following exception {1}
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.
CWSJN1063W: Failed to delete subscription {0} from persistent state: {1}
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/.
CWSJN1064I: The remote subscription for administered subscription {0} was reported as unknown.
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.
CWSJN1065E: An extension topic was found in a topic namespace document. Use of extension topics is not supported. The XML node is {0}.
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.
CWSJN1066E: Failed to read data at version {0}, can support version {1}
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/.
CWSJN1067E: The syntax of the topic {0} is not valid for the topic dialect {1}
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.
CWSJN1068E: The topic {0} could not be parsed due to an internal precondition failure
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/.
CWSJN1069E: An attempt was made to perform a notify operation using WSN Service {0} on topic {1} from an unregistered administered subscription {2}
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.
CWSJN1070E: An attempt was made to perform a notify operation using WSN Service {0} on topic {1} from an unknown administered subscription
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
CWSJN1071E: An attempt was made to perform a subscribe operation specifying a pull point with id {0} that is already in use by another subscription. The subscription that is already associated is {1}.
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.
CWSJN1072E: An attempt was made to perform a notify operation on WPM topic space {0} and topic {1} under username {2} but this could not be completed as the user is not authorized to send to that WPM topic space using the specified topic. The producer''s endpoint reference was {3}. The exception was {4}.
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.
CWSJN1073E: An attempt was made to create a subscription on WPM topic space {0} under username {1} but this could not be completed as the user is not authorized to subscribe to that WPM topic space using the specified topic expressions. The consumer''s endpoint reference was {2}. The exception was {3}.
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.
CWSJN1074E: An attempt to create a subscription failed because access was denied.
Problem A subscription request was denied by the Notification Broker.
User response Examine any previous errors in the log for further information.
CWSJN1075E: An illegal argument was passed to the administered subscriber in field ''{0}''. The argument was {1}.
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/.
CWSJN1076E: An illegal argument was passed to the topic namespace document in field ''{0}''. The argument was {1}.
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/.
CWSJN1077E: A request to register a demand based publisher has failed because the publisher returned a null subscription reference from its Subscribe operation. The remote web service is found at the endpoint {0}
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.
CWSJN1078W: An attempt was made to perform an operation on topic space {0} but the topic namespace has been marked ''inactive'' as one or more topic namespace documents have yet to be parsed.
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.
CWSJN5000E: The time value passed to constructor of AbsoluteOrRelativeTime cannot be null.
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.
CWSJN5001E: The maximum number of messages to return for GetMessages cannot be less than 0.
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.
CWSJN5002E: Invalid URI {0} when initializing Dialect constants
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/.
CWSJN5003E: Error deserializing {0} instance: {1}
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/.
CWSJN5004E: Error serializing {0} : {1}
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/.
CWSJN5005E: Error deserializing {0} instance: instance has no value
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/.
CWSJN5006E: Error deserializing {0} instance: unexpected Java class {1} encountered for child object
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/.
CWSJN5007E: Error deserializing {0} instance: child element {1} encountered out of sequence
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/.
CWSJN5008E: Error deserializing NotificationMessageHolderType type: Message element has no children
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/.
CWSJN5009E: Error deserializing NotificationMessageHolderType type: Message element has more than one child
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/.
CWSJN5010E: Error deserializing {0} instance: unexpected element {1} encountered
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/.
CWSJN5011E: Error deserializing NotificationMessageHolderType type: no value for Message element found
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/.
CWSJN5012E: Error deserializing NotificationMessageHolderType instance: unexpected Message element encountered
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/.
CWSJN5013E: Invalid duration string: {0}
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.
CWSJN5014E: An endpoint reference failed to be created from the URI string {0} due to {1}.
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/.
CWSJN5015E: A filter instance {0} failed to be converted to an XML string due to {1}.
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/.
CWSJN5016E: A filter could not be converted to an XML string because it was null.
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/.
CWSJN5017E: An XML string {0} failed to be converted to a filter due to {1}.
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/.
CWSJN5018E: An endpoint reference instance {0} failed to be converted to an XML string due to {1}.
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/.
CWSJN5019E: An endpoint reference could not be converted to an XML string because it was null.
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/.
CWSJN5020E: An XML string {0} failed to be converted to an endpoint reference due to {1}.
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/.
CWSJN5021E: The raw format notification message cannot contain more than 1 child element.
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/.
CWSJN5022E: An exception occurred when deserializing the raw format notification message: {0}.
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/.
CWSJN5023E: An exception occurred when serializing the SOAP message: {0}.
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/.
CWSJN5024E: An error occurred when processing a Notify operation request from a client with IP address {0}. The notification messages array was null.
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/.
CWSJN5025E: An error occurred when processing a Notify operation request from a client with IP address {0}. The exception was {1}.
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.
CWSJN5026E: The is no current message stored for the topic {0}
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
CWSJN5027E: An internal error occurred: Unable to retrieve the service point due to {0}.
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/.
CWSJN5028E: An internal error occurred: Unable to build SOAP response due to {0}.
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/.
CWSJN5029E: An internal error occurred: Unable to get the endpoint reference for the Notification Broker service due to {0}.
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/.
CWSJN5030E: An internal error occurred: Unable to notify a consumer at endpoint reference {0} due to {1}.
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/.
CWSJN5031E: An internal error occurred: Unable to notify a consumer using raw message format at endpoint reference {0} due to {1}.
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/.
CWSJN5032E: An internal error occurred: Unable to subscribe with remote publisher at endpoint reference {0} due to {1}.
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/.
CWSJN5033E: An internal error occurred: Unable to pause remote publisher at endpoint reference {0} due to {1}.
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/.
CWSJN5034E: An internal error occurred: Unable to resume remote publisher at endpoint reference {0} due to {1}.
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/.
CWSJN5035E: An internal error occurred: Unable to unsubscribe from remote publisher at endpoint reference {0} due to {1}.
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/.
CWSJN5036E: An internal error occurred: Unable to renew subscription with remote publisher at endpoint reference {0} due to {1}.
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/.
CWSJN5037E: An internal error occurred: Unable to create the outbound stub due to {0}.
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/.
CWSJN5038E: An internal error occurred: Unable to create the remote publisher stub due to {0}.
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/.
CWSJN5039E: An internal error occurred: Failed to create endpoint reference for the NotificationBroker service as the service point {0} for service {1} could not be found.
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/.
CWSJN5040E: An internal error occurred: Failed to create endpoint reference for the NotificationBroker service because the inbound service {0} on bus {1} could not be found.
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/.
CWSJN5041E: An internal error occurred: Failed to create endpoint reference for the NotificationBroker service because the inbound port {0} for inbound service {1} on bus {2} could not be found.
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/.
CWSJN5042E: An internal error occurred: Failed to read WSDL from location {0} due to {1}.
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/.
CWSJN5043E: An internal error occurred: Failed to create WS-Notification outbound deployment due to {0}.
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/.
CWSJN5044E: An internal error occurred: JAX RPC Handler {0} has no class defined.
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/.
CWSJN5045E: An internal error occurred: JAX RPC Handler {0} in class {1} does not implement javax.xml.rpc.handler.Handler.
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/.
CWSJN5046E: An internal error occurred: JAX RPC Handler {0} in class {1} cannot be found. The exception was {2}.
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/.
CWSJN5047E: An internal error occurred: JAX RPC Handler list {0} is not defined.
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/.
CWSJN5048E: An internal error occurred: An exception occurred setting outbound security settings for {0} due to {1}.
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/.
CWSJN5049E: The SetTerminationTime request could not processed because the SetTerminationTime element was null
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
CWSJN5050E: The SetTerminationTime request did not contain a valid RequestedTerminationTime or RequestedLifetimeDuration element value
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.
CWSJN5051E: The SetTerminationTime request contained an unexpected element: {0}.
Problem The element found was not expected.
User response Correct the application making the SetTerminationTime request to remove the specified element
CWSJN5052E: A null termination time was received in a Renew request.
Problem The termination time value must be specified
User response Retry the request supplying a termination time.
CWSJN5053E: The SetTerminationTime request could not processed because the SetTerminationTime element was null
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
CWSJN5054E: The SetTerminationTime request did not contain a valid RequestedTerminationTime or RequestedLifetimeDuration element value
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.
CWSJN5056E: An internal error occurred: Unable to find the broker service handler for inbound service {0} on bus {1}.
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/.
CWSJN5057E: An internal error occurred: Unable to find the service point for WS-Notification service {0} on bus {1} associated with inbound port {2}.
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/.
CWSJN5058E: An internal error occurred: Unable to find the inbound service {0} on bus {1}. The creation of the endpoint reference is not possible without the inbound service.
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/.
CWSJN5059E: An internal error occurred: No MessageContext exists on this thread.
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/.
CWSJN5060E: An internal error occurred: Attributed URI has no URI 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/.
CWSJN5061E: An internal error occurred: Cannot process WSA action, no MessageContext value has been set.
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/.
CWSJN5062E: An internal error occurred: No WSA action header has been set in the SOAP message. The required value is {0}.
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/.
CWSJN5063E: An internal error occurred: An invalid WSA action value was received when invoking operation {0}. The value received was {1}. The required value was {2}.
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/.
CWSJN5064E: An internal error occurred: An error occurred creating an instance of a WS-Notification service object. The exception was {0}.
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/.
CWSJN5065E: An internal error occurred: The WS-Notification dispatcher was unable to determine the service object.
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/.
CWSJN5066E: An internal error occurred: The WS-Notification dispatcher was unable to determine the service class.
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/.
CWSJN5067E: An internal error occurred: The WS-Notification dispatcher did not find an inbound port in the SOAP port.
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/.
CWSJN5068E: An error occurred when processing a register publisher operation. The exception was {0}.
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.
CWSJN5069E: An error occurred when retrieving resource property {0}. The exception was {1}.
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/.
CWSJN5070E: An internal error occurred: Unable to find the inbound port {0} for inbound service {1} on bus {2}. The creation of the endpoint reference is not possible without the inbound port.
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/.
CWSJN5071E: The specified filter type {0} is not supported.
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.
CWSJN5072W: The resource with identifier {0} cannot be reconciled because a WSN topic namespace on which it depends has been deleted.
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.
CWSJN5073E: A TopicExpression could not be converted to an XML string because it was null.
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/.
CWSJN5074E: A TopicExpression instance {0} failed to be converted to an XML string due to {1}.
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/.
CWSJN5075E: An XML string {0} failed to be converted to a TopicExpression due to {1}.
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/.
CWSJN5076E: An internal error occurred: An exception occurred when reading serialized TopicExpression data. The exception is {0}
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/.
CWSJN5077E: An internal error occurred: An exception occurred when reading serialized QueryExpression data. The exception is {0}
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/.
CWSJN5078E: An internal error occurred: An exception occurred when reading serialized Filter data. The exception is {0}
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/.
CWSJN5079E: Failed to serialize an instance of {0} into a SOAP message, the required minimum time value is null
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/.
CWSJN5080E: Failed to deserialize {0} instance: unexpected duplicate element {1} found in 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/.
CWSJN5081E: Failed to deserialize {0} instance: element {1} has no 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/.
CWSJN5082E: Failed to deserialize {0} instance: a required {1} element was not found
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.
CWSJN5083E: The required application ClassLoader could not be found to load outbound JAX-RPC handlers for WS-Notification Service {0} on bus {1}
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.
CWSJN5084E: A Notify operation request was received at a pull point {0} from a client with IP address {1}. The pull point does not support the receipt of notification messages.
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.
CWSJN5085E: Failed to serialize {0}: the required Dialect value was null
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.
CWSJN5086E: Failed to deserialize {0} instance: a required Dialect attribute value was not found
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.
CWSJN5087E: A request was received for a resource property with name {0}. This resource property is not known.
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.
CWSJN5088E: A subscribe request was received containing a policy with an unrecognized element: {0}
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
CWSJN5089E: A request to destroy a pull point was received containing no pull point id.
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.
CWSJN5090E: Failed to serialize an instance of InvalidFilterFault into a SOAP message, unknown filter name value is null
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/.
CWSJN5091E: Failed to serialize an instance of UnrecognizedPolicyFault into a SOAP message, unrecognized policy name value is null
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/.
CWSJN5092E: Failed to serialize an instance of UnsupportedPolicyFault into a SOAP message, unsupported policy name value is null
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/.
CWSJN5093E: A subscribe request was received with no filter specified. The producer or broker does not support this.
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.
CWSJN5095E: An endpoint reference specified for an outbound request did not contain an address.
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
CWSJN5096E: The value {0} is not valid for an instance of AbsoluteOrRelativeTimeType
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
CWSJN6000E: A bus was not supplied.
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.
CWSJN6001E: A bus was supplied as BOTH the target object and 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.
CWSJN6002E: A WS-Notification service with the name ''{0}'' already exists on bus ''{1}''
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.
CWSJN6003E: A WS-Notification service point with the name ''{0}'' already exists on service ''{1}''
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.
CWSJN6004E: A WS-Notification topic namespace with the namespace ''{0}'' already exists on service ''{1}''
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.
CWSJN6005E: Illegal endpoint parameter combination.
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.
CWSJN6006E: Endpoint ''{0}'' does not exist.
Problem The supplied endpoint does not exist.
User response Specify an existing endpoint using the cluster or node and server parameters.
CWSJN6008E: ''{0}'' is not a valid channel number.
Problem The channel number supplied is not a valid option.
User response To use channel 1, supply "1". To use channel 2, supply "2".
CWSJN6009E: Illegal endpoint listener parameter combination.
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.
CWSJN6010E: Endpoint listener ''{0}'' does not exist on endpoint ''{1}''.
Problem The supplied endpoint listener does not exist.
User response Specify an existing endpoint listener that exists on the specified endpoint.
CWSJN6011E: The type ''{0}'' is not valid
Problem The type supplied is not a valid type.
User response Specify either "BROKER", "SUB_MGR" or "PUB_REG_MGR".
CWSJN6012E: The bus ''{0}'' could not be found
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.
CWSJN6013E: A target WS-Notification service OR bus and name parameters must be supplied.
Problem An illegal target and parameter combination was used.
User response Supply either a target WS-Notifcation OR bus and name parameters.
CWSJN6014E: The requested WS-Notification service could not be found.
Problem The requested WS-Notification service could not be found.
User response Supply alternative bus and name parameters
CWSJN6015E: The requested WS-Notification service point could not be found.
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
CWSJN6016E: An illegal target and parameter combination was supplied.
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
CWSJN6017E: An illegal target object was supplied. Either a WS-Notification service or a WS-Notification service point is required
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
CWSJN6018E: The requested WS-Notification administered subscriber could not be found.
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
CWSJN6019E: An illegal target and parameter combination was supplied.
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
CWSJN6020E: An illegal target object was supplied. Either a WS-Notification service point or a WS-Notification administered subscriber is required
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
CWSJN6021E: The requested WS-Notification topic namespace could not be found.
Problem The requested WS-Notification topic namespace could not be found.
User response Supply an alternative WS-Notification service target or alternative namespace parameter
CWSJN6022E: An illegal target and parameter combination was supplied.
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
CWSJN6023E: An illegal target object was supplied. Either a WS-Notification service or a WS-Notification topic namespace is required
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
CWSJN6024E: The requested WS-Notification topic document could not be found.
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
CWSJN6025E: An illegal target and parameter combination was supplied.
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
CWSJN6026E: An illegal target object was supplied. Either a WS-Notification topic namespace or a WS-Notification topic document is required
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
CWSJN6027E: The reliability parameter {0} is not allowed ("ASSURED_PERSISTENT", "RELIABLE_PERSISTENT", "RELIABLE_NONPERSISTENT", "EXPRESS_NONPERSISTENT" and "BEST_EFFORT_NONPERSISTENT" are the only valid options)
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"
CWSJN6030E: The URL supplied for the topic namespace document is invalid.
Problem The URL supplied for the topic namespace document is invalid.
User response Supply a valid URL to use for the topic namespace document.
CWSJN6031E: The host defined in the supplied URL for the topic namespace document is unknown.
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.
CWSJN6032E: It was not possible to open a connection to the topic namespace document defined by the supplied URL.
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.
CWSJN6033E: An invalid topic namespace was supplied: {0}
Problem An invalid topic namespace was supplied.
User response Supply a valid topic namespace.
CWSJN6034E: The document supplied is not a valid topic document: {0}
Problem An invalid topic document was supplied.
User response Supply the URL for a valid topic document.
CWSJN6035E: The cluster supplied contains servers on nodes that are not the version required for WS-Notification configurations.
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.
CWSJN6036E: The node supplied is not the correct version required for WS-Notification configurations.
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.
CWSJN6037E: 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.
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.
CWSJN9999E: {0}
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.
Reference topic    

Terms of Use | Feedback

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

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