This section describes problems with the message service.
[CR #274966] To delete a message queue, you must first remove any listeners that are attached to the queue. If you attempt to delete a message queue that has an active listener, the message queue is not deleted, and an exception is thrown. This problem occurs whether you are using Jaguar Manager, jagtool, or jagant.
Workaround: To remove a listener from a message queue:
In Jaguar Manager, select either Active Queues or Configured Queues.
Highlight the message queue, and select File | Properties.
In the Properties dialog box, select the Listeners tab.
Highlight the listener name and click Delete.
[CR #258376] When running in an EAServer cluster, the message service may hang when adding a selector. This problem occurs when some, but not all members of the cluster have an IIOP or IIOPS listener host name set to “localhost”.
Workaround: Set the listener host name to the machine name for all servers in the cluster.
You cannot use two concurrent threads within a single transacted session to send or receive messages. Attempts to do so result in an INVALID_TRANSACTION exception.
Workaround: Create a separate transacted session for each thread that you use to send or receive messages. This restriction applies to messages received both synchronously and asynchronously; that is, regardless of whether you call “receive” or use a message listener.
If the message service is installed but configured incorrectly or cannot connect to its database, EAServer starts in Admin mode.
Workaround: Verify that you can ping the message service database, and if necessary, reconfigure the message service. See Chapter 8, “Setting up the Message Service,” in the EAServer System Administration Guide for more information.
[CR #258873] Non-ASCII text does not display correctly when using the message service database.
Workaround: To store, retrieve, and display non-ASCII text correctly when using the message service database, you must do one of the following:
When you specify the Server Name for the message service connection cache, define the character set using a jConnect URL of this form:
jdbc:sybase:Tds:<host>:<port>?charset=<charset>
Change the character set of the message service database to be consistent with the language you are using:
Using a text editor, open the MessageServiceConfig.props file located in the EAServer /Repository/Component/CtsComponents directory.
Change the datatype of the varchar columns in the SQL schemas to varbinary.
Drop any tables that contain a column with a datatype you changed from the message service database.
[CR #287123] By default, temporary message queues time out after 60 seconds of inactivity.
Workaround: To increase this value, you can do one of two things:
Set the connection factory’s CONFIG_QUEUE property to the name of a message queue with a reasonably high timeout value. Subsequently, each temporary message queue you create that uses this connection factory inherits the properties of the queue assigned to CONFIG_QUEUE.
Set the value at the global level so all temporary message queues use the same timeout value. To do this, edit the MessageServiceConfig.props file, located in the EAServer /Repository/Component/CtsComponents directory, and set the session.timeout property to the appropriate number of seconds.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
