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. |
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. |
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. |
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. |
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. |
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. |
Explanation | An Incorrect destination type has been specified. |
Action | Make sure the destination type specified is a valid destination type. |
Explanation | The parameters supplied do not provide a valid bus Member configuration. |
Action | Provide either "node" and "server" parameters, or "cluster" parameter. |
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. |
Explanation | The destination specified already exists on the bus. |
Action | Ensure that destinations on a bus have unique names. |
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. |
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. |
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. |
Explanation | Multiple messaging engines have been found matching the configuration data provided. |
Action | Ensure that messaging engines are unique within an administrative domain. |
Explanation | An attempt has been made to locate a JDBC provider within the scope provider, but none was found. |
Action | Ensure that there is a JDBC provider available within the administrative domain. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | The specified parameter is not a valid option for bus name. |
Action | Ensure that a valid bus name is being specified upon bus creation. |
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. |
Explanation | The bus member specified could not be located within the administrative domain. |
Action | Ensure that a valid bus member is being located. |
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. |
Explanation | A messaging engine already exists with the configuration data supplied. |
Action | Ensure that unique configuration data is supplied when creating a messaging engine. |
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. |
Explanation | An exception occurred attempting to locate the specified destination. |
Action | Ensure that the destination being located exists within the administrative domain. |
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. |
Explanation | An exception occurred due to multiple buses having identical UUIDs. |
Action | Ensure that each bus in an administrative domain has a unique UUID. |
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. |
Explanation | A suitable messaging engine name could not be created. |
Action | Try specifying different configuration data when creating the messaging engine. |
Explanation | An exception occurred due to multiple destinations having identical UUIDs. |
Action | Ensure that each destination in an administrative domain has a unique UUID. |
Explanation | An exception occurred retrieving the SIB Services for the messaging server. |
Action | Ensure that a SIB Service exists for the messaging server. |
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. |
Explanation | The createDefaultDatasource flag is only be used with servers. Its use with clusters is not permitted. |
Action | Execute the command again, this time omitting the createDefaultDatasource parameter. |
Explanation | Either the specified parameter was not supplied, or no value was supplied for it. |
Action | Execute the command again, this time supplying the missing parameter value. |
Explanation | The value supplied for the specified parameter of the specified command was not valid. |
Action | Execute the command again, this time supply a valid value. |
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. |
Explanation | An internal error occurred while trying to determine values for "reliability" and "maxReliability". |
Action | Report this problem to your system administrator. |
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. |
Explanation | The value supplied for the specified parameter was not recognized. |
Action | Execute the command again, this time supplying a valid value. |
Explanation | The destination name supplied to the createSIBDestination command is not valid. |
Action | Supply a valid destination name. |
Explanation | The value supplied for the specified parameter was not valid. |
Action | Execute the command again, this time supply a valid value. |
Explanation | The node, server and/or cluster parameters should not be specified when type is "WebServices". |
Action | Execute the command again, this time supply a valid combination of parameters. |
Explanation | An internal error occurred while validating reliability and maxReliability. |
Action | Report this problem to your system administrator. |
Explanation | {1} is a prereq of {0} being set |
Action | Either dont specify {0} or specify both {0} and {1} |
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. |
Explanation | You can not create a foreign destination by setting the foreign bus value to be the local bus |
Action | Select a foreign bus for the foreign bus value |
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. |
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. |
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. |
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. |
Explanation | An incorrect type has been found for the connection factory. |
Action | Ensure that the connection factory type is either Queue, Topic or All. |
Explanation | The command was executed but no result object was returned. |
Action | Ensure that the correct configuration information has been passed to the command being executed. |
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. |
Explanation | The interface of the target object is not of type Queue. |
Action | Ensure that the target object is of type Queue. |
Explanation | The interface of the target object is not of type Topic. |
Action | Ensure that the target object is of type Topic. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | An illegal value has been provided for the JMS connection factory property specified. |
Action | Ensure that the value specified is legal for the given property. |
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. |
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. |
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/. |
Explanation | The named ActivationSpec already exists on the specified resource adapter. |
Action | Ensure that ActivationSpec objects are unique within a given scope. |
Explanation | The create command was executed but no result object was returned. |
Action | Ensure that the correct configuration information has been passed to the create command being executed. |
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. |
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. |
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. |
Explanation | The target object specified is not of the correct type. |
Action | Ensure that the target object is of type JMS ActivationSpec. |
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. |
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. |
Explanation | The bus 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. |
Explanation | The user has entered a value for the read ahead property which is not valid |
Action | Check the documentation for a valid value |
Explanation | The user has entered a value for the destination type property which is not valid |
Action | Check the documentation for a valid value |
Explanation | The mediation specified already exists within the administrative domain. |
Action | Ensure that all mediations are uniquely identified within an administrative domain. |
Explanation | The mediation specified could not be found within the administrative domain. |
Action | Ensure that the mediation specified to the command exists. |
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. |
Explanation | The destination specified could not be found within the administrative domain. |
Action | Ensure that the destination specified exists. |
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. |
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. |
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. |
Explanation | An inconsistent configuration has been detected. |
Action | Run cross document validation to check the destination configuration. |
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. |
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. |
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. |
Explanation | The configuration archive does not contain any cells. |
Action | Make sure that the configuration archive contains a cell. |
Explanation | The deployment manager configuration does not contain any cells. |
Action | Make sure that the deployment manager configuration contains a cell. |
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. |
Explanation | The configuration does not contain any cells. |
Action | Make sure that the configuration contains a cell. |
Explanation | No cells were found in the deployment manager configuration. |
Action | Ensure that the deployment manager configuration contains a cell definition. |
Explanation | Internal error. Method invoked requires a deployment manager configuration session parameter. |
Action | Please contact your system administrator to resolve this problem. |
Explanation | Internal error. Method invoked requires a cell object, |
Action | Please contact your system administrator to resolve this problem. |
Explanation | Internal error. Method invoked requires a bus object. |
Action | Please contact your system administrator to resolve this problem. |
Explanation | Internal error. Method invoked requires destination object. |
Action | Please contact your system administrator to resolve this problem. |
Explanation | Internal error. The specified command did not return a result. |
Action | Please contact your system administrator to resolve this problem. |
Explanation | Internal error. The application server template ID is null. |
Action | Please contact your system administrator to resolve this problem. |