- CWSXA0200E: 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.
- User Action: Ensure that you used the correct spelling for the name, and that a Bus with that name exists in the configuration.
- CWSXA0201E: 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.
- User Action: Ensure that both the messaging engine and bus name supplied to the command exist in the configuration.
- CWSXA0202E: The value "{0}" is not valid for the parameter "{1}"
- Explanation: An invalid value was supplied for the parameter specified above.
- User Action: See the command help for a list of valid parameter values.
- CWSXA0203E: An internal error occured getting the "name" attribute of MQLink "{0}" : "{1}"
- Explanation: An internal error has occured. See linked exception for details.
- User Action: Ensure that a valid MQLink name was specified to the command.
- CWSXA0204E: 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.
- User Action: Ensure that both the foreign bus and bus name supplied to the command exist in the configuration.
- CWSXA0206E: 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.
- User Action: Ensure that the correct messaging engine was supplied to the command.
- CWSXA0207E: 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.
- User Action: Ensure that both the messaging engine and MQLink named on the command exist in the configuration.
- CWSXA0300E: The Foreign Bus "{1}" could not be found on Bus "{0}"
- Explanation: A Foreign Bus name was supplied to the command which could not be resolved on the Bus provided.
- User Action: Ensure that the Foreign Bus supplied to the command exists in the configuration.
- CWSXA0301E: The parameter nextHopBus must be specified when routingType = Indirect
- Explanation: When the routingType parameter = Indirect, a valid nextHopBus parameter must be supplied.
- User Action: Ensure that the nextHopBus parameter and value is supplied to the command.
- CWSXA0302E: The type parameter must be specified when routingType parameter = Direct
- Explanation: When the routingType parameter = Direct, a valid type parameter must be specified
- User Action: Ensure that the type parameter for the command is either "SIBus" or "MQ"
- CWSXA0303E: An invalid routingType parameter was supplied to this command.
- Explanation: The routingType of either "Direct" or "Indirect" is required for this command.
- User Action: Ensure that the routingType parameter for the command is either "Direct" or "Indirect"
- CWSXA0304E: 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.
- User Action: Ensure that the foreign bus specified has a virtual link child object.
- CWSXA0305E: The foreign bus "{0}" does not contain a SIBVirtualMQLink child object.
- Explanation: The foreign bus specified contains a SIBVirtualGatewayLink, not the required SIBVirtualMQLink.
- User Action: Ensure that the foreign bus specified has a SIBVirtualMQLink child object.
- CWSXA0306E: 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.
- User Action: Ensure that a valid value is specified for the default priority attribute.
- CWSXA0307E: 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".
- User Action: Report this problem to your system administrator.
- CWSXA0308E: An invalid type parameter was supplied to this command.
- Explanation: The type of either "MQ" or "SIBus" is required for this command.
- User Action: Ensure that the type parameter for the command is either "MQ" or "SIBus"
- CWSXA0309E: 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.
- User Action: Make sure that the routingType parameter is supplied if the type parameter is supplied.
- CWSXA0400E: An internal error occured getting the "name" attribute of SIBLink "{0}" : "{1}"
- Explanation: An internal error has occured. See linked exception for details.
- User Action: Ensure that a valid SIBLink name was specified to the command.
- CWSXA0401E: 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.
- User Action: Ensure that the foreign bus specified has a SIBVirtualGatewayLink child object.
- CWSXA0402E: The foreign bus "{0}" does not contain a SIBVirtualGatewayLink child object.
- Explanation: The foreign bus specified contains a SIBVirtualMQLink, not the required SIBVirtualGatewayLink.
- User Action: Ensure that the foreign bus specified has a SIBVirtualGatewayLink child object.
- CWSXA0403E: 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.
- User Action: Ensure that both the messaging engine and SIBLink name supplied to the command exist in the configuration.
- CWSXA0404E: 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.
- User 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.
- CWSXA0405E: Scope specification is not valid.
- Explanation: The details specified do not represent a valid scope specification.
- User Action: Make sure that valid node name, server name and cluster name details are used to represent the scope.
- CWSXA0600E: The value "{0}" is not valid for the Messaging Engine custom property "multicastPort".
- Explanation: Valid port values are up to and including 65535.
- User Action: Ensure that a valid number was specified for the multicastPort property.
- CWSXA0601E: The value "{0}" is not valid for the Messaging Engine custom property "multicastTTL".
- Explanation: Valid TTL values are up to and including 32767.
- User Action: Ensure that a valid number was specified for the multicastTTL property.
- CWSXA0602E: The value "{0}" is not valid for the Topic Connection Factory custom property "subcriptionProtocol".
- Explanation: Valid values are "Unicast", "Multicast" and "UnicastAndMulticast".
- User Action: Ensure that a valid value was specified for the subscriptionProtocol property.
- CWSXA0603E: The scope "{0}" could not be found using the parameters supplied to the command.
- Explanation: The command supplied a cell parameter, and optional node and server parameters which did not reference a valid scope.
- User Action: Ensure that a valid set of scope parameters were supplied to the command.
- CWSXA0604E: A J2C Resource Adapter with the name "SIB JMS Resource Adapter" could not be found at scope "{0}"
- Explanation: An unsuccessful attempt was made to access the J2C Resource Adapter at the scope provided.
- User Action: Ensure that a J2C Resource Adapter exists at this scope with the name "SIB JMS Resource Adapter".
- CWSXA0605E: A J2C Connection Factory with the jndiName "{0}" could not be found at the scope provided.
- Explanation: An unsuccessful attempt was made to access a J2C Connection Factory at the scope provided.
- User Action: Ensure that a J2C Connection Factory exists at this scope with the jndiName supplied to the command.
- CWSXA0606E: An invalid combination of parameters to set the scope was entered to the command.
- Explanation: The parameters supplied do not resolve to a valid scope. See user action for more detail.
- User Action: Specify either "cell", "cell" and "cluster", "cell" and "node", or "cell" "node" and "server" parameters.
- CWSXA0607E: The JMS Connection Factory with jndiName of "{0}" is of type javax.jms.QueueConnectionFactory.
- Explanation: Multicast properties can only be set on objects of type javax.jms.ConnectionFactory or javax.jms.TopicConnectionFactory.
- User Action: Ensure that the JMS Connection Factory identified to the command is of the correct type.
- CWSXA0608E: No valid object was specified to the command.
- Explanation: The command specified neither a targer object or a suitable parameter combiniation.
- User Action: Ensure that either a target object or suitable node/server/cluster parameters are supplied to the command.
- CWSXA0609E: The JNDI name parameter was not supplied to the command.
- Explanation: If not target object is supplied to the command, a jndiName and valid scope details must be supplied.
- User Action: Ensure that either a target object or suitable scope and jndiName values are supplied to the command.
- CWSXA1500E: Application does not contain an SCA module.
- Explanation: The SCA application supplied does not contain a .module file.
- User Action: Supply an application that contains an SCA module.
- CWSXA1501E: Application "{0}" does not exist.
- Explanation: The application specified cannot be found in the cell.
- User Action: Ensure the application specified has been installed.
- CWSXA1502E: No SCA module found in application "{0}" binaries.
- Explanation: No SCA module exists in the application specified.
- User Action: Ensure the correct application has been specified.
- CWSXA1503E: The module "{0}" does not exist in application "{1}".
- Explanation: The SCA module specified is not found in the application specified.
- User Action: Ensure the correct module and application have been specified.
- CWSXA1504E: The module "{0}" does not exist.
- Explanation: The module specified cannot be found in any application in the cell.
- User Action: Ensure the correct module has been specified.
- CWSXA1505E: The import "{0}" does not exist in module "{1}".
- Explanation: The import specified cannot be found in the module specified to the command.
- User Action: Ensure the correct import and module details have been specified.
- CWSXA1506E: The export "{0}" does not exist in module "{1}".
- Explanation: The export specified cannot be found in the module specified to the command.
- User Action: Ensure the correct export and module details have been specified.
- CWSXA1507E: The import "{0}" in module "{1}" does not contain an import binding of type SCAImportBinding.
- Explanation: The import specified has the incorrect type of Import Binding for this command.
- User Action: Ensure the import specified contains an SCAImportBinding.
- CWSXA1508E: The destination "{0}" could not be found on bus "{1}".
- Explanation: The destination could not be found on the specified bus.
- User Action: Ensure the SCA System Bus has a suitable destination on it.
- CWSXA1509E: The destination with name "{0}" could not be created.
- Explanation: The destination could not be created.
- User Action: Re-install the application to retry the destination creation.
- CWSXA1510E: The destination with name "{0}" could not be deleted.
- Explanation: The destination could not be deleted.
- User Action: Delete the named destination manually.
- CWSXA1511E: Failed to resolve EJB reference mappings for module.
- Explanation: The EJB reference supporting the synchronous SCA import binding could not be found within the application.
- User Action: Verify that the application is well-formed.
- CWSXA1512E: No forward routing path was found on the import link destination for import "{0}" in module "{1}".
- Explanation: An invalid destination configuration exists, where the import link destination for the above import does not contain an forward routing path.
- User Action: Uninstall and re-install the SCA Module application in question to refresh the destination configuration.
- CWSXA1513W: Interface "{1}", as required by import "{0}", could not be found in export "{2}". This may mean the interfaces are incompatible.
- Explanation: There is a portType on the import interfaces that could not be found in the target export interfaces. This may mean the interfaces are incompatible.
- User Action: Ensure the target export interfaces are compatible with the import interfaces.