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


CWSIA

CWSIA0001E: An internal error occurred. An object of class {0} can not be created because the JAR file {1} could not be found.
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/.
CWSIA0002E: An internal error occurred. It was not possible to instantiate a required class: {0}
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/.
CWSIA0003E: The specified value {1} is not allowed for {0}.
Explanation The given value is not allowed for the property specified.
Action Change the value to a value that is supported for the property.
CWSIA0004E: The authentication for the supplied user name and the associated password was not successful.
Explanation The user name and password supplied are not correct.
Action See the linked exception for the user name and check that the user name and password are correct and have been defined to the system.
CWSIA0005E: The JCA runtime failed to allocate a connection.
Explanation An attempt to create a JMS connection failed due to an exception from the JCA runtime.
Action See the linked exception for more information.
CWSIA0006E: The authorization for the supplied user name was not successful.
Explanation The user name is not authorized to access the resource.
Action See the linked exception for the user name and ensure that it is correctly authorized to the required resource on the system.
CWSIA0007E: An exception was received during the call to the method {1}: {0}.
Explanation During execution of the specified method an exception was thrown by another component.
Action See the linked exception for more information.
CWSIA0008E: An internal error occurred. An object of class {0} can not be created because the JAR file {1} could not be found.
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/.
CWSIA0021E: This connection is closed.
Explanation An application called a method that must not be used after the connection is closed.
Action Ensure that the connection is not closed before calling the method.
CWSIA0022E: An exception was received during the call to the method {1}: {0}.
Explanation During execution of the specified method an exception was thrown by another component.
Action See the linked exception for more information.
CWSIA0023E: The client ID for this connection is read-only.
Explanation An application has tried to set the client ID after it has previously been set or administratively configured.
Action Ensure that the client ID is not set after it has been previously set or configured.
CWSIA0024E: The JCA runtime failed to create a session.
Explanation A call into the JCA runtime to create a session generated an exception.
Action Examine the linked exception for further information.
CWSIA0025E: The method {0} is not permitted in this container.
Explanation A method was called that is not permitted in the current container.
Action Remove the call to the method.
CWSIA0026E: {0} is not supported in this release.
Explanation The application has attempted to use a feature or capability that is not supported by the current release of the software.
Action Remove the code that attempts to use this capability or update to a later release of the software if available.
CWSIA0041E: Connection closed
Explanation The connection was closed during the execution of this method.
Action Repeat the call using a new connection.
CWSIA0042E: It is not valid to call the {0} method on a nontransacted session.
Explanation The application called a method that must not be called on a nontransacted session.
Action Change the application program to remove this behavior.
CWSIA0043E: Subscription locked
Explanation It was not possible to unsubscribe from the durable subscription. This may happen if there is an active subscriber attached to the subscription, or the subscription holds messages that are under transaction.
Action Ensure that there is no active subscriber and retry the unsubscribe method.
CWSIA0044E: Not authorised to unsubscribe durable subscription
Explanation The current user does not have authorisation to unsubscribe the durable subscription.
Action Check the userID has the required access to the resources needed. See the linked exception for more details.
CWSIA0045E: The optional JMS operation {0} is not supported by this implementation.
Explanation The application called a method that is optional in the JMS specification, and which is not supported by this implementation.
Action Remove calls to the named methods from the application.
CWSIA0046E: The parameter {0} is from a foreign implementation that is not supported.
Explanation The user application passed in an implementation class from an unsupported JMS provider.
Action Replace the unsupported object with one that is supported.
CWSIA0047E: The name {1} does not describe an object of type {0}.
Explanation A queue name was supplied to a createTopic call or vice versa.
Action Alter the name so that it correctly describes the object type.
CWSIA0048E: The specified value {1} is not allowed for {0}.
Explanation The given value is not allowed for the property specified.
Action Change the value to a value that is supported for the property.
CWSIA0049E: This session is closed.
Explanation An application called a method that must not be used after the session is closed.
Action Ensure that the session in not closed before calling the method.
CWSIA0050E: It is not valid to call the {0} method on a transacted session.
Explanation The application called a method that must not be called on a transacted session.
Action Change the application program to remove this behavior.
CWSIA0051E: This connection associated with this session is closed.
Explanation The application call a method on a session object for which the associated Connection has been closed.
Action Ensure that the connection is not closed before calling the method.
CWSIA0052E: The destination {0} does not exist.
Explanation The application tried to connect to a destination that is not defined.
Action Correctly define the required destination and repeat the operation.
CWSIA0053E: An exception was received during the call to the method {1}: {0}.
Explanation During execution of the specified method an exception was thrown by another component.
Action See the linked exception for more information.
CWSIA0054E: The durable subscription with subscription name {0} does not exist.
Explanation The application tried to unsubscribe a durable subscription which does not exist.
Action No action is required unless the application expected the subscription to exist, in which case it should previously have created it.
CWSIA0055E: The method {0} is not permitted in this container.
Explanation A method was called that is not permitted in the current container.
Action Remove the call to the method.
CWSIA0056E: A null or empty value was specified for the durableSubscriptionHome property of the ConnectionFactory
Explanation It is mandatory to set the durableSubscriptionHome property before creating a connection that will use durable subscribers
Action Set the ConnectionFactory durableSubscriptionHome property to the name of the messaging engine on which the subscription should be localized.
CWSIA0057E: The authorization for {0} was not successful.
Explanation The user name is not authorized to access the resource.
Action See the linked exception for more detail. Check that the user name is correctly authorized to the required resource on the system.
CWSIA0058E: Temporary topic locked
Explanation The temporary topic could not be deleted. It may have active subscribers.
Action Close any subscribers to the topic and retry the call.
CWSIA0061E: This message producer is closed.
Explanation An application called a method that must not be used after the message producer is closed.
Action Ensure that the message producer is not closed before calling the method.
CWSIA0062E: Failed to create a MessageProducer for {0}
Explanation A problem was encountered whilst creating a MessageProducer.
Action See the linked exception for more information.
CWSIA0063E: Failed to send to {0}
Explanation A problem was encountered whilst sending a messsage.
Action See the linked exception for more information.
CWSIA0065E: A destination must be specified when sending from this producer.
Explanation The producer was created with a null destination and a destination was not supplied on the send method.
Action Change the application so that a send method that specifies a destination is used, or specify a destination when creating the producer.
CWSIA0066E: It is not valid to specify a destination when sending from this producer.
Explanation The producer was created with a specified destination; it is not valid to specify a destination again when sending a message.
Action Change the application so that a send method that does not specify a destination is used, or specify a null destination when creating the producer.
CWSIA0067E: An exception was received during the call to the method {1}: {0}.
Explanation During execution of the specified method an exception was thrown by another component.
Action See the linked exception for more information.
CWSIA0068E: The specified value {1} is not allowed for {0}.
Explanation The given value is not allowed for the property specified.
Action Change the value to a value that is supported for the property.
CWSIA0069E: The user does not have authorization to carry out this operation. See the linked exception for details.
Explanation The linked exception contains details of the authority that is required to carry out this operation.
Action The administrator must grant the required authority to the relevant user.
CWSIA0081E: This message consumer is closed.
Explanation An application called a method that must not be used after the message consumer is closed.
Action Ensure that the message consumer is not closed before calling the method.
CWSIA0082E: Synchronous method call not permitted when a session is being used asynchronously: {0}
Explanation The JMS specification does not permit the use of a session for synchronous methods when asynchronous message delivery is running.
Action Create a separate session if you wish to use both synchronous methods and asynchronous delivery simultaneously.
CWSIA0083E: The selector is not valid.
Explanation A message selector was supplied that was incorrect.
Action See the linked exception for more information.
CWSIA0084E: The method {0} is not permitted in this container.
Explanation A method was called that is not permitted in the current container.
Action Remove the call to the method.
CWSIA0085E: An exception was received during the call to the method {1}: {0}.
Explanation During execution of the specified method an exception was thrown by another component.
Action See the linked exception for more information.
CWSIA0086E: Failed to create a MessageConsumer for {0}
Explanation A problem was encountered whilst creating a MessageConsumer.
Action See the linked exception for more information.
CWSIA0087W: An attempt was made to consume a message while the connection was stopped - {0}
Explanation A stopped connection will not deliver messages to message consumers. An attempt to consume messages from a stopped connection may indicate an error in the application logic.
Action Check to see if consuming from a stopped connection is an expected behaviour of the application. Correct the application design if it is not.
CWSIA0089E: A RuntimeException was thrown by MessageListener.onMessage
Explanation A MessageConsumer with a registered MessageListener received an exception from the onMessage method.
Action The onMessage method should be changed to avoid throwing exceptions.
CWSIA0090E: The user does not have authorization to carry out this operation. See the linked exception for details.
Explanation The linked exception contains details of the authority that is required to carry out this operation.
Action The administrator must grant the required authority to the relevant user.
CWSIA0102E: The type {0} is not valid for use as object property {1}.
Explanation An application tried to set an object property using an object type that is not permitted by the JMS specification.
Action Use a permitted object type, which are the primitive wrapper classes or String objects.
CWSIA0103E: An exception occurred while receiving a message: {0}.
Explanation While receiving a message an exception was thrown that caused the operation to fail.
Action Examine the specified exception, and linked exception object for more information.
CWSIA0104E: The conversion of the item {0} from type {1} to type {2} is not permitted.
Explanation Conversion between the two specified data types is not permitted by the JMS specification.
Action Retrieve the named item using one of the permitted conversions.
CWSIA0105E: The message field {0} has not been set.
Explanation An application attempted to retrieve the value of a field that has not been set.
Action Set the value of the field before retrieving it.
CWSIA0106E: A null or empty string field name is not permitted.
Explanation A user application has attempted to set a field using a name that is not valid, for example, null or empty String.
Action Use a valid field name.
CWSIA0107E: It is not permitted to call method {0} on the message because the message body is read-only.
Explanation A user application has attempted to set a read-only message body.
Action Change the application program to remove this behavior, or call the clearBody method first.
CWSIA0108E: It is not permitted to call method {0} on the message because the message properties are read-only.
Explanation A user application has attempted to set a read-only message property.
Action Change the application program to remove this behavior, or call the clearProperties method first.
CWSIA0109E: It is not permitted to call method {0} on the message because the message body is write-only.
Explanation A user application has attempted to read a write-only message body.
Action Change the application program to remove this behavior, or call the reset method first.
CWSIA0110E: It is only permitted to call the operation {0} on a message that was obtained using a receive call, or a message presented to a MessageListener.
Explanation The message has either been constructed by the application, or has been obtained using a queue browser, and so does not support the stated operation.
Action Ensure that applications only invoke this operation on messages obtained via a receive call, or on messages presented to a MessageListener.
CWSIA0111E: An error occurred while trying to create the message. See the linked exception for more details.
Explanation It was not possible to create the message due to an error.
Action Examine the linked exception for details of the error.
CWSIA0112E: The property name {0} is not a valid Java identifier.
Explanation The supplied property name does not conform to the allowed format described in the JMS specification.
Action Check the characters used in the property name and modify as necessary.
CWSIA0113E: The property name {0} is reserved and cannot be set.
Explanation The supplied property name begins with the JMS prefix, but is not one of the supported, settable properties.
Action Check the property name and correct errors.
CWSIA0114E: The property {0} should be set using type {1}, not {2}.
Explanation JMS_IBM properties may only be set using a specific variable type.
Action Correct application code to use the required variable type when setting this JMS_IBM property.
CWSIA0115E: An exception was received during the call to the method {1}: {0}.
Explanation During execution of the specified method an exception was thrown by another component.
Action See the linked exception for more information.
CWSIA0116E: The specified value {1} is not allowed for {0}.
Explanation The given value is not allowed for the property specified.
Action Change the value to a value that is supported for the property.
CWSIA0121E: An exception occurred while serializing the object: {0}.
Explanation It was not possible to serialize the object because of the exception.
Action Examine the linked exception for details of the error.
CWSIA0122E: An exception occurred deserializing a message, exception: {0}.
Explanation It was not possible to deserialize the message because of the exception shown.
Action Examine the linked exception for details of the error.
CWSIA0141E: The queue browser has no messages available.
Explanation A user application requested a message from a queue browser when none was available.
Action Ensure the application either does not call this method when there are no messages available, or handles this exception.
CWSIA0142E: This queue browser is closed.
Explanation An application called a method that must not be used after the queue browser is closed.
Action Ensure that the queue browser is not closed before calling the method.
CWSIA0143E: An internal error occurred.
Explanation The createBrowserSession call returned null instead of a valid BrowserSession object.
Action This exception is unexpected. The cause is not immediately known.
CWSIA0144E: An exception was received during the call to the method {1}: {0}.
Explanation During execution of the specified method an exception was thrown by another component.
Action See the linked exception for more information.
CWSIA0145E: Unable to browse destination {0}
Explanation A problem was encountered whilst browsing the destination.
Action See the linked exception for more information.
CWSIA0147E: The selector is not valid.
Explanation A message selector was supplied that was incorrect.
Action See the linked exception for more information.
CWSIA0148E: An exception occurred while receiving a message: {0}.
Explanation While receiving a message an exception was thrown that caused the operation to fail.
Action Examine the specified exception, and linked exception object for more information.
CWSIA0149E: The user does not have authorization to carry out this operation. See the linked exception for details.
Explanation The linked exception contains details of the authority that is required to carry out this operation.
Action The administrator must grant the required authority to the relevant user.
CWSIA0161E: The read buffer is null.
Explanation A null reference was passed to the StreamMessage.readBytes method, so no data could be returned.
Action Pass a suitably sized buffer into the readBytes method.
CWSIA0162I: The end of the message stream has been reached.
Explanation The end of the message content has been reached. This is normal if the reading application does not know how much data to expect.
Action No action required.
CWSIA0163E: The StreamMessage byte array was incompletely read.
Explanation An attempt has been made to read the next field from the stream whilst a byte array is partly read.
Action Ensure that the user code completes the read of any byte array before attempting to read the next field.
CWSIA0164E: It is not possible to return null as a character.
Explanation An attempt was made to read a StreamMessage field containing null using the readChar method.
Action Avoid reading nulls using the readChar method.
CWSIA0181E: The encoding is not valid for string {0}.
Explanation The supplied value does not have a known encoding.
Action Ensure that the application supplies a value from the defined list of encodings.
CWSIA0182E: An internal error occurred while writing to the data stream.
Explanation A problem has occurred with data streams used for format conversion of float and double values.
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/.
CWSIA0183I: An attempt was made to read beyond the end of the message.
Explanation An attempt was made to read beyond the end of the message. This may be a normal condition if an application has been coded to read variable length data using the JMS 1.0.2 specification.
Action If necessary, recode the application to use the new getBodyLength method.
CWSIA0184E: The UTF-8 conversion failed.
Explanation There was a problem during either reading or writing of a UTF-8 string. The most common problem is attempting to write a string longer than 65535 characters.
Action See the linked exception for further information.
CWSIA0185E: An incorrect object of type {0} was provided.
Explanation An object was provided to the writeObject method that was not a Java primitive wrapper type.
Action Correct the application to ensure that only objects of the permitted types are passed as parameters to the writeObject method.
CWSIA0186E: An internal error occurred. There is a problem in writing to the message.
Explanation An error was encountered whilst trying to write an item to the message.
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/.
CWSIA0188E: An incorrect object of type {0} was provided.
Explanation An object was provided to the writeObject method that was not a Java primitive wrapper type.
Action Correct the application to ensure that only objects of the permitted types are passed as parameters to the writeObject method.
CWSIA0189E: An incorrect object of type {0} was provided.
Explanation An object was provided to the writeObject method that was not a Java primitive wrapper type.
Action Correct the application to ensure that only objects of the permitted types are passed as parameters to the writeObject method.
CWSIA0190E: An exception was received during the call to the method {1}: {0}.
Explanation During execution of the specified method an exception was thrown by another component.
Action See the linked exception for more information.
CWSIA0201E: An internal error occurred. An object of class {0} can not be created because the JAR file {1} could not be found.
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/.
CWSIA0221E: An exception was received during the call to the method {1}: {0}.
Explanation During execution of the specified method an exception was thrown by another component.
Action See the linked exception for more information.
CWSIA0222E: Connection closed
Explanation The connection was closed during the execution of this method.
Action Repeat the call using a new connection.
CWSIA0223E: Subscription locked
Explanation The durable subscription is not accepting consumers. It may already have an active subsriber, or it may have been administratively disabled. See the linked exception for further detail.
Action Check the application(s) to see if there may be multiple attempts to access a single durable subscription. The JMS specification prohibits this, but if absolutely required see the shareDurableSubscriptions option on the connection factory.
CWSIA0224E: Not authorised to access durable subscription
Explanation The current user does not have authorisation to access the durable subscription.
Action Check the userID has the required access to the resources needed. See the linked exception for more details.
CWSIA0225E: The provided message selector was not valid.
Explanation A problem was encountered interpreting the provided selector string.
Action Check the selector string and correct any errors.
CWSIA0226E: Unable to create durable subscriber for given topic.
Explanation It was not possible to create a durable subscriber because of a problem with the topic space.
Action See the linked exception for details. If the topic space did not exist, either create it or use one that does exist. If the topic was a temporary one, either use a non-durable subscriber or change to a permanent topic.
CWSIA0241E: An exception was received during the call to the method {1}: {0}.
Explanation During execution of the specified method an exception was thrown by another component.
Action See the linked exception for more information.
CWSIA0261E: The specified value {1} is not allowed for {0}.
Explanation The given value is not allowed for the property specified.
Action Change the value to a value that is supported for the property.
CWSIA0281E: The specified value {1} is not allowed for {0}.
Explanation The given value is not allowed for the property specified.
Action Change the value to a value that is supported for the property.
CWSIA0282E: An internal error occurred. An object of class {0} can not be created because the JAR file {1} could not be found.
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/.
CWSIA0283E: The destination in question is blocked from producing/receiving messages with a reason code of {0}
Explanation It is likely that the destination object does not have sufficient information to be used for production and/or consumption of messages.
Action Refer to your IBM representative for information on the cause of the given reason code.
CWSIA0284E: There is insufficient information to route a message to this destination: {0}
Explanation The publish/subscribe broker profile topic mapping used to transfer the original publication from MQ does not contain a broker input queue so it is not possible to route the reply message.
Action Add the correct broker input queue name to the appropriate broker profile topic mapping.
CWSIA0301E: The specified value {1} is not allowed for {0}.
Explanation The given value is not allowed for the property specified.
Action Change the value to a value that is supported for the property.
CWSIA0321E: The specified value {1} is not allowed for {0}.
Explanation The given value is not allowed for the property specified.
Action Change the value to a value that is supported for the property.
CWSIA0341E: Exception received during asynchronous processing: {0}
Explanation An exception originated outside of user code whilst asynchronous delivery was running
Action See the linked exception for more information
CWSIA0342E: The messaging engine is shutting down.
Explanation The messaging engine to which the application is attached has been shut down.
Action The application should use this as a signal to disconnect from the messaging engine.
CWSIA0343E: The connection has been closed because of the following exception: {0}
Explanation A communications failure has resulted in the loss of the connection to the messaging engine.
Action Examine the linked exception for more information.
CWSIA0344E: The connection has been closed because the messaging engine has terminated.
Explanation The messaging engine has been shutdown leaving the connection unusable.
Action Restart the messaging engine and reconnect.
CWSIA0360E: The required character set encoding {0} is not supported.
Explanation The specified character set is a required for operation of this functionality, but could not found.
Action Make the specified character set available for use by this JVM.
CWSIA0361E: An internal error has occurred because {0} was specified for {1}
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/.
CWSIA0362E: An internal error has occurred. ProbeID: {0}. Extra information: {1} : {2}
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/.
CWSIA0381E: The character {0} is not escaped in the element {1} within the URI: {2}
Explanation The identified character is not allowed in a name-value pair element of a URI string unless escaped by a backslash.
Action Escape the identified character by preceding it with a backslash.
CWSIA0382E: The URI element {0} is malformed in URI {1}
Explanation The name-value pair element identified is malformed, possibly not containing both a name and a value.
Action Examine the identified name-value pair element to ensure that is it correctly formed.
CWSIA0383E: The reserved destination prefix {0} was found in URI {1}
Explanation The identified destination prefix is reserved.
Action Consider using the prefix 'queue://' for a queue destination or 'topic://' for a topic destination.
CWSIA0384E: The URI element {0}={1} could not be set as a property on the Destination object, from URI {2}
Explanation The name property of the URI element indentified could not be decoded into a valid Destination property.
Action Ensure that the name property identified is a valid property for Destination objects.
CWSIA0385E: It is not permitted for a destination URI to specify a queue manager, as found in URI : {0}
Explanation The use of queue managers as specified in the destination URI is not supported.
Action Specify a valid URI which does not include the use of a queue manager.
CWSIA0386E: An internal error occurred.
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/.
CWSIA0391E: An internal error occurred. An object of class {0} can not be created because the JAR file {1} could not be found.
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/.
CWSIA0392E: The sequence {0} is not a legal XML entity.
Explanation An illegal escape sequence was found whilst processing the URI string for a Destination
Action If the destination or replyTo strings have been manipulated by user code then check that all & characters are correctly escaped (for use in xml). If not, consider contacting IBM service.
CWSIA0393E: Unable to process illegal surrogate {0}
Explanation Whilst attempting to prepare a message for transmission to MQ, an character was encountered in the Destination or ReplyTo fields that did not conform to the UTF-16 surrogate rules.
Action Ensure that no illegal surrogate characters are used for Destination or ReplyTo names that may be sent to MQ.
CWSIA0481E: It is not permitted to call method {0} on class {1}.
Explanation The application called a method that is not supported by the JMS specification.
Action Change the application program to remove this behavior.
CWSIA0482E: {0} is not supported in this release.
Explanation The application has attempted to use a feature or capability that is not supported by the current release of the software.
Action Remove the code that attempts to use this capability or update to a later release of the software if available.
CWSIA0483E: It is not permitted to call method {0} on class {1}.
Explanation The application called a method that is not supported by the JMS specification.
Action Change the application program to remove this behavior.
CWSIA0484E: {0} is not supported in this release.
Explanation The application has attempted to use a feature or capability that is not supported by the current release of the software.
Action Remove the code that attempts to use this capability or update to a later release of the software if available.
CWSIA0485E: An exception was received during the call to the method {1}: {0}.
Explanation During execution of the specified method an exception was thrown by another component.
Action See the linked exception for more information.
CWSIA0499E: An internal error occurred. The value {1} is not valid for parameter or variable {0}.
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/.
CWSIA0500E: {0}
Explanation If the message does not give sufficient information, check any previous messages for further information.
Action If you are not able to resolve the problem ask your system administrator to help resolve the problem.
Reference topic    

Terms of Use | Feedback

Last updated: Apr 23, 2009 7:19:30 AM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.websphere.sib.api.jms.CWSIAJMSMessages.html

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