Express (Distributed operating systems), v8.0 > Reference > Messages
CWSJR
CWSJR1021E: An internal exception was created. The exception {0} in method {1}.
Explanation The included exception information can be used for diagnosis. Action More info at:
CWSJR1022E: An unexpected exception has occurred during the call to the method {0}. An unexpected type of ConnectionRequest object, {2}, was received instead of {1}.
Explanation An internal exception was created. The included exception information can be used for diagnosis. Action More info at:
CWSJR1023E: An internal error has occurred. A valid SICoreConnectionFactory cannot be retrieved during a call to the method {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSJR1024E: An internal error has occurred. During the call to the method {0} an unexpected object of type, {2}, was received instead of {1}.
Explanation An internal exception was created. The JmsFactoryFactory.getInstance() method did not receive a correct JMSRAFactoryFactory type as expected. Action More info at:
CWSJR1025E: The prefix {0} is longer than twelve characters.
Explanation The prefix for temporary destination names cannot be longer than twelve characters. Action Specify a prefix that is twelve characters or less.
CWSJR1026E: An internal error has occurred. The exception {0} was received in method {1}.
Explanation The included exception information can be used for diagnosis. Action More info at:
CWSJR1027E: An internal error has occurred. The exception {0} was received in method {1}.
Explanation The included exception information can be used for diagnosis. Action More info at:
CWSJR1028E: An internal error has occurred. The exception {0} was received in method {1}.
Explanation The included exception information can be used for diagnosis. Action More info at:
CWSJR1029E: The prefix {0} is longer than twelve characters.
Explanation The prefix for temporary destination names cannot be longer than twelve characters. Action Specify a prefix that is twelve characters or less.
CWSJR1061E: An internal error occurred in method {0}. A valid connection was not created; the object {2} was received instead of {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSJR1064E: An internal error has occurred. The exception {0} was received in method {1}.
Explanation The included exception information can be used for diagnosis. Action More info at:
CWSJR1065E: An internal error has occurred. The exception {0} was received in method {1}.
Explanation The included exception information can be used for diagnosis. Action More info at:
CWSJR1066E: A valid SICoreConnectionFactory cannot be retrieved during a call to the method {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSJR1067E: The following JCA Connection error has occurred when trying to get the connection. The retrieving of the connection will be retried. The exception is {0}.
Explanation An exception was created while obtaining a connection. The system will purge the connection, then attempt to obtain another one. Action More info at:
CWSJR1068E: It was not possible to authenticate using the supplied authentication alias, {0}.
Explanation An application used a resource reference to look up a connection factory. The resource reference was configured to use container-managed authentication, but the associated authentication data was not valid. Action Ensure that the authentication alias associated with this resource reference contains valid credentials for the bus.
CWSJR1069E: The supplied user name, {0}, failed to be authenticated.
Explanation An application used a resource reference to look up a connection factory. The resource reference was configured to use application-managed authentication, but the associated component authentication alias data was not valid. Action Ensure that the component authentication alias contains valid credentials for the bus.
CWSJR1070E: It was not possible to authenticate because no authentication alias was specified.
Explanation An application used a resource reference to look up a connection factory. The resource reference was configured to use container-managed authentication, but an authentication alias was not associated with the resource reference. Action Ensure that an authentication alias is associated with this resource reference.
CWSJR1071E: It was not possible to authenticate because no credentials were supplied.
Explanation An application used a resource reference to look up a connection factory. The resource reference was configured to use application-managed authentication, but no component authentication alias data was specified. Action Ensure that an authentication alias is associated with this resource reference.
CWSJR1072E: The supplied user name, {0}, could not be authenticated.
Explanation An application used a resource reference to look up a connection factory. The resource reference was configured to use application-managed authentication, but the application supplied credentials that are not valid. Action Ensure that the correct credentials are supplied when creating a connection.
CWSJR1073E: It was not possible to authenticate using the supplied authentication alias, {0}.
Explanation An application used a resource reference to look up a connection factory. The resource reference was configured to use container-managed authentication, but the associated authentication data was not valid. Action Ensure that the authentication alias associated with this resource reference contains valid credentials for the bus.
CWSJR1074E: The supplied user name, {0}, failed to be authenticated.
Explanation An application used a resource reference to look up a connection factory. The resource reference was configured to use application-managed authentication, but the associated component authentication alias data was not valid. Action Ensure that the component authentication alias contains valid credentials for the bus.
CWSJR1075E: It was not possible to authenticate because no authentication alias was specified.
Explanation An application used a resource reference to look up a connection factory. The resource reference was configured to use container-managed authentication, but an authentication alias was not associated with the resource reference. Action Ensure that an authentication alias is associated with this resource reference.
CWSJR1076E: It was not possible to authenticate because no credentials were supplied.
Explanation An application used a resource reference to look up a connection factory. The resource reference was configured to use application-managed authentication, but no component authentication alias data was specified. Action Ensure that an authentication alias is associated with this resource reference.
CWSJR1082E: An internal error has occurred during the call to the method {0}. Exactly one session was expected but {1} sessions were found.
Explanation The set of sessions in the connection has more than one session when there should only be one. Action More info at:
CWSJR1083E: An internal error has occurred during the call to the method {0}. A {1} object was found when a {2} object was expected.
Explanation An object found in the set of sessions was not of the type required. Action More info at:
CWSJR1084E: An internal error has occurred during the call to the method {0}. A {1} object was found when a {2} object was expected.
Explanation An object found in the set of sessions was not of the type required. Action More info at:
CWSJR1085E: An internal error has occurred. A call was made to the method {0} after the connection was closed.
Explanation The method cannot be called after the connection is closed. Action More info at:
CWSJR1086E: An internal error has occurred. A call was made to the method {0} after the connection was closed.
Explanation The method cannot be called after the connection is closed. Action More info at:
CWSJR1101E: An internal error has occurred during the call to the method {0}. The connection failed because a {2} object was found when a {1} object was expected.
Explanation The request information is not of the correct type. Action More info at:
CWSJR1102E: An internal error has occurred. The exception {0} was thrown.
Explanation The call to the lazyEnlist method on the connection manager was not successful. Action More info at:
CWSJR1103E: The credentials ({2}) passed to the method {0} did not match those passed to the constructor ({1}).
Explanation The supplied credentials did not pass the authentication check. Action More info at:
CWSJR1104E: An internal error has occurred during the call to the method {0}. A {2} object was received instead of a {1} object.
Explanation An object of the wrong type was received. Action More info at:
CWSJR1105E: An internal error has occurred. An attempt was made to start a local transaction when such a transaction already existed.
Explanation It is not possible to start a local transaction if one already exists. Action More info at:
CWSJR1106E: An internal error has occurred during the call to the method {0}. A required SICoreConnection object was not found.
Explanation A SICoreConnection object is required but cannot be found. Action More info at:
CWSJR1107E: An internal error has occurred during the call to the method {0}. A required SICoreConnection object was not found.
Explanation A SICoreConnection object is required but cannot be found. Action More info at:
CWSJR1108E: A specific messaging engine must be specified to use JMS resources within a transaction. The connection property {0} must be set to {1}.
Explanation To permit recovery of transactions, a connection factory must target a specific messaging engine in the bus. Action Change the connection factory property 'Target' value to the string value of the name of the target messaging engine, 'Target type' to the pull down value 'Messaging engine name' and 'Target significance' to the pull down value of 'Required'.
CWSJR1110E: An internal error has occurred. Exception: {0} in method {1}
Explanation The included exception information can be used for diagnosis. Action More info at:
CWSJR1111E: An internal error has occurred. Exception: {0} in method {1}
Explanation The included exception information can be used for diagnosis. Action More info at:
CWSJR1112E: An internal error has occurred. Exception: {0} in method {1}
Explanation The included exception information can be used for diagnosis. Action More info at:
CWSJR1113E: An internal error has occurred. Exception: {0} in method {1}
Explanation The included exception information can be used for diagnosis. Action More info at:
CWSJR1114E: An internal error has occurred. Exception: {0} in method {1}
Explanation The included exception information can be used for diagnosis. Action More info at:
CWSJR1117E: An internal error has occurred. The credentials passed to the method {0} did not match those passed to the constructor.
Explanation The supplied credentials did not pass the authentication check. Action More info at:
CWSJR1121E: An internal error has occurred. During the call to the method {0} the exception {1} was thrown.
Explanation An unexpected exception was created when the session tried to re-associate itself with a connection manager. Action More info at:
CWSJR1122E: An internal error has occurred. During the call to the method {0} we expected to receive a {2} but received a {1}
Explanation The connection manager is not lazy enlistable. Action More info at:
CWSJR1123E: An internal error has occurred. A call was made to {0} after the session closed.
Explanation The method cannot be called after the session is closed. Action More info at:
CWSJR1124E: An internal error has occurred. A call was made to {0} after the session was invalidated.
Explanation The method call is not allowed when the session is no longer valid. Action More info at:
CWSJR1125E: An internal error has occurred. A call was made to {0} but there is no local transaction.
Explanation The method call is not allowed if there is no local transaction. Action More info at:
CWSJR1126E: An internal error has occurred. The call to the method {0} is not allowed because of the nonmanaged environment.
Explanation The call is not allowed in an unmanaged environment. Action More info at:
CWSJR1130E: An internal error has occurred. A call was made to {0} after the session closed.
Explanation The method cannot be called after the session is closed. Action More info at:
CWSJR1131E: An internal error has occurred. A call was made to {0} after the session closed.
Explanation The method cannot be called after the session is closed. Action More info at:
CWSJR1132E: An internal error has occurred. A call was made to {0} after the session closed.
Explanation The method cannot be called after the session is closed. Action More info at:
CWSJR1133E: An internal error has occurred. A call was made to {0} after the session closed.
Explanation The method cannot be called after the session is closed. Action More info at:
CWSJR1134E: An internal error has occurred. A call was made to {0} after the session was invalidated.
Explanation The method call is not allowed when the session is no longer valid. Action More info at:
CWSJR1135E: An internal error has occurred. A call was made to {0} after the session was invalidated.
Explanation The method call is not allowed when the session is no longer valid. Action More info at:
CWSJR1136E: An internal error has occurred. A call was made to {0} after the session was invalidated.
Explanation The method call is not allowed when the session is no longer valid. Action More info at:
CWSJR1137E: An internal error has occurred. A call was made to {0} after the session was invalidated.
Explanation The method call is not allowed when the session is no longer valid. Action More info at:
CWSJR1138E: An internal error has occurred. An unexpected exception has occurred. A call was made to {0} but there is no local transaction.
Explanation The method call is not allowed if a global transaction is active. Action More info at:
CWSJR1139E: An internal error has occurred. An unexpected exception has occurred. A call was made to {0} but there is no local transaction.
Explanation The method call is not allowed if there is no local transaction. Action More info at:
CWSJR1140E: An internal error has occurred. An unexpected exception has occurred. A call was made to {0} but there is no local transaction.
Explanation The method call is not allowed if a global transaction is active. Action More info at:
CWSJR1141E: An internal error has occurred. An unexpected exception has occurred. A call was made to {0} but there is no local transaction.
Explanation The method call is not allowed if there is no local transaction. Action More info at:
CWSJR1142E: An internal error has occurred. An unexpected exception has occurred. A call was made to {0} but there is no local transaction.
Explanation The method call is not allowed if there is no local transaction. Action More info at:
CWSJR1161E: An internal error has occurred during initialization of the {1} class. Exception: {0}.
Explanation The JmsJcaReferenceUtils class did not initialize. Action More info at:
CWSJR1179E: The following target significance field on a JMS activation specification is invalid [{2}]. The values [{0}] or [{1}] are expected.
Explanation During validation of the properties configured on a JMS activation specification, the target significance property was found not to be valid. Action Correct the value of the target significance property on the activation specification, then restart the server.
CWSJR1180E: The following target type field on a JMS activation specification is invalid [{3}]. The values [{0}], [{1}] or [{2}] are expected.
Explanation During validation of the properties configured on a JMS activation specification, the target type was found not to be valid. Action Correct the value of the target type property on the activation specification, then restart the server.
CWSJR1181E: The JMS activation specification has invalid values - the reason(s) for failing to validate the JMS activation specification are: {0}
Explanation During validation of the properties configured on a JMS activation specification, one or more properties were found that are not valid. Action Correct the values of the properties on the JMS activation specification, then restart the server.
CWSJR1182E: An internal error. The following exception was thrown while attempting to obtain a utility class: {0}
Explanation During endpoint activation the JMS resource adapter was attempting to obtain a utility class and an unexpected exception was received. Action More info at:
CWSJR1183E: The client ID field on a JMS Activation specification must be set
Explanation During validation of the properties configured on a JMS activation specification, the client ID was found not to be valid. Action Correct the value of the client ID property on the activation specification, then restart the server.
CWSJR1185E: An internal error has occurred during the validation of a JMS activation specification: {0}.
Explanation During the validation of a JMS activation specification an unexpected exception was received. Action More info at:
CWSJR1186E: An internal error has occurred during the registration of the WLM classifier for the JMS resource adapter: {0}.
Explanation During the registration of the WLM classifier for the JMS resource adapter with the handler registry, an unexpected exception was received. Action More info at:
CWSJR1187E: The bus name on a JMS activation specification must be given a value
Explanation During validation of the properties configured on a JMS activation specification, the bus name was found not to be valid. Action Correct the value of the bus name property on the activation specification, then restart the server.
CWSJR1188E: The destination on a JMS activation specification must be given a value
Explanation During validation of the properties configured on a JMS activation specification, the destination was found not to be valid. Action Correct the value of the destination property on the activation specification, then restart the server.
CWSJR1189E: The following destination type on a JMS activation specification is invalid [{2}]. The values [{0}] or [{1}] are expected.
Explanation During validation of the properties configured on a JMS activation specification, the destination type was found not to be valid. Action Correct the value of the destination type property on the activation specification, then restart the server.
CWSJR1190E: The following acknowledge mode on a JMS activation specification is invalid [{2}]. The values [{0}] or [{1}] are expected.
Explanation During validation of the properties configured on a JMS activation specification, the acknowledge mode was found not to be valid. Action Correct the value of the acknowledge mode property on the activation specification, then restart the server.
CWSJR1191E: The following read ahead value on a JMS activation specification is invalid [{3}]. The values [{0}], [{1}] or [{2}] are expected.
Explanation During validation of the properties configured on a JMS activation specification, the read ahead value was found not to be valid. Action Correct the value of the read ahead property on the activation specification, then restart the server.
CWSJR1192E: JMS activation specs using a destination type of queue must have a destination of type [{0}] but the destination passed was of type [{1}]
Explanation During validation of the properties configured on a JMS activation specification, the destination was found not to be valid. Action Correct the value of the destination property on the activation specification, then restart the server.
CWSJR1193E: JMS activation specs using a destination type of topic must have a destination of type [{0}] but the destination passed was of type [{1}]
Explanation During validation of the properties configured on a JMS activation specification, the destination was found not to be valid. Action Correct the value of the destination property on the activation specification, then restart the server.
CWSJR1194E: The following subscription durability on a JMS activation specification is invalid [{2}]. The values [{0}] or [{1}] are expected.
Explanation During validation of the properties configured on a JMS activation specification, the subscription durability was found not to be valid. Action Correct the value of the subscription durability property on the activation specification, then restart the server.
CWSJR1195E: The durable subscription home on a JMS activation specification must have a value when using durable subscriptions.
Explanation During validation of the properties configured on a JMS activation specification, the durable subscription home was found not to be valid. Action Correct the value of the durable subscription home property on the activation specification, then restart the server.
CWSJR1196E: The subscription name on a JMS activation specification must have a value when using durable subscriptions
Explanation During validation of the properties configured on a JMS activation specification, the subscription name was found not to be valid. Action Correct the value of the subscription name property on the activation specification, then restart the server.
CWSJR1197E: The following share durable subscription field on a JMS activation specification is invalid [{3}]. The values [{0}], [{1}] or [{2}] are expected.
Explanation During validation of the properties configured on a JMS activation specification, the share durable subscription property was found not to be valid. Action Correct the value of the share durable subscription property on the activation specification, then restart the server.
CWSJR1198E: The maximum concurrency on a JMS activation specification must be given a postive value
Explanation During validation of the properties configured on a JMS activation specification, the maximum concurrency value was found not to be valid. Action Correct the value of the maximum concurrency property on the activation specification, then restart the server.
CWSJR1199E: The maximum batch size on a JMS activation specification must be given a postive value
Explanation During validation of the properties configured on a JMS activation specification, the maximum batch size was found not to be valid. Action Correct the value of the maximum batch size property on the activation specification, then restart the server.
CWSJR1200E: The share data source with CMP field on a JMS activation specification must be set
Explanation During validation of the properties configured on a JMS activation specification, the share data source with CMP was found not to be valid. Action Correct the value of the share data source with CMP property on the activation specification, then restart the server.
CWSJR1441E: An internal error has occurred. Creation of the JmsJcaFactory object failed with exception: {0}.
Explanation A problem occurred while creating the JmsJcaFactory object. See the accompanying error messages for further information. Action More info at:
CWSJR1461E: An internal error has occurred. Creation of an SIUncoordinatedTransaction failed with exception: {0}
Explanation The service integration technologies JMS resource adapter was attempting to create an SIUncoordinatedTransaction to register in a transaction as a Synchronization when an exception was received. Action More info at:
CWSJR1462E: The connection to the messaging engine does not support the container-managed persistence sharing optimization.
Explanation The connection the service integration technologies JMS resource adapter has obtained does not support the container-managed persistence optimization because it is to a remote messaging engine. Action Ensure that there is a local messaging engine available to which the resource adapter can connect, or disable the sharing optimization on the connection factory definition using the administrative console.
CWSJR1463E: An internal error has occurred. The managed connection {0} is already registered as a synchronization in a transaction.
Explanation A call to getSynchronization has occurred when the managed connection is already registered as a synchronization in a transaction. Action More info at:
CWSJR1481E: An internal error. The following exception was thrown while attempting to obtain a utility class: {0}.
Explanation During endpoint activation the JMS resource adapter was attempting to obtain a utility class and an unexpected exception was received. Action More info at:
CWSJR1482E: An internal error occurred. The message endpoint {0} does not implement the expected interface {1}.
Explanation The message endpoint factory has returned a message endpoint that does not implement the MessageListener interface as expected. Action More info at:
CWSJR1483E: An internal error occurred. The exception {0} was thrown while attempting to obtain an instance of the onMessage method.
Explanation An exception was created during the attempt to obtain an instance of the onMessage method. Action More info at:
CWSJR9999E: {0}
Explanation If the message does not give sufficient information, see the accompanying error messages for further information. Action See the accompanying error messages for further information.