WebSphere Process Server messages     Operating Systems: All supported

CWSJR

CWSJR1021E: An internal error has occurred. The exception {0} in method {1}.
Problem The included exception information can be used for diagnosis.
User response 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/.
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}.
Problem An internal error has occurred. The included exception information can be used for diagnosis.
User response 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/.
CWSJR1023E: An internal error has occurred. A valid SICoreConnectionFactory cannot be retrieved during a call to the method {0}.
Problem This exception is unexpected. The cause is not immediately known.
User response 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/.
CWSJR1024E: An internal error has occurred. During the call to the method {0} an unexpected object of type, {2}, was received instead of {1}.
Problem An internal error has occurred. The JmsFactoryFactory.getInstance() method did not receive a correct JMSRAFactoryFactory type as expected.
User response 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/.
CWSJR1025E: The prefix {0} is longer than twelve characters.
Problem The prefix for temporary destination names may not be longer than twelve characters.
User response Specify a prefix that is twelve characters or less.
CWSJR1026E: An internal error has occurred. The exception {0} was received in method {1}.
Problem The included exception information can be used for diagnosis.
User response 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/.
CWSJR1027E: An internal error has occurred. The exception {0} was received in method {1}.
Problem The included exception information can be used for diagnosis.
User response 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/.
CWSJR1028E: An internal error has occurred. The exception {0} was received in method {1}.
Problem The included exception information can be used for diagnosis.
User response 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/.
CWSJR1029E: The prefix {0} is longer than twelve characters.
Problem The prefix for temporary destination names may not be longer than twelve characters.
User response 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}.
Problem This exception is unexpected. The cause is not immediately known.
User response 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/.
CWSJR1064E: An internal error has occurred. The exception {0} was received in method {1}.
Problem The included exception information can be used for diagnosis.
User response 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/.
CWSJR1065E: An internal error has occurred. The exception {0} was received in method {1}.
Problem The included exception information can be used for diagnosis.
User response 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/.
CWSJR1066E: A valid SICoreConnectionFactory cannot be retrieved during a call to the method {0}.
Problem This exception is unexpected. The cause is not immediately known.
User response 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/.
CWSJR1067E: The following JCA Connection error has occurred when trying to get the connetion. The retrieving of the connection will be retried. The exception is {0}.
Problem An error has been caught whilst obtaining a connection. The system will purge the connection and attempt to obtain another one.
User response 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/.
CWSJR1082E: An internal error has occurred during the call to the method {0}. Exactly one session was expected but {1} sessions were found.
Problem The set of sessions in the connection has more than one session when there should only be one.
User response 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/.
CWSJR1083E: An internal error has occurred during the call to the method {0}. A {1} object was found when a {2} object was expected.
Problem An object was found in the set of sessions which was not of the type required.
User response 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/.
CWSJR1084E: An internal error has occurred during the call to the method {0}. A {1} object was found when a {2} object was expected.
Problem An object was found in the set of sessions which was not of the type required.
User response 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/.
CWSJR1085E: An internal error has occurred. A call was made to the method {0} after the connection was closed.
Problem The method cannot be called after the connection is closed.
User response 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/.
CWSJR1086E: An internal error has occurred. A call was made to the method {0} after the connection was closed.
Problem The method cannot be called after the connection is closed.
User response 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/.
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.
Problem The request information is not of the correct type.
User response 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/.
CWSJR1102E: An internal error has occurred. The exception {0} was thrown
Problem The call to the lazyEnlist method on the connection manager failed.
User response 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/.
CWSJR1103E: The credentials ({2}) passed to the method {0} did not match those passed to the constructor ({1}).
Problem The supplied credentials resulted in an authentication failure.
User response 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/.
CWSJR1104E: An internal error has occurred during the call to the method {0}. A {2} object was received instead of a {1} object.
Problem An object of the wrong type was received.
User response 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/.
CWSJR1105E: An internal error has occurred. An attempt was made to start a local transaction when such a transaction already existed.
Problem It is not possible to start a local transaction if one already exists.
User response 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/.
CWSJR1106E: An internal error has occurred during the call to the method {0}. A required SICoreConnection object was not found.
Problem A SICoreConnection object is required but cannot be found.
User response 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/.
CWSJR1107E: An internal error has occurred during the call to the method {0}. A required SICoreConnection object was not found.
Problem A SICoreConnection object is required but cannot be found.
User response 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/.
CWSJR1108E: A messaging engine name must be specified to use JMS resources within a transaction.
Problem Outside of a WebSphere application server a messaging engine name must be explicitly stated during connection factory configuration in order to support transactional usage.
User response Change the connection factory configuration to specify a remoteTargetType of "ME" and a remoteTargetGroup containing the name of the messaging engine to connect to.
CWSJR1110E: An internal error has occurred. Exception: {0} in method {1}
Problem The included exception information can be used for diagnosis.
User response 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/.
CWSJR1111E: An internal error has occurred. Exception: {0} in method {1}
Problem The included exception information can be used for diagnosis.
User response 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/.
CWSJR1112E: An internal error has occurred. Exception: {0} in method {1}
Problem The included exception information can be used for diagnosis.
User response 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/.
CWSJR1113E: An internal error has occurred. Exception: {0} in method {1}
Problem The included exception information can be used for diagnosis.
User response 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/.
CWSJR1114E: An internal error has occurred. Exception: {0} in method {1}
Problem The included exception information can be used for diagnosis.
User response 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/.
CWSJR1117E: An internal error has occurred. The credentials passed to the method {0} did not match those passed to the constructor.
Problem The supplied credentials resulted in an authentication failure.
User response 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/.
CWSJR1121E: An internal error has occurred. During the call to the method {0} the exception {1} was thrown.
Problem An unexpected exception was thrown when the session tried to re-associate itself with a connection manager.
User response 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/.
CWSJR1122E: An internal error has occurred. During the call to the method {0} we expected to receive a {2} but received a {1}
Problem The connection manager is not lazy enlistable.
User response 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/.
CWSJR1123E: An internal error has occurred. A call was made to {0} after the session closed.
Problem The method cannot be called after the session is closed.
User response 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/.
CWSJR1124E: An internal error has occurred. A call was made to {0} after the session was invalidated.
Problem The method call is not allowed after the session is invalidated.
User response 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/.
CWSJR1125E: An internal error has occurred. A call was made to {0} but there is no local transaction.
Problem The method call is not allowed if there is no local transaction.
User response 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/.
CWSJR1126E: An internal error has occurred. The call to the method {0} is not allowed because of the nonmanaged environment.
Problem The call is not allowed in a nonmanaged environment.
User response 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/.
CWSJR1130E: An internal error has occurred. A call was made to {0} after the session closed.
Problem The method cannot be called after the session is closed.
User response 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/.
CWSJR1131E: An internal error has occurred. A call was made to {0} after the session closed.
Problem The method cannot be called after the session is closed.
User response 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/.
CWSJR1132E: An internal error has occurred. A call was made to {0} after the session closed.
Problem The method cannot be called after the session is closed.
User response 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/.
CWSJR1133E: An internal error has occurred. A call was made to {0} after the session closed.
Problem The method cannot be called after the session is closed.
User response 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/.
CWSJR1134E: An internal error has occurred. A call was made to {0} after the session was invalidated.
Problem The method call is not allowed after the session is invalidated.
User response 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/.
CWSJR1135E: An internal error has occurred. A call was made to {0} after the session was invalidated.
Problem The method call is not allowed after the session is invalidated.
User response 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/.
CWSJR1136E: An internal error has occurred. A call was made to {0} after the session was invalidated.
Problem The method call is not allowed after the session is invalidated.
User response 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/.
CWSJR1137E: An internal error has occurred. A call was made to {0} after the session was invalidated.
Problem The method call is not allowed after the session is invalidated.
User response 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/.
CWSJR1138E: An internal error has occurred. An unexpected exception has occurred. A call was made to {0} but there is no local transaction.
Problem The method call is not allowed if there is a global transaction active.
User response 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/.
CWSJR1139E: An internal error has occurred. An unexpected exception has occurred. A call was made to {0} but there is no local transaction.
Problem The method call is not allowed if there is no local transaction.
User response 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/.
CWSJR1140E: An internal error has occurred. An unexpected exception has occurred. A call was made to {0} but there is no local transaction.
Problem The method call is not allowed if there is a global transaction active.
User response 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/.
CWSJR1141E: An internal error has occurred. An unexpected exception has occurred. A call was made to {0} but there is no local transaction.
Problem The method call is not allowed if there is no local transaction.
User response 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/.
CWSJR1142E: An internal error has occurred. An unexpected exception has occurred. A call was made to {0} but there is no local transaction.
Problem The method call is not allowed if there is no local transaction.
User response 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/.
CWSJR1161E: An internal error has occurred during initialization of the {1} class. Exception: {0}.
Problem The JmsJcaReferenceUtils class failed to initialize.
User response 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/.
CWSJR1179E: The following target significance field on a JMS activation specification is invalid [{2}]. The values [{0}] or [{1}] are expected.
Problem During validation of the properties configured on a JMS activation specification the target significance was deemed to be invalid
User response The target significance field had an invalid value, correct the value of the property on the activation specification and 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.
Problem During validation of the properties configured on a JMS activation specification the target type was deemed to be invalid
User response The target type field had an invalid value, correct the value of the property on the activation specification and restart the server.
CWSJR1181E: The JMS activation specification has invalid values - the reason(s) for failing to validate the JMS activation specification are: {0}
Problem During validation of the properties configured on a JMS activation specification the given reasons were given as to why the validation failed.
User response One or more invalid properties where found, correct the values of the properties on the JMS activation specification and restart the server.
CWSJR1182E: An internal error. The following exception was thrown while attempting to obtain a utility class: {0}.
Problem During endpoint activation the JMS resource adapter was attempting to obtain a utility class and an unexpected exception was received.
User response 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/.
CWSJR1183E: The client ID field on a JMS Activation specification must be set
Problem During validation of the properties configured on a JMS activation specification the client ID was deemed to be invalid
User response The client ID had an invalid value, correct the value of the property on the activation specification and restart the server.
CWSJR1185E: An internal error has occurred during the validation of a JMS activation specification: {0}.
Problem During the validation of a JMS activation specification an unexpected exception was received.
User response 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/.
CWSJR1186E: An internal error has occurred during the registration of the WLM classifier for the JMS resource adapter: {0}.
Problem During the registration of the WLM classifier for the JMS resource adapter with the handler registry an unexpected exception was received.
User response 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/.
CWSJR1187E: The bus name on a JMS activation specification must be given a value
Problem During validation of the properties configured on a JMS activation specification the bus name was deemed to be invalid
User response The bus name had an invalid value, correct the value of the property on the activation specification and restart the server.
CWSJR1188E: The destination on a JMS activation specification must be given a value
Problem During validation of the properties configured on a JMS activation specification the destination was deemed to be invalid
User response The destination had an invalid value, correct the value of the property on the activation specification and restart the server.
CWSJR1189E: The following destination type on a JMS activation specification is invalid [{2}]. The values [{0}] or [{1}] are expected.
Problem During validation of the properties configured on a JMS activation specification the destination type was deemed to be invalid
User response The destination type had an invalid value, correct the value of the property on the activation specification and restart the server.
CWSJR1190E: The following acknowledge mode on a JMS activation specification is invalid [{2}]. The values [{0}] or [{1}] are expected.
Problem During validation of the properties configured on a JMS activation specification the acknowledge mode was deemed to be invalid
User response The acknowledge mode had an invalid value, correct the value of the property on the activation specification and 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.
Problem During validation of the properties configured on a JMS activation specification the read ahead was deemed to be invalid
User response The read ahead had an invalid value, correct the value of the property on the activation specification and 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}]
Problem During validation of the properties configured on a JMS activation specification the destination was deemed to be invalid
User response The destination had an invalid value, correct the value of the property on the activation specification and restart the server.
CWSJR1193E: JMS ativation specs using a destination type of topic must have a destination of type [{0}] but the destination passed was of type [{1}]
Problem During validation of the properties configured on a JMS activation specification the destination was deemed to be invalid
User response The destination had an invalid value, correct the value of the property on the activation specification and restart the server.
CWSJR1194E: The following subscription durability on a JMS activation specification is invalid [{2}]. The values [{0}] or [{1}] are expected.
Problem During validation of the properties configured on a JMS activation specification the subscription durability was deemed to be invalid
User response The subscription durability had an invalid value, correct the value of the property on the activation specification and restart the server.
CWSJR1195E: The durable subscription home on a JMS activation specification must have a value when using durable subscriptions.
Problem During validation of the properties configured on a JMS activation specification the durable subscription home was deemed to be invalid
User response The durable subscription home had an invalid value, correct the value of the property on the activation specification and restart the server.
CWSJR1196E: The subscription name on a JMS activation specification must have a value when using durable subscriptions
Problem During validation of the properties configured on a JMS activation specification the subscription name was deemed to be invalid
User response The subscription name had an invalid value, correct the value of the property on the activation specification and 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.
Problem During validation of the properties configured on a JMS activation specification the share durable subscription was deemed to be invalid
User response The share durable subscription field had an invalid value, correct the value of the property on the activation specification and restart the server.
CWSJR1199E: The maximum batch size on a JMS activation specification must be given a postive value
Problem During validation of the properties configured on a JMS activation specification the maximum batch size was deemed to be invalid
User response The maximum batch size had an invalid value, correct the value of the property on the activation specification and restart the server.
CWSJR1200E: The share data source with CMP field on a JMS activation specification must be set
Problem During validation of the properties configured on a JMS activation specification the share data source with CMP was deemed to be invalid
User response The share data source with CMP had an invalid value, correct the value of the property on the activation specification and restart the server.
CWSJR1441E: An internal error has occurred. Creation of the JmsJcaFactory object failed with exception: {0}.
Problem A problem occurred while creating the JmsJcaFactory object. Previous messages contain information about the problem.
User response 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/.
CWSJR1461E: An internal error has occurred. Creation of an SIUncoordinatedTransaction failed with exception: {0}
Problem The WebSphere Platform Messaging JMS resource adapter was attempting to create an SIUncoordinatedTransaction to register in a transaction as a Synchronization when an exception occurred.
User response 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/.
CWSJR1462E: The connection to the messaging engine does not support the container-managed persistence sharing optimization.
Problem The connection the WebSphere Platform Messaging JMS resource adapter has obtained does not support the container-managed persistence optimization because it is to a remote messaging engine.
User response Ensure that there is a local messaging engine available for the resource adapter to connect to or disable the sharing optimization on the connection factory definition via WebSphere administration.
CWSJR1463E: An internal error has occurred. The managed connection {0} is already registered as a synchronization in a transaction.
Problem A call to getSynchronization has occurred when the managed connection is already registered as a synchronization in a transaction.
User response 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/.
CWSJR1481E: An internal error. The following exception was thrown while attempting to obtain a utility class: {0}.
Problem During endpoint activation the JMS resource adapter was attempting to obtain a utility class and an unexpected exception was received.
User response 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/.
CWSJR1482E: An internal error occurred. The message endpoint {0} does not implement the expected interface {1}.
Problem The message endpoint factory has returned a message endpoint that does not implement the MessageListener interface as expected.
User response 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/.
CWSJR1483E: An internal error occurred. The exception {0} was thrown while attempting to obtain an instance of the onMessage method.
Problem An exception was thrown during the attempt to obtain an instance of the onMessage method.
User response 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/.
CWSJR9999E: {0}
Problem If the message does not give sufficient information, check previous messages for further help.
User response See previous messages for further information.
Reference topic    

Terms of Use | Feedback

Last updated: Jun 13, 2009 1:00:35 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.sib.api.jmsra.CWSJRMessages.html

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