WebSphere Application Server messages
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS


CWSJA

CWSJA0000E: Bus "{0}" already exists.
Explanation Bus names must be unique within the administrative domain.
Action Specify a unique bus name that is not already in existence within the administrative domain.
CWSJA0001E: Bus "{0}" not found.
Explanation The specified bus name could not be located within the administrative domain.
Action Make sure that the bus name specified is a valid bus name for an existing bus.
CWSJA0002E: Multiple instances of bus "{0}" found.
Explanation Only one instance of a bus should exist with the name specified, yet more than one instance has been located.
Action Make sure that bus names are unique within the administrative domain.
CWSJA0003E: Bus member "{0}" already exists.
Explanation An attempt has been made to add a server to a bus of which it is already a member.
Action Do not attempt to add a bus member if the server in question is already a member.
CWSJA0004E: Messaging engine "{0}" already exists.
Explanation The messaging engine specified already exists on the server.
Action Ensure that the messaging engine details are not identical to that of another messaging engine on the server.
CWSJA0005E: Unable to create bus member "{0}".
Explanation An exception was generated attempting to create a bus member with the configuration data provided.
Action Ensure that all configuration data for the bus member is valid.
CWSJA0006E: Destination type "{0}" is not supported by this command.
Explanation An Incorrect destination type has been specified.
Action Make sure the destination type specified is a valid destination type.
CWSJA0007E: Incorrect parameter combination supplied : node name = "{0}", server name = "{1}", cluster name = "{2}", WebSphere MQ server name = "{3}".
Explanation The parameters supplied do not provide a valid bus member configuration.
Action To correctly identify a bus member, specify node name and server name, or cluster name, or WebSphere MQ server name.
CWSJA0008E: Scope specification is not valid.
Explanation The details specified do not represent a valid scope specification.
Action Make sure that valid node name, server name and cluster name details are used to represent the scope.
CWSJA0009E: Destination "{0}" already exists.
Explanation The destination specified already exists on the bus.
Action Ensure that destinations on a bus have unique names.
CWSJA0010E: "{0}" must be set to create an alias destination.
Explanation An attempt has been made to create an alias destination without sufficient configuration detail.
Action Make sure that an Alias parameter is specified when creating an alias destination.
CWSJA0011E: "{0}" must be set to create a foreign destination.
Explanation An attempt has been made to create an foreign destination without sufficient configuration detail.
Action Make sure that a foreign parameter is specified when creating an foreign destination.
CWSJA0012E: The messaging engine "{0}" does not exist at scope "{1}" for bus "{2}".
Explanation The operation could not be invoked because the given messaging engine does not exist for the given bus at the specified scope.
Action Ensure that a correct messaging engine name and scope are specified.
CWSJA0013E: Multiple messaging engines were found.
Explanation Multiple messaging engines have been found matching the configuration data provided.
Action Ensure that messaging engines are unique within an administrative domain.
CWSJA0015E: SIB JDBC provider not found.
Explanation An attempt has been made to locate a SIB JDBC provider within the scope provider, but none was found.
Action Ensure that there is a SIB JDBC provider available within the administrative domain.
CWSJA0016E: Unable to create data source.
Explanation An exception occurred creating a data source with the configuration data provided.
Action Make sure that the configuration data provided to create a data source is valid.
CWSJA0017E: Unable to create resource property set.
Explanation An exception occurred creating a resource property set with the configuration data provided.
Action Make sure that the configuration data provided to create a resource property set is valid.
CWSJA0018E: Bus member supplied is not a member of the specified bus.
Explanation An exception occurred dealing with a bus member which is not a member of the specified bus.
Action Ensure that the bus member supplied is a member of the specified bus.
CWSJA0019E: Unable to create messaging engine.
Explanation An exception occurred creating a messaging engine with the configuration data provided.
Action Make sure that the configuration data provided to create a messaging engine is valid.
CWSJA0020E: Unable to create data store.
Explanation An exception occurred creating a data store with the configuration data provided.
Action Make sure that the configuration data provided to create a data store is valid.
CWSJA0021E: The bus with name "{0}" contains invalid characters
Explanation The specified bus contained illegal characters. Bus names cannot contain any of the following characters \/,#$@:;"*?<>|=+&%' or start with _ or . or contain ]]> .
Action Ensure that a valid bus name is being specified upon bus creation.
CWSJA0022E: Not allowed to delete a bus called "{0}".
Explanation An exception has occurred attempting to delete a bus with the name specified.
Action Ensure that a valid bus name is being specified upon bus deletion.
CWSJA0023E: Bus member not found.
Explanation The bus member specified could not be located within the administrative domain.
Action Ensure that a valid bus member is being located.
CWSJA0024E: Multiple bus members found.
Explanation Only one instance of a bus member should exist within the scope specified, yet more than one instance has been located.
Action Ensure that bus members have unique configuration data within an administrative domain.
CWSJA0025E: Messaging engine already defined for this bus member.
Explanation A messaging engine already exists with the configuration data supplied.
Action Ensure that unique configuration data is supplied when creating a messaging engine.
CWSJA0026E: Not allowed to delete "{0}" because it is a system destination.
Explanation An exception has occurred attempting to delete a destination with the name specified.
Action Ensure that a valid destination name is being specified upon destination deletion.
CWSJA0027E: Destination {0} not found on bus {1}.
Explanation An exception occurred attempting to locate the specified destination.
Action Ensure that the destination being located exists within the administrative domain.
CWSJA0028E: Multiple destinations found.
Explanation Only one instance of a destination should exist within the scope specified, yet more than one instance has been located.
Action Ensure that destinations have unique configuration data within an administrative domain.
CWSJA0029E: Failed to find bus. More than one bus found with duplicate UUID.
Explanation An exception occurred due to multiple buses having identical UUIDs.
Action Ensure that each bus in an administrative domain has a unique UUID.
CWSJA0030E: Failed to find Bus with UUID "{0}".
Explanation The UUID specified does not belong to a bus in the administrative domain.
Action Ensure that the UUID specified belongs to a valid bus.
CWSJA0031E: No messaging engine names available for cluster.
Explanation A suitable messaging engine name could not be created.
Action Try specifying different configuration data when creating the messaging engine.
CWSJA0032E: Failed to find destination. More than one destination with duplicate UUID.
Explanation An exception occurred due to multiple destinations having identical UUIDs.
Action Ensure that each destination in an administrative domain has a unique UUID.
CWSJA0033E: Server supplied does not have a SIB Service.
Explanation An exception occurred retrieving the SIB Services for the messaging server.
Action Ensure that a SIB Service exists for the messaging server.
CWSJA0034E: Failed to find destination "{1}" on bus "{0}".
Explanation The named destination could not be located on the named bus within the administrative domain.
Action Make sure that the named destination exists on the named bus.
CWSJA0036E: Required value not supplied for parameter "{1}" of command "{0}".
Explanation Either the specified parameter was not supplied, or no value was supplied for it.
Action Run the command again, this time supplying the missing parameter value.
CWSJA0037E: Incorrect value "{2}" for parameter "{1}" of command "{0}".
Explanation The value supplied for the specified parameter of the specified command was not valid.
Action Run the command again, this time supply a valid value.
CWSJA0038E: Required value not supplied for parameter "{2}" of step "{1}" of command "{0}".
Explanation Either the specified parameter was not supplied for the specified step, or no value was supplied for it.
Action Supply the missing parameter value for the specified step.
CWSJA0039E: Failed to determine values for "reliability" and "maxReliability".
Explanation An internal error occurred while trying to determine values for "reliability" and "maxReliability".
Action Report this problem to your system administrator.
CWSJA0040E: The value supplied for "reliability" is greater than the value supplied for "maxReliability".
Explanation The value supplied for "reliability" should be less than or equal to the value supplied for "maxReliability".
Action Report this problem to your system administrator.
CWSJA0041E: Value for parameter "{0}" not recognised.
Explanation The value supplied for the specified parameter was not recognized.
Action Run the command again, this time supplying a valid value.
CWSJA0042E: Not allowed to create a SIBDestination called "{0}"
Explanation The destination name supplied to the createSIBDestination command is not valid.
Action Supply a valid destination name.
CWSJA0043E: The value of {2} is not valid for parameter {1} when destination type is {0}.
Explanation The value supplied for the specified parameter was not valid.
Action Run the command again, this time supply a valid value.
CWSJA0044E: Node, server, WebSphere MQ Server and/or cluster supplied when type is "WebServices".
Explanation The node, server and/or cluster parameters should not be specified when type is "WebServices".
Action Run the command again, this time supply a valid combination of parameters.
CWSJA0045E: An internal error occurred while validating reliability and maxReliability.
Explanation An internal error occurred while validating reliability and maxReliability.
Action Report this problem to your system administrator.
CWSJA0047E: Can not have a reply destination bus with out a reply destination name.
Explanation A reply destination can not be specified with out a reply destination name. The reply destination object will be removed
Action If a reply destination is required specify at least the reply destination name.
CWSJA0049E: WebSphere MQ server "{0}" is already a member of bus "{1}".
Explanation An attempt has been made to add an MQ server to a bus of which it is already a member.
Action Do not attempt to add an WebSphere MQ server to a bus of which it is already a member.
CWSJA0050E: Unable to create WebSphere MQ Server Bus Member.
Explanation An exception occurred creating a WebSphere MQ server Bus Member with the configuration data provided.
Action Make sure that the configuration data provided to create a WebSphere MQ server Bus Member is valid.
CWSJA0051E: No bus member target found for WebSphere MQ server "{0}" on bus "{1}".
Explanation When added to a bus, a WebSphere MQ server should have one bus member target. None was found.
Action Report this problem to your system administrator.
CWSJA0052E: Too many bus member targets found for WebSphere MQ server "{0}" on bus "{1}". Number of bus member targets found was {2}.
Explanation When added to a bus, a WebSphere MQ server should have one bus member target. More than one was found.
Action Report this problem to your system administrator.
CWSJA0053E: The parameter {0} is only valid when specifying a WebSphere MQ Server name.
Explanation The supplied parameter was not valid when adding a Server or a Cluster to a bus.
Action Remove the parameter from the addSIBusMember command and retry.
CWSJA0054E: The parameter {0} with value {1} is only valid when specifying a WebSphere MQ Server name.
Explanation The supplied parameter was not valid when creating a Destination. The parameter supplied is only valid when specifying a WebSphere MQ Server name.
Action Remove the parameter from the createSIBDestination command and retry.
CWSJA0055E: The parameter {0} with value {1} is not valid when specifying a WebSphere MQ Server name.
Explanation The supplied parameter was not valid when creating a Destination. The parameter supplied is only valid when not specifying a WebSphere MQ Server name.
Action Remove the parameter from the createSIBDestination command and retry.
CWSJA0056E: The WebSphere MQ Server name parameter can only be specified with a destination type of QUEUE, the type specified was "{0}"
Explanation When creating a destination the WebSphere MQ Server name was specified with a destination type which was not QUEUE.
Action Change the destination type to be QUEUE and retry the command.
CWSJA0057E: The WebSphere MQ queue name parameter must be specified for a destination on a WebSphere MQ Server
Explanation When creating a destination on a WebSphere MQ Server the wmqQueueName parameter must be specified.
Action Change the destination type to be QUEUE and retry the command.
CWSJA0058E: Can not specify both a file store AND a data store, or parameters implying such
Explanation -fileStore and -dataStore are mutually exclusive, likewise parameters relating to both types are not allowed in the same command
Action Either remove parameters relating to file store or data store
CWSJA0059E: Can not specify maximum permanent file store size if unlimited permanent store size is set to true
Explanation When the size of the permanent file store has been set to unlimited, a maximum permanent size can not be set
Action Remove the maximum permanent file store size parameter or change the unlimited permanent file store size to false then retry.
CWSJA0060E: Unable to create file store.
Explanation An exception occurred creating a file store with the configuration data provided.
Action Make sure that the configuration data provided to create a file store is valid.
CWSJA0062E: An unexpected error has occured.
Explanation This scenario shouldnt occur.
Action Unexpected error has occured.
CWSJA0063E: Can not specify parameter {0} for message store type {1}
Explanation A file store parameter has been specified for a data store or vise versa.
Action Check parameters are correct for this message store type
CWSJA0064E: When creating a {0} on a cluster unable to use default values. The parameter {1} is required
Explanation Certain default parameters dont apply with clusters, therefore must be specified
Action Check parameters are correct for this message store type
CWSJA0065E: Can not create a {0} without a value for {1}
Explanation A value for parameter {1} is required to create {0}
Action Check parameters are correct for this message store type
CWSJA0066E: Minimum permanent store size can not be less than log size
Explanation The permanent file store size must be greater than the file store log size
Action Increase the permanent store size or decrease the log size
CWSJA0067E: Log size must be greater than {0} megabytes
Explanation The log size specified is lower than the minimum log size
Action Increase the size of the log file
CWSJA0068E: Maximum permanent store size must be greater than {0} megabytes
Explanation The maximum permanent store size specified is lower than the maximum permanent store size minimum value
Action Increase the size of the maximum permanent store size, or make it unlimited
CWSJA0069E: Maximum permanent store size can not be less than minimum permanent store size
Explanation Maximum store size can not be less than minimum store size
Action either lower the minimum store size, increase the size of the maximum store size or make it unlimited
CWSJA0070E: busSecurity parameter specified with scriptCompatibility set to 6. Set the scriptCompatibility to 6.1 when using the busSecurity parameter
Explanation The busSecurity parameter being specified and scriptCompatibility set to 6 is invalid. The busSecurity parameter is only valid with scriptCompatibility set to 6.1
Action Either set the scriptCompatibility to 6.1 or use the secure parameter.
CWSJA0071E: secure parameter specified with scriptCompatibility set to 6.1. Set the scriptCompatibility to 6 when using the secure parameter
Explanation The secure parameter being specified and scriptCompatibility set to 6.1 is invalid. The secure parameter is only valid with scriptCompatibility set to 6
Action Either set the scriptCompatibility to 6 or use the busSecurity parameter.
CWSJA0072E: Bus security has been specified to be enabled, but administrative security is disabled.
Explanation The busSecurity parameter has been specified to be enabled, but administrative security is not enabled.
Action Either enable administrative security in the Admin Console, or set the busSecurity to be false.
CWSJA0073E: The permitted transport chain name {0} was not found
Explanation The permitted transport chain with the specified name was not found on the bus
Action Check that the transport chain name should exist in the Admin console. Check that the case of the name is correct and try the command again.
CWSJA0074E: Invalid permittedChains setting {0}. Allowable values ALL|SSL_ENABLED|LISTED
Explanation The supplied parameter permittedChains has an invalid value so the command was rejected
Action Set the permittedChains to an allowable value of either ALL, SSL_ENABLED or LISTED
CWSJA0075E: permittedChains parameter specified with the secure parameter for the modifySIBus command
Explanation The permittedChains parameter being specified with the secure parameter is invalid.
Action Use the busSecurity parameter instead of the secure parameter.
CWSJA0076E: filestore parameter is specified for a messaging engine on a pre version 6.1 node
Explanation The filestore option is only valid for messaging engines created on version 6.1 or later nodes.
Action Select a datastore, or choose a node which is of version 6.1 or later.
CWSJA0077E: The transport chain name {0} already exists as a permitted transport for the bus {1}.
Explanation An attempt was made to add a transport chain as a permitted transport to the bus. This failed as the transport chain is already a permitted transport for the bus.
Action Add a transport chain with a different name.
CWSJA0078E: The transport chain name {0} was not found as a permitted transport for the bus {1}.
Explanation An attempt was made to remove a permitted transport from a bus. The permitted transport chain specified is not a permitted transport for the bus specified.
Action If the permitted transport does exist on the bus, check the name and correct and reissue the command.
CWSJA0079E: Incorrect value "{0}" for parameter "scriptCompatibility".
Explanation The value supplied for the parameter scriptCompatibility was not valid.
Action Run the command again, this time supply a valid value which is either 6 or 6.1.
CWSJA0080E: Destination {0} not found on bus {1}.
Explanation The specified destination could not be found on the specified bus.
Action Ensure that the destination being located exists within the administrative domain.
CWSJA0081E: Unable to mediate destination {0} as the WebSphere MQ queue name {1} cannot be used as both the mediation and queue points.
Explanation When mediating a destination whose message point is on WebSphere MQ, the pre-mediation point MQ queue name must not be the same as the message point's MQ queue name.
Action Choose a different WebSphere MQ destination from which the mediation is to get messages from
CWSJA0082E: busSecurity parameter specified with the secure parameter for the modifySIBus command.
Explanation The busSecurity parameter being specified with the secure parameter is invalid.
Action Remove either the busSecurity or the secure parameter from the modifySIBus command.
CWSJA0083E: The parameter {0} is only valid for a destination type which is either a Queue, Port or WebService
Explanation The parameter supplied can only be used when the destination type is Queue, Port or WebService.
Action Run the command again without using the previously stated parameter.
CWSJA0084E: The value {0} for parameter port is not a valid value.
Explanation The range of allowable values for the port parameter range between 0 and 65535.
Action Run the command again specifying a valid port value.
CWSJA0085E: The value {0} for the WebSphere MQ queue manager or queue sharing group is too long.
Explanation The maximum length for a WebSphere MQ queue manager or queue sharing group is 48 characters.
Action Run the command again specifying a valid WebSphere MQ queue manager or queue sharing group value.
CWSJA0086E: The value {0} for the WebSphere MQ queue manager or queue sharing group contains invalid characters.
Explanation The WebSphere MQ queue manager or queue sharing group allowable characters range a-z, A-Z, 0-9, ., /, % and _.
Action Run the command again specifying a valid WebSphere MQ queue manager or queue sharing group value.
CWSJA0087E: The value {0} for the WebSphere MQ channel is too long.
Explanation The maximum length for a WebSphere MQ channel is 20 characters.
Action Run the command again specifying a valid WebSphere MQ channel value.
CWSJA0088E: The value {0} for the WebSphere MQ channel contains invalid characters.
Explanation The WebSphere MQ queue channel allowable characters range a-z, A-Z, 0-9, ., /, % and _.
Action Run the command again specifying a valid WebSphere MQ channel value.
CWSJA0089E: Scope specification is not valid, unable to locate node {0} and or server {1}.
Explanation The details specified do not represent a valid scope specification.
Action Make sure that valid node and server name details are used to represent the scope.
CWSJA0090E: Scope specification is not valid, unable to locate cluster {0}.
Explanation The details specified do not represent a valid scope specification.
Action Make sure that valid cluster name details are used to represent the scope.
CWSJA0091E: The parameter "topicAccessCheckRequired" is only valid for a destination type which is TopicSpace.
Explanation The parameter "topicAccessCheckRequired" supplied can only be used when the destination type is TopicSpace.
Action Run the command again and remove the parameter specified.
CWSJA0092E: Can not specify maximum temporary file store size if unlimited temporary store size is set to true.
Explanation When the size of the temporary file store has been set to unlimited, a maximum temporary size can not be set.
Action Remove the maximum temporary file store size parameter or change the unlimited temporary file store size to false then retry.
CWSJA0093E: Minimum temporary store size can not be less than log size.
Explanation The temporary file store size must be greater than the temporary store log size.
Action Increase the temporary store size or decrease the log size.
CWSJA0094E: Maximum temporary store size must be greater than {0} megabytes.
Explanation The maximum temporary store size specified is lower than the maximum temporary store size minimum value.
Action Increase the size of the maximum temporary store size, or make it unlimited.
CWSJA0095E: Maximum temporary store size can not be less than minimum temporary store size.
Explanation Maximum temporary store size can not be less than minimum temporary store size.
Action either lower the minimum temporary store size, increase the size of the maximum temporary store size or make it unlimited.
CWSJA0096E: The value {0} for the WebSphere MQ reply to queue is too long.
Explanation The maximum length for a WebSphere MQ reply to queue is 48 characters.
Action Run the command again specifying an allowable WebSphere MQ reply to queue value.
CWSJA0097E: The value {0} for the WebSphere MQ reply to queue contains invalid characters.
Explanation The WebSphere MQ reply to queue allowable characters range a-z, A-Z, 0-9, ., /, % and _.
Action Run the command again specifying an allowable WebSphere MQ reply to queue value.
CWSJA0098E: The parameters "aliasBus" and "foreignBus" were supplied to the deleteSIBDestination command.
Explanation The deleteSIBDestination command takes either the "aliasBus" or the "foreignBus" parameters. The command had both parameters supplied.
Action If there are multiple destinations with the same name, then the aliasBus, foreignBus parameters can be used to identify an Alias, or a Foreign destination to delete. Only one of aliasBus or foreignBus parameters can be supplied.
CWSJA0099E: Failed to find destination "{1}" on bus "{0}" with an alias bus "{2}".
Explanation The named Alias destination could not be located on the named bus within the administrative domain.
Action Make sure that the named Alias destination exists on the named bus with the named alias bus.
CWSJA0100E: Failed to find destination "{1}" on bus "{0}" with a foreign bus "{2}".
Explanation The named Foreign destination could not be located on the named bus within the administrative domain.
Action Make sure that the named Foreign destination exists on the named bus with the named foreign bus.
CWSJA0101E: A file store cannot be specified for a server which is not at version 6.1 or later.
Explanation The support for a file store is only available on WebSphere Application Server version 6.1 or later. Either the -fileStore option was specified or another one that implied it.
Action Run the command again, this time specifying a data store.
CWSJA0102E: The maintainStrictMessageOrder option cannot be used for a destination that has all its message points on servers of a version less than 6.1.
Explanation The maintain strict message order support is only available on WebSphere Application Server version 6.1 or later.
Action Run the command again, this time either not specifying strict message ordering, or specifying a server of version 6.1 or later.
CWSJA0103E: The specified scope "{0}" is not a member of bus "{1}".
Explanation The operation could not be invoked because the specified server or cluster is not a member of the given bus.
Action Ensure that a server or cluster is specified which is a member of the given bus.
CWSJA0104E: No messaging engines found at scope "{0}" for bus "{1}".
Explanation The operation could not be invoked because no messaging engines exist for the given bus at the specified scope.
Action Ensure that there is a messaging engine at the specified scope for the given bus.
CWSJA0105E: The messaging engine with UUID "{0}" does not exist at scope "{1}".
Explanation The operation could not be invoked because the messaging engine with the given UUID does not exist at the specified scope.
Action Ensure that there is a messaging engine at the specified scope.
CWSJA0106E: Security settings for bus "{0}" are not compatible with server "{1}" because it resides on pre-6.1 node "{2}".
Explanation The server could not be added to the bus because the server resides on a pre-6.1 node, and bus security settings are not compatible with pre-6.1 nodes. The permitted transport chains setting must not be "LISTED" or "SSL_ENABLED". The group "Server" must not be in the bus connector role.
Action Disable security on the named bus, or modify the bus security settings so that it is compatible with pre-6.1 nodes, or upgrade the named server so that it resides on a 6.1 node.
CWSJA0107E: Security settings for bus "{0}" are not compatible with cluster "{1}" because one or more of its member servers reside on a pre-6.1 node.
Explanation The cluster could not be added to the bus because at least one of its member servers resides on a pre-6.1 node, and bus security settings are not compatible with pre-6.1 nodes. The permitted transport chains setting must not be "LISTED" or "SSL_ENABLED". The group "Server" must not be in the bus connector role.
Action Disable security on the named bus, or modify the bus security settings so that it is compatible with pre-6.1 nodes, or upgrade the pre-6.1 servers on the named cluster so that they reside on 6.1 nodes.
CWSJA0108E: The value "{1}" for the permitted transport chains bus security attribute is not valid for bus "{0}" because the bus contains at least one pre-6.1 bus member.
Explanation Enabling bus security and/or changing the named bus security attribute to the indicated value when the bus contains one or more pre-6.1 bus members is not allowed because the value is not compatible with pre-6.1 nodes. The permitted transport chains setting must not be "LISTED" or "SSL_ENABLED".
Action Disable security on the named bus, or modify the named security setting to a value that does not conflict with pre-6.1 bus members, or remove all pre-6.1 bus members from the bus.
CWSJA0109E: Found group "Server" in the bus connector role for bus "{0}". This is not allowed because the bus contains at least one pre-6.1 bus member.
Explanation The named bus contains one or more pre-6.1 bus members. Having the named group in the bus connector role is not compatible with pre-6.1 bus members. The group "Server" must not be in the bus connector role.
Action Disable security on the named bus, or remove the named group from the bus connector role, or remove all pre-6.1 bus members from the bus.
CWSJA0145E: Duplicate destination "{0}" in nameList.
Explanation The given destination is specified more than once in the nameList.
Action Make sure that the destinations specified in the nameList are unique.
CWSJA0200E: Failed to get SIB JMS resource adapter at specified scope.
Explanation At unsuccessful attempt was made to locate a JMS JCA resource adapter installed at the specified scope.
Action Ensure that a JMS JCA resource adapter exists within the specified scope.
CWSJA0201E: Incorrect value for type parameter: {0}.
Explanation An incorrect type has been found for the connection factory.
Action Ensure that the connection factory type is either Queue, Topic or All.
CWSJA0202E: Failed to get J2C command result: {0}.
Explanation The command was run but no result object was returned.
Action Ensure that the correct configuration information has been passed to the command being run.
CWSJA0203E: Target object is not a SIB JMS connection factory.
Explanation The target object specified is not of type QueueConnectionFactory, TopicConnectionFactory or ConnectionFactory.
Action Ensure that a valid connection factory interface is specified to the target object.
CWSJA0204E: Target object is not a SIB JMS queue.
Explanation The interface of the target object is not of type Queue.
Action Ensure that the target object is of type Queue.
CWSJA0205E: Target object is not a SIB JMS topic.
Explanation The interface of the target object is not of type Topic.
Action Ensure that the target object is of type Topic.
CWSJA0206E: Not allowed to create a SIB JMS connection factory called "{0}".
Explanation The name provided for the SIB JMS connection factory does not adhere to naming restrictions.
Action Ensure that the name does not begin with an underscore, and is not empty or null.
CWSJA0207E: Not allowed to delete a SIB JMS connection factory called "{0}".
Explanation The name provided for the SIB JMS connection factory does not adhere to naming restrictions.
Action Ensure that the name does not begin with an underscore, and is not empty or null.
CWSJA0208E: Not allowed to create a SIB JMS queue called "{0}".
Explanation The name provided for the SIB JMS queue does not adhere to naming restrictions.
Action Ensure that the name does not begin with an underscore, and is not empty or null.
CWSJA0209E: Not allowed to delete a SIB JMS queue called "{0}".
Explanation The name provided for the SIB JMS queue does not adhere to naming restrictions.
Action Ensure that the name does not begin with an underscore, and is not empty or null.
CWSJA0210E: Not allowed to create a SIB JMS topic called "{0}".
Explanation The name provided for the SIB JMS Topic does not adhere to naming restrictions.
Action Ensure that the name does not begin with an underscore, and is not empty or null.
CWSJA0211E: Not allowed to delete a SIB JMS topic called "{0}".
Explanation The name provided for the SIB JMS topic does not adhere to naming restrictions.
Action Ensure that the name does not begin with an underscore, and is not empty or null.
CWSJA0212E: Not allowed to configure a SIB JMS queue with "{0}" = "{1}".
Explanation An illegal value has been provided for the JMS Queue property specified.
Action Ensure that the value specified is legal for the given property.
CWSJA0213E: Not allowed to configure a SIB JMS topic with "{0}" = "{1}".
Explanation An illegal value has been provided for the JMS Topic property specified.
Action Ensure that the value specified is legal for the given property.
CWSJA0215E: Failed to create a SIB JMS queue with queue name : "{0}".
Explanation An internal exception was thrown creating an instance of a JMS Queue.
Action Ensure that a valid queue name has been specified upon creation of the Queue object.
CWSJA0216E: Failed to create a SIB JMS topic with topic name : "{0}".
Explanation An internal exception was thrown creating an instance of a JMS Topic.
Action Ensure that a valid queue name has been specified upon creation of the Topic object.
CWSJA0217E: An internal error has occurred. Failed to create a SIB JMS connection factory.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSJA0400E: ActivationSpec with given name({0}) or jndiName({1}) already exists in given scope.
Explanation The named ActivationSpec already exists on the specified resource adapter.
Action Ensure that ActivationSpec objects are unique within a given scope.
CWSJA0401E: Unable to create SIB JMS ActivationSpec at scope {0}.
Explanation The create command ran but no result object was returned.
Action Ensure that the correct configuration information has been passed to the create command being run.
CWSJA0402E: Unable to modify attributes of ActivationSpec {0}.
Explanation It is likely that Incorrect or null parameters were passed to the modify command.
Action Ensure that all parameters passed to the modify command are valid.
CWSJA0403E: Unable to find SIB JMS resource adapter in scope {0}.
Explanation It is likely that Incorrect or null parameters were passed to the command.
Action Ensure that all parameters are valid, and that a JMS JCA resource adapter is installed at the specified scope.
CWSJA0404E: Failed to get list of existing SIB JMS ActivationSpecs from resource adapter {0}.
Explanation The list command failed either because null parameters were given, or no result was returned.
Action Ensure that all parameters passed to the command are valid, and not null.
CWSJA0405E: {0} is not a valid SIB JMS ActivationSpec.
Explanation The target object specified is not of the correct type.
Action Ensure that the target object is of type JMS ActivationSpec.
CWSJA0406E: Not allowed to create a SIB JMS ActivationSpec called "{0}".
Explanation The name provided for the SIB JMS ActivationSpec does not adhere to naming restrictions.
Action Ensure that the name does not begin with an underscore, and is not empty or null.
CWSJA0407E: Not allowed to delete a SIB JMS ActivationSpec called "{0}".
Explanation The name provided for the SIB JMS ActivationSpec does not adhere to naming restrictions.
Action Ensure that the name does not begin with an underscore, and is not empty or null.
CWSJA0409E: {0} is not a valid value for read ahead.
Explanation The user has entered a value for the read ahead property which is not valid
Action Check the documentation for a valid value
CWSJA0410E: {0} is not a valid value for destination type.
Explanation The user has entered a value for the destination type property which is not valid
Action Check the documentation for a valid value
CWSJA0411E: {0} is not a valid value for target type.
Explanation The user has entered a value for the target type property which is not valid
Action Check the documentation for a valid value
CWSJA0412E: {0} is not a valid value for target significance.
Explanation The user has entered a value for the target significance property which is not valid
Action Check the documentation for a valid value
CWSJA0600E: Mediation "{0}" already exists.
Explanation The mediation specified already exists within the administrative domain.
Action Ensure that all mediations are uniquely identified within an administrative domain.
CWSJA0601E: Mediation "{0}" cannot be found.
Explanation The mediation specified could not be found within the administrative domain.
Action Ensure that the mediation specified to the command exists.
CWSJA0602E: Mediation "{0}" cannot be deleted. It is being used to mediate destination "{1}".
Explanation A mediation cannot be deleted whilst it is being used to mediate a destination.
Action Ensure that a mediation is not be used before trying to delete it.
CWSJA0603E: Destination "{0}" cannot be found.
Explanation The destination specified could not be found within the administrative domain.
Action Ensure that the destination specified exists.
CWSJA0604E: Destination "{0}" is already mediated.
Explanation The destination specified is already mediated, and no destination may be mediated twice.
Action Ensure that the destination specified is not already mediated before trying to mediate it.
CWSJA0605E: Supply either "node" and "server" parameters or "cluster" parameter.
Explanation Null parameters have been supplied to the command.
Action Ensure that either "node" and "server" parameters, or "cluster" parameter is supplied to the command.
CWSJA0606E: Bus member "{0}" cannot be found.
Explanation The bus member specified could not be located in the administrative domain.
Action Ensure that the bus member specified exists before trying to use it.
CWSJA0607E: Destination "{0}" cannot be mediated.
Explanation An inconsistent configuration has been detected.
Action Run cross document validation to check the destination configuration.
CWSJA0608E: Destination "{0}" is not mediated.
Explanation It is not possible to un-mediate a destination which is not already mediated.
Action Ensure that the destination is mediated before attempting to un-mediate it.
CWSJA0609E: Not allowed to create a mediation called "{0}".
Explanation The name provided for the mediation does not adhere to naming restrictions.
Action Ensure that the name does not begin with an underscore, and is not empty or null.
CWSJA0610E: Not allowed to delete a mediation called "{0}".
Explanation The name provided for the mediation does not adhere to naming restrictions.
Action Ensure that the name does not begin with an underscore, and is not empty or null.
CWSJA0611E: When supplying "wmqServer" parameter it must be supplied with either "node" and "server" parameters or "cluster" parameter.
Explanation Invalid parameters have been supplied to the command. When specifying "wmqServer" an execution point must be specified where the mediation will run.
Action Ensure that "wmqServer" is supplied with either "node" and "server" parameters, or "cluster" parameter.
CWSJA0612E: The parameter {0} is only valid when specifying a WebSphere MQ Server name using the "wmqServer" parameter.
Explanation The supplied parameter was not valid when mediating a destination and a WebSphere MQ Server name was not specified.
Action Remove the parameter from the mediateSIBDestination command and retry.
CWSJA0613E: When specifying a WebSphere MQ Server name using the "wmqServer" parameter the "wmqQueueName" parameter must be supplied.
Explanation When specifying a WebSphere MQ Server name a WebSphere MQ Queue name must be supplied.
Action Add the "wmqQueueName" parameter to the mediateSIBDestination command and retry.
CWSJA0614E: No bus member found for WebSphere MQ server {0} on bus {1}.
Explanation When mediating a destination using a WebSphere MQ server it must have been added to the bus, but no bus member was found.
Action Ensure that the WebSphere MQ Server has been added to the bus specified and retry the command
CWSJA0615E: node parameter specifies a pre version 6.1 node, which is not valid for a WebSphere MQ mediation execution point
Explanation The node parameter specifies a pre version 6.1 node which cannot host a mediation execution point for a WebSphere MQ mediated destination.
Action Select a node which is of version 6.1 or later.
CWSJA0616E: When specifying a value of true for parameter "externallyMediated" a "wmqServer" parameter must be supplied.
Explanation External mediation support is only valid for destinations localized to WebSphere MQ.
Action Either specify a false value for the "externallyMediated" parameter or add a "wmqServer" parameter.
CWSJA0617E: When specifying a value of true for parameter "externallyMediated" and a WebSphere MQ server, the "node", "server" or "cluster" parameters should not be specified.
Explanation Externally mediating destinations are only supported for destinations that are localized in WebSphere MQ.
Action Remove the "node" or "server" or "cluster" parameter that was specified.
CWSJA0618E: When specifying a value of true for parameter "externallyMediated" the destination being mediated must be assigned to WebSphere MQ.
Explanation Externally mediating destinations are only supported for destinations that are localized in WebSphere MQ.
Action Set the "externallyMediated" parameter to false or mediate a destination that is assigned to WebSphere MQ.
CWSJA0800E: No cells found in configuration archive.
Explanation The configuration archive does not contain any cells.
Action Make sure that the configuration archive contains a cell.
CWSJA0801E: No cells found in the deployment manager configuration.
Explanation The deployment manager configuration does not contain any cells.
Action Make sure that the deployment manager configuration contains a cell.
CWSJA0802W: WARNING: Bus "{0}" already exists in the deployment manager configuration. Bus "{0}" will NOT be replaced in the deployment manager configuration.
Explanation A bus of the same name already exists in the deployment manager configuration. As a result the bus on this node will not be added to the deployment manager configuration. However the node will still be federated.
Action Ensure that the named bus does not exist in the deployment manager configuration before running addNode. If there is a conflict in the names, the bus on the node being federated will not be included. As a result the bus on the deployment manager must be configured to have the required resources needed. Either that, or the bus should be either renamed or deleted.
CWSJA0803E: Configuration contains no cells.
Explanation The configuration does not contain any cells.
Action Make sure that the configuration contains a cell.
CWSJA1000E: Deployment manager configuration contains no cells.
Explanation No cells were found in the deployment manager configuration.
Action Ensure that the deployment manager configuration contains a cell definition.
CWSJA1001E: No deployment manager configuration session supplied.
Explanation Internal error. Method invoked requires a deployment manager configuration session parameter.
Action Please contact your system administrator to resolve this problem.
CWSJA1002E: No cell specified.
Explanation Internal error. Method invoked requires a cell object,
Action Please contact your system administrator to resolve this problem.
CWSJA1003E: No bus specified.
Explanation Internal error. Method invoked requires a bus object.
Action Please contact your system administrator to resolve this problem.
CWSJA1004E: No destination specified.
Explanation Internal error. Method invoked requires destination object.
Action Please contact your system administrator to resolve this problem.
CWSJA1200E: The {0} command did not return a result.
Explanation Internal error. The specified command did not return a result.
Action Please contact your system administrator to resolve this problem.
CWSJA1400E: Application server template ID is null.
Explanation Internal error. The application server template ID is null.
Action Please contact your system administrator to resolve this problem.
CWSJA1600E: WebSphere MQ Server "{0}" not found.
Explanation The specified WebSphere MQ Server name could not be located within the administrative domain.
Action Make sure that the WebSphere MQ Server name specified is a valid name for an existing WebSphere MQ Server.
CWSJA1601E: More than one WebSphere MQ Server named "{0}" found.
Explanation Only one instance of a WebSphere MQ Server should exist with the name specified, yet more than one instance has been found.
Action Make sure that WebSphere MQ Server names are unique within the administrative domain.
CWSJA1602E: A WebSphere MQ Server named "{0}" already exists.
Explanation A WebSphere MQ Server name must be unique. A WebSphere MQ Server with the supplied name already exists.
Action Make sure that WebSphere MQ Server names are unique within the administrative domain.
CWSJA1603E: WebSphere MQ Server Proxy "{0}" not found on Bus {1}.
Explanation The specified WebSphere MQ Server Proxy name could not be located within the Bus administrative domain.
Action Make sure that the WebSphere MQ Server Proxy name specified is a valid name for an existing WebSphere MQ Server Proxy. Check that the bus name specified is the correct bus for the WebSphere MQ Server Proxy
CWSJA1604E: Multiple instances of WebSphere MQ Server Proxy "{0}" found on Bus {1}.
Explanation Only one instance of a WebSphere MQ Server Proxy should exist with the name specified, yet more than one instance has been located.
Action Make sure that WebSphere MQ Server Proxy names are unique within the administrative domain.
CWSJA1605E: The selected JMS provider is built-in and cannot be deleted.
Explanation Only custom JMS providers can be deleted.
Action Select another JMS provider to delete.
CWSJA2000E: The Foreign Bus "{0}" could not be found on Bus "{1}"
Explanation A Foreign Bus name was supplied to the command which could not be resolved on the Bus provided.
Action Ensure that the Foreign Bus supplied to the command exists in the configuration.
CWSJA2001E: The parameter nextHopBus must be specified when routingType = Indirect
Explanation When the routingType parameter = Indirect, a valid nextHopBus parameter must be supplied.
Action Ensure that the nextHopBus parameter and value is supplied to the command.
CWSJA2002E: The type parameter must be specified when routingType parameter = Direct
Explanation When the routingType parameter = Direct, a valid type parameter must be specified
Action Ensure that the type parameter for the command is either "SIBus" or "MQ"
CWSJA2003E: An invalid routingType parameter was supplied to this command, allowable values are "Direct" or "Indirect".
Explanation The routingType of either "Direct" or "Indirect" is required for this command.
Action Ensure that the routingType parameter for the command is either "Direct" or "Indirect"
CWSJA2004E: A virtual link could not be found on foreign bus "{0}"
Explanation The foreign bus specified to the command does not have a virtual link child object.
Action Ensure that the foreign bus specified has a virtual link child object.
CWSJA2005E: The foreign bus "{0}" does not contain a SIBVirtualMQLink child object.
Explanation The foreign bus specified contains a SIBVirtualGatewayLink, not the required SIBVirtualMQLink.
Action Ensure that the foreign bus specified has a SIBVirtualMQLink child object.
CWSJA2006E: The default priority specified "{0}" is not a valid value for this attribute.
Explanation The value of the default priority attribute must be between 0 and 9 inclusive.
Action Ensure that a valid value is specified for the default priority attribute.
CWSJA2007E: The value supplied for "reliability" is greater than the value supplied for "maxReliability".
Explanation The value supplied for "reliability" should be less than or equal to the value supplied for "maxReliability".
Action Report this problem to your system administrator.
CWSJA2008E: An invalid type parameter was supplied to this command, allowable values are "MQ" or "SIBus".
Explanation The type of either "MQ" or "SIBus" is required for this command.
Action Ensure that the type parameter for the command is either "MQ" or "SIBus"
CWSJA2009E: The routingType parameter is required if the type parameter is supplied.
Explanation The type parameter is only permitted if the routingType parameter is also supplied.
Action Make sure that the routingType parameter is supplied if the type parameter is supplied.
CWSJA2010E: The name of the foreign bus cannot be the same as the local bus name "{0}" on which it is to be created.
Explanation When creating a foreign bus, its name cannot be the same as the local bus on which it is being created. The name should be the unique name of the foreign bus being connected to.
Action Make sure that the name parameter supplied is different to the bus parameter.
CWSJA2200E: The bus name "{0}" could not be found.
Explanation The bus name that was supplied to the command could not be resolved to a Bus object.
Action Ensure that you used the correct spelling for the name, and that a Bus with that name exists in the configuration.
CWSJA2201E: The messaging engine "{0}" could not be found on the bus supplied.
Explanation A messaging engine name was supplied to the command which could not be resolved on the bus name supplied.
Action Ensure that both the messaging engine and bus name supplied to the command exist in the configuration.
CWSJA2202E: The value "{0}" is not valid for the parameter "{1}"
Explanation An invalid value was supplied for the parameter specified above.
Action See the command help for a list of valid parameter values.
CWSJA2203E: An internal error occured getting the "name" attribute of MQLink "{0}" : "{1}"
Explanation An internal error has occured. See linked exception for details.
Action Ensure that a valid MQLink name was specified to the command.
CWSJA2204E: The foreign bus "{0}" could not be found on the bus "{1}"
Explanation The foreign bus name supplied to the command is not the name of a foreign bus configured on the bus.
Action Ensure that both the foreign bus and bus name supplied to the command exist in the configuration.
CWSJA2206E: A Bus Member Target with an Engine UUID of "{0}" could not be found
Explanation The engine UUID specified above could not be found on any of the existing Bus Member Targets.
Action Ensure that the correct messaging engine was supplied to the command.
CWSJA2207E: The MQLink "{0}" could not be found on the messaging engine "{1}"
Explanation An MQLink with the name supplied could not be found on the messaging engine supplied.
Action Ensure that both the messaging engine and MQLink named on the command exist in the configuration.
CWSJA2400E: An internal error occured getting the "name" attribute of SIBLink "{0}" : "{1}"
Explanation An internal error has occured. See linked exception for details.
Action Ensure that a valid SIBLink name was specified to the command.
CWSJA2401E: A virtual link could not be found on foreign bus "{0}"
Explanation The foreign bus specified to the command does not have a child SIBVirtualGatewayLink object.
Action Ensure that the foreign bus specified has a SIBVirtualGatewayLink child object.
CWSJA2402E: The foreign bus "{0}" does not contain a SIBVirtualGatewayLink child object.
Explanation The foreign bus specified contains a SIBVirtualMQLink, not the required SIBVirtualGatewayLink.
Action Ensure that the foreign bus specified has a SIBVirtualGatewayLink child object.
CWSJA2403E: The SIBLink "{0}" could not be found on the messaging engine "{1}"
Explanation A SIBLink name was supplied to the command which could not be resolved on the messaging engine name supplied.
Action Ensure that both the messaging engine and SIBLink name supplied to the command exist in the configuration.
CWSJA2404E: There is already a SIBLink or MQLink with the name "{0}"
Explanation SIBLinks and MQLinks objects share a namespace within a Messaging Engine, and require unique names.
Action If you want to use the supplied name, ensure that neither an MQLink nor SIBLink already exists with that name. Otherwise, specify a different name.
CWSJA2405E: Scope specification is not valid.
Explanation The details specified do not represent a valid scope specification.
Action Make sure that valid node name, server name and cluster name details are used to represent the scope.
CWSJA2500E: The configuration service is not available.
Explanation This message is displayed when an AdminTask command is attempted on a process that is not connected to a server that has a running config service.
Action Reissue the command on a process that is connected to a server that has a running config service - for example a deployment manager, managed server or unmanaged server.
Reference topic    

Terms of Use | Feedback

Last updated: Nov 25, 2008 6:45:20 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.management.commands.sib.CWSJAMessages.html

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