CWSJN

CWSJN0001E: Unexpected implementation class received: {0}
CWSJN0002E: A start or stop event was driven for messaging engine {0} on bus {1} before it had been registered.
CWSJN0003E: An internal error occurred: {0}.
CWSJN0006I: The WS-Notification service {0} has successfully reconciled the configuration state on messaging engine {1} and is available for use.
CWSJN0007I: The WS-Notification service {0} has successfully created the configuration state on messaging engine {1} and is available for use.
CWSJN0008I: The WS-Notification service {0} on messaging engine {1} is no longer available for use because the messaging engine has been stopped.
CWSJN0009E: The WS-Notification service {0} on messaging engine {1} failed to start due to the following exception: {2}
CWSJN0011E: An internal error occurred: Unexpected configuration information was passed to the WS-Notification component. The data was: {0}.
CWSJN0013E: An internal error occurred: The configuration file {0} could not be located due to {1}.
CWSJN0015W: Custom property {0} on WSN Service {2} cannot be configured to the value {1}
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}.
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}.
CWSJN1003E: An illegal argument was passed to the Broker Service Handler in field ''{0}''. The argument was {1}.
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}
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}.
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}.
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}.
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}.
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}.
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}.
CWSJN1011W: An internal error occurred: An attempt was made to remove topic namespace document {0} but an error occurred. The exception was {1}.
CWSJN1012E: An illegal argument was passed to a TopicNamespaceImpl in field ''{0}''. The argument was {1}.
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}.
CWSJN1014E: An attempt to create a subscription failed due to {0}.
CWSJN1015E: An attempt to reconnect a persisted subscription failed due to {0}.
CWSJN1016E: An attempt to reconnect a persisted publisher registration failed due to {0}.
CWSJN1018E: An attempt to restore a persisted administered subscription failed due to {0}.
CWSJN1024E: An attempt was made to register a publisher on a topic {0} in a namespace {1} which has not been defined.
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}.
CWSJN1027E: No acknowledgement was received from a Servant Region when communicating with an external Web service.
CWSJN1028E: An internal error occurred: A response was received from a Servant Region but the response was not of the expected type: {0}.
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}.
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.
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.
CWSJN1032E: An internal error occurred: Unable to write publisher registration to the persistent message store due to {0}.
CWSJN1034E: An internal error occurred: Publisher registration version mis-match when restoring from the persistent message store. The version was {0}.
CWSJN1035E: An internal error occurred: An exception occurred destroying a publication registration. The exception was {0}.
CWSJN1036E: A request was issued using a publication registration with id {0}, but the publication registration does not exist.
CWSJN1037E: An internal error occurred: An exception occurred destroying a pull point. The exception was {0}.
CWSJN1038E: An internal error occurred: An exception occurred creating a pull point. The exception was {0}.
CWSJN1039E: A request was issued using a pull point with id {0}, but the pull point does not exist.
CWSJN1040E: An invalid termination time was specified: {0}.
CWSJN1041E: An illegal argument was passed to the Service Point in field ''{0}''. The argument was {1}.
CWSJN1042E: An attempt was made to terminate subscription {0} but this failed due to {1}.
CWSJN1043E: An attempt was made to resume subscription {0} but this failed due to {1}.
CWSJN1044E: A request was issued against a subscription with id {0}, but the subscription does not exist.
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}.
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.
CWSJN1047E: An internal error occurred: Subscription version mis-match when restoring from the persistent message store. The version was {0}.
CWSJN1048E: An illegal argument was passed to the Timer Services in field ''{0}''. The argument was {1}.
CWSJN1049E: The document contains a definition for the namespace ''{0}''. This cannot be applied to the namespace ''{1}''
CWSJN1050E: The instance document does not define a '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.
CWSJN1052E: An attempt was made to parse a topic namespace instance document but the parsing failed due to {0}
CWSJN1053E: An internal error occurred: No ''name'' attribute was found in the XML node {0}.
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.
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.
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.
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.
CWSJN1058E: An internal error occurred: Service point {0} already exists.
CWSJN1059E: An internal error occurred: Topic namespace {0} already exists.
CWSJN1060E: An attempt was made to reference a dynamic namespace, {0}, dynamic namespaces are not supported on this broker
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.
CWSJN1062E: The attempt to renew the administered subscription {0} was rejected with the following exception {1}
CWSJN1063W: Failed to delete subscription {0} from persistent state: {1}
CWSJN1064I: The remote subscription for administered subscription {0} was reported as unknown.
CWSJN1065E: An extension topic was found in a topic namespace document. Use of extension topics is not supported. The XML node is {0}.
CWSJN1066E: Failed to read data at version {0}, can support version {1}
CWSJN1067E: The syntax of the topic {0} is not valid for the topic dialect {1}
CWSJN1068E: The topic {0} could not be parsed due to an internal precondition failure
CWSJN1069E: An attempt was made to perform a notify operation using WSN Service {0} on topic {1} from an unregistered administered subscription {2}
CWSJN1070E: An attempt was made to perform a notify operation using WSN Service {0} on topic {1} from an unknown administered subscription
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}.
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}.
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}.
CWSJN1074E: An attempt to create a subscription failed because access was denied.
CWSJN1075E: An illegal argument was passed to the administered subscriber in field ''{0}''. The argument was {1}.
CWSJN1076E: An illegal argument was passed to the topic namespace document in field ''{0}''. The argument was {1}.
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}
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.
CWSJN1079E: An attempt to create a subscription failed due to a syntax error in a message content filter expression, with error {0}.
CWSJN5000E: The time value passed to constructor of AbsoluteOrRelativeTime cannot be null.
CWSJN5001E: The maximum number of messages to return for GetMessages cannot be less than 0.
CWSJN5002E: Invalid URI {0} when initializing Dialect constants
CWSJN5003E: Error deserializing {0} instance: {1}
CWSJN5004E: Error serializing {0} : {1}
CWSJN5005E: Error deserializing {0} instance: instance has no value
CWSJN5006E: Error deserializing {0} instance: unexpected Java class {1} encountered for child object
CWSJN5007E: Error deserializing {0} instance: child element {1} encountered out of sequence
CWSJN5008E: Error deserializing NotificationMessageHolderType type: Message element has no children
CWSJN5009E: Error deserializing NotificationMessageHolderType type: Message element has more than one child
CWSJN5010E: Error deserializing {0} instance: unexpected element {1} encountered
CWSJN5011E: Error deserializing NotificationMessageHolderType type: no value for Message element found
CWSJN5012E: Error deserializing NotificationMessageHolderType instance: unexpected Message element encountered
CWSJN5013E: Invalid duration string: {0}
CWSJN5014E: An endpoint reference failed to be created from the URI string {0} due to {1}.
CWSJN5015E: A filter instance {0} failed to be converted to an XML string due to {1}.
CWSJN5016E: A filter could not be converted to an XML string because it was null.
CWSJN5017E: An XML string {0} failed to be converted to a filter due to {1}.
CWSJN5018E: An endpoint reference instance {0} failed to be converted to an XML string due to {1}.
CWSJN5019E: An endpoint reference could not be converted to an XML string because it was null.
CWSJN5020E: An XML string {0} failed to be converted to an endpoint reference due to {1}.
CWSJN5021E: The raw format notification message cannot contain more than 1 child element.
CWSJN5022E: An exception occurred when deserializing the raw format notification message: {0}.
CWSJN5023E: An exception occurred when serializing the SOAP message: {0}.
CWSJN5024E: An error occurred when processing a Notify operation request from a client with IP address {0}. The notification messages array was null.
CWSJN5025E: An error occurred when processing a Notify operation request from a client with IP address {0}. The exception was {1}.
CWSJN5026E: There is no current message stored for the topic {0}
CWSJN5027E: An internal error occurred: Unable to retrieve the service point due to {0}.
CWSJN5028E: An internal error occurred: Unable to build SOAP response due to {0}.
CWSJN5029E: An internal error occurred: Unable to get the endpoint reference for the Notification Broker service due to {0}.
CWSJN5030E: An internal error occurred: Unable to notify a consumer at endpoint reference {0} due to {1}.
CWSJN5031E: An internal error occurred: Unable to notify a consumer using raw message format at endpoint reference {0} due to {1}.
CWSJN5032E: An internal error occurred: Unable to subscribe with remote publisher at endpoint reference {0} due to {1}.
CWSJN5033E: An internal error occurred: Unable to pause remote publisher at endpoint reference {0} due to {1}.
CWSJN5034E: An internal error occurred: Unable to resume remote publisher at endpoint reference {0} due to {1}.
CWSJN5035E: An internal error occurred: Unable to unsubscribe from remote publisher at endpoint reference {0} due to {1}.
CWSJN5036E: An internal error occurred: Unable to renew subscription with remote publisher at endpoint reference {0} due to {1}.
CWSJN5037E: An internal error occurred: Unable to create the outbound stub due to {0}.
CWSJN5038E: An internal error occurred: Unable to create the remote publisher stub due to {0}.
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.
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.
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.
CWSJN5042E: An internal error occurred: Failed to read WSDL from location {0} due to {1}.
CWSJN5043E: An internal error occurred: Failed to create WS-Notification outbound deployment due to {0}.
CWSJN5044E: An internal error occurred: JAX RPC Handler {0} has no class defined.
CWSJN5045E: An internal error occurred: JAX RPC Handler {0} in class {1} does not implement javax.xml.rpc.handler.Handler.
CWSJN5046E: An internal error occurred: JAX RPC Handler {0} in class {1} cannot be found. The exception was {2}.
CWSJN5047E: An internal error occurred: JAX RPC Handler list {0} is not defined.
CWSJN5048E: An internal error occurred: An exception occurred setting outbound security settings for {0} due to {1}.
CWSJN5049E: The SetTerminationTime request could not processed because the SetTerminationTime element was null
CWSJN5050E: The SetTerminationTime request did not contain a valid RequestedTerminationTime or RequestedLifetimeDuration element value
CWSJN5051E: The SetTerminationTime request contained an unexpected element: {0}.
CWSJN5052E: A null termination time was received in a Renew request.
CWSJN5053E: The SetTerminationTime request could not processed because the SetTerminationTime element was null
CWSJN5054E: The SetTerminationTime request did not contain a valid RequestedTerminationTime or RequestedLifetimeDuration element value
CWSJN5055E: It was not possible to find the broker service handler for inbound service {0} on messaging engine with the UUID {1} in bus {2}. This may be because the service provider is stopped or is being failed over.
CWSJN5056E: It was not possible to find the broker service handler for inbound service {0} on bus {1}. This may be because the service provider is stopped or is being failed over.
CWSJN5057E: An internal error occurred: Unable to find the service point for WS-Notification service {0} on bus {1} associated with inbound port {2}.
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.
CWSJN5059E: An internal error occurred: No MessageContext exists on this thread.
CWSJN5060E: An internal error occurred: Attributed URI has no URI value.
CWSJN5061E: An internal error occurred: Cannot process WSA action, no MessageContext value has been set.
CWSJN5062E: An internal error occurred: No WSA action header has been set in the SOAP message. The required value is {0}.
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}.
CWSJN5064E: An internal error occurred: An error occurred creating an instance of a WS-Notification service object. The exception was {0}.
CWSJN5065E: An internal error occurred: The WS-Notification dispatcher was unable to determine the service object.
CWSJN5066E: An internal error occurred: The WS-Notification dispatcher was unable to determine the service class.
CWSJN5067E: An internal error occurred: The WS-Notification dispatcher did not find an inbound port in the SOAP port.
CWSJN5068E: An error occurred when processing a register publisher operation. The exception was {0}.
CWSJN5069E: An error occurred when retrieving resource property {0}. The exception was {1}.
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.
CWSJN5071E: The specified filter type {0} is not supported.
CWSJN5072W: The resource with identifier {0} cannot be reconciled because a WSN topic namespace on which it depends has been deleted.
CWSJN5073E: A TopicExpression could not be converted to an XML string because it was null.
CWSJN5074E: A TopicExpression instance {0} failed to be converted to an XML string due to {1}.
CWSJN5075E: An XML string {0} failed to be converted to a TopicExpression due to {1}.
CWSJN5076E: An internal error occurred: An exception occurred when reading serialized TopicExpression data. The exception is {0}
CWSJN5077E: An internal error occurred: An exception occurred when reading serialized QueryExpression data. The exception is {0}
CWSJN5078E: An internal error occurred: An exception occurred when reading serialized Filter data. The exception is {0}
CWSJN5079E: Failed to serialize an instance of {0} into a SOAP message, the required minimum time value is null
CWSJN5080E: Failed to deserialize {0} instance: unexpected duplicate element {1} found in message
CWSJN5081E: Failed to deserialize {0} instance: element {1} has no value
CWSJN5082E: Failed to deserialize {0} instance: a required {1} element was not found
CWSJN5083E: The required application ClassLoader could not be found to load outbound JAX-RPC handlers for WS-Notification Service {0} on bus {1}
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.
CWSJN5085E: Failed to serialize {0}: the required Dialect value was null
CWSJN5086E: Failed to deserialize {0} instance: a required Dialect attribute value was not found
CWSJN5087E: A request was received for a resource property with name {0}. This resource property is not known.
CWSJN5088E: A subscribe request was received containing a policy with an unrecognized element: {0}
CWSJN5089E: A request to destroy a pull point was received containing no pull point id.
CWSJN5090E: Failed to serialize an instance of InvalidFilterFault into a SOAP message, unknown filter name value is null
CWSJN5091E: Failed to serialize an instance of UnrecognizedPolicyFault into a SOAP message, unrecognized policy name value is null
CWSJN5092E: Failed to serialize an instance of UnsupportedPolicyFault into a SOAP message, unsupported policy name value is null
CWSJN5093E: A subscribe request was received with no filter specified. The producer or broker does not support this.
CWSJN5094E: A subscribe request was received with no consumer reference specified.
CWSJN5095E: An endpoint reference specified for an outbound request did not contain an address.
CWSJN5096E: The value {0} is not valid for an instance of AbsoluteOrRelativeTimeType
CWSJN5097E: The specified message content filter dialect {0} is not supported.
CWSJN5098E: Invalid URI {0} when initializing Message Content Expression Dialect constant
CWSJN5099E: An endpoint reference failed to be created from the WSDL service {0} and port {1} due to {2}.
CWSJN5100E: A negative duration {0} is not valid for a termination time
CWSJN5101E: The topic expression {0} targets multiple topics. The message will not be processed further.
CWSJN6000E: A bus was not supplied.
CWSJN6001E: A bus was supplied as BOTH the target object and a command parameter.
CWSJN6002E: A WS-Notification service with the name ''{0}'' already exists on bus ''{1}''
CWSJN6003E: A WS-Notification service point with the name ''{0}'' already exists on service ''{1}''
CWSJN6004E: A WS-Notification topic namespace with the namespace ''{0}'' already exists on service ''{1}''
CWSJN6005E: Illegal endpoint parameter combination.
CWSJN6006E: Endpoint ''{0}'' does not exist.
CWSJN6008E: ''{0}'' is not a valid channel number.
CWSJN6009E: Illegal endpoint listener parameter combination.
CWSJN6010E: Endpoint listener ''{0}'' does not exist on endpoint ''{1}''.
CWSJN6011E: The type ''{0}'' is not valid
CWSJN6012E: The bus ''{0}'' could not be found
CWSJN6013E: A target WS-Notification service OR bus and name parameters must be supplied.
CWSJN6014E: The requested WS-Notification service could not be found.
CWSJN6015E: The requested WS-Notification service point could not be found.
CWSJN6016E: An illegal target and parameter combination was supplied.
CWSJN6017E: An illegal target object was supplied. Either a WS-Notification service or a WS-Notification service point is required
CWSJN6018E: The requested WS-Notification administered subscriber could not be found.
CWSJN6019E: An illegal target and parameter combination was supplied.
CWSJN6020E: An illegal target object was supplied. Either a WS-Notification service point or a WS-Notification administered subscriber is required
CWSJN6021E: The requested WS-Notification topic namespace could not be found.
CWSJN6022E: An illegal target and parameter combination was supplied.
CWSJN6023E: An illegal target object was supplied. Either a WS-Notification service or a WS-Notification topic namespace is required
CWSJN6024E: The requested WS-Notification topic document could not be found.
CWSJN6025E: An illegal target and parameter combination was supplied.
CWSJN6026E: An illegal target object was supplied. Either a WS-Notification topic namespace or a WS-Notification topic document is required
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)
CWSJN6028E: The dialect parameter {0} is not a valid option, the allowed values are "SIMPLE" (or "http://docs.oasis-open.org/wsn/t-1/TopicExpression/Simple"), "CONCRETE" (or "http://docs.oasis-open.org/wsn/t-1/TopicExpression/Concrete") and "FULL" (or "http://docs.oasis-open.org/wsn/t-1/TopicExpression/Full").
CWSJN6029E: This destination is reserved for use by WS-Notification service "{0}".
CWSJN6030E: The URL supplied for the topic namespace document is invalid.
CWSJN6031E: The host defined in the supplied URL for the topic namespace document is unknown.
CWSJN6032E: It was not possible to open a connection to the topic namespace document defined by the supplied URL.
CWSJN6033E: An invalid topic namespace was supplied: {0}
CWSJN6034E: The document supplied is not a valid topic document: {0}
CWSJN6035E: The cluster supplied contains servers on nodes that are not the version required for WS-Notification configurations.
CWSJN6036E: The node supplied is not the correct version required for WS-Notification configurations.
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.
CWSJN6038E: The value {0} is not valid for the type parameter. Valid values are V6.1 or V7.0.
CWSJN6039E: The following parameters must not be supplied if the type parameter is set to V6.1: jaxwsHandlerListName, queryWSDL.
CWSJN6040E: The following parameters must not be supplied if the type parameter is set to V7.0: jaxrpcHandlerListName, outboundSecurityConfigName, outboundSecurityRequestBindingName, outboundSecurityResponseBindingName.
CWSJN6041E: A WS-Notification service with the name "{0}" already exists at the current cell scope.
CWSJN6042E: The following parameters must not be supplied if the WSN Service target object has a type attribute of V6.1: transportURLRoot, transportSoapVersion, jaxwsHandlerListNB, jaxwsHandlerListSM, jaxwsHandlerListPRM.
CWSJN6043E: The following parameters must not be supplied if the WSN Service target object has a type attribute of V7.0: eplName, eplURLRoot, eplWSDLServingURLRoot.
CWSJN6044E: The command cannot be called on WSN Service "{0}" because its type attribute is set to V7.0.
CWSJN6045E: The command cannot be called on the supplied WSN Service Point, because its parent object WSN Service "{0}" is of type V7.0.
CWSJN6046E: The node supplied is not the correct version required for WS-Notification service point creation as the WS-N Service is of type V7.0.
CWSJN6047E: The cluster supplied contains servers on nodes that are not the version required for WS-Notification service point creation as the WS-N Service is of type V7.0.
CWSJN6048E: An illegal target was specified for service point installation. Node = ''{0}'', Server = ''{1}'', and Cluster = ''{2}''
CWSJN6049E: Unable to discover AppManagement MBean while processing application ''{0}''
CWSJN6050E: An illegal program state was encountered while installing application ''{0}''
CWSJN6051E: An internal error occurred: It was not possible to resolve handler list ''{0}'' from the config service while installing application ''{1}''.
CWSJN6052E: An internal error occurred: The installation of application ''{0}'' failed. The following status message was received from WebSphere application management when the failure occurred: ''{1}''
CWSJN6053E: An internal error occurred: The uninstallation of application ''{0}'' failed. The following status message was received from WebSphere application management when the failure occurred: ''{1}''
CWSJN6054E: An internal error occurred: It was not possible to discover an invoker for the WSN service with QName ''{0}'' and soap version ''{1}''
CWSJN6055E: The value "{0}" is not a valid URL value for the parameter transportURLRoot. The value must start with "http://" or "https://", and conform to standard URL syntax rules.
CWSJN6056E: The target object must be of type: "{0}".
CWSJN6057E: The handler name "{0}" does not exist as a JAXWSHandler object at cell scope.
CWSJN6058E: It was not possible to create an EndpointReference because of the following exception: {0}
CWSJN6059E: An attempt to generate a deployment descriptor for a new WSN service point failed because the WSN port type ''{0}'' was not recognized.
CWSJN6060E: It was not possible to create an IBMMessageFactory because the binding with ID ''{0}'' is not recognized.
CWSJN6061E: It was not possible to create a dispatch-based WSN client because the SOAP version ''{0}'' was not recognized.
CWSJN6062E: It was not possible to create a dispatch-based WSN client because the the URI scheme ''{0}'' was not recognized.
CWSJN6063E: A configuration directory for WSN service ''{0}'' in bus ''{1}'' could not be found.
CWSJN6064E: It was not possible to create the configuration directory for WSN service ''{0}'' in bus ''{1}''. It already exists.
CWSJN6065E: The NotificationBroker JAX-WS handler list ''{0}'' was specified for a WSN service but could not be resolved via the config service
CWSJN6066E: An unexpected error was encountered when processing operation ''{0}'' for the WS-Notification service with WSDL service name ''{1}'' and WSDL port name ''{2}''. Please contact the system administrator of the remote system for further information.
CWSJN6067E: Subscription was rejected because the consumer reference address ''{0}'' is the same as the NotificationBroker address: ''{1}''
CWSJN6068E: A configuration directory for bus ''{0}'' could not be found.
CWSJN6069E: This service is used by WS-Notification service "{0}". The destination specified should not be altered.
CWSJN9999E: {0}


Terms and conditions for information centers | Feedback

Last updated: June 12, 2013 12:15 PM EDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=com.ibm.ws.sib.wsn.CWSJNMessages.dita
File name: com.ibm.ws.sib.wsn.CWSJNMessages.html