■ "Configure advanced topic parameters""Configure advanced topic parameters"
■
■ "Configure advanced queue parameters""Configure advanced queue parameters"
■
■ "Uniform distributed topics - configure advanced parameters""Uniform distributed topics - configure advanced parameters"
■
■ "Uniform distributed queues - configure advanced parameters""Uniform distributed queues - configure advanced parameters"
■
■ "Configure advanced JMS template parameters""Configure advanced JMS template parameters"
For more information about these parameters, see
For more information about these parameters, seeDestinationBeanDestinationBean and andTemplateBeanTemplateBean
in the
in the MBean Reference MBean Reference for Oracle Wfor Oracle WebLogic ServerebLogic Server..
13.17.
13.17.22 Compat Compatibili ibility With the Asy ty With the Asynchr nchronous Me onous Message Pipe ssage Pipeline line
The Message Performance Preference option is compatible with asynchronous The Message Performance Preference option is compatible with asynchronous consumers using the Asynchronous Message Pipeline, and is also compatible with consumers using the Asynchronous Message Pipeline, and is also compatible with synchronous consumers that use the
synchronous consumers that use the Prefetch Mode for Synchronous ConsumersPrefetch Mode for Synchronous Consumers feature, which simulates the Asynchronous Message
feature, which simulates the Asynchronous Message Pipeline. However, if the value ofPipeline. However, if the value of the Maximum Messages value is set too low, it may negate the impact of the
the Maximum Messages value is set too low, it may negate the impact of the destination's higher-level performance algorithms (e.g., Low, Medium, and High destination's higher-level performance algorithms (e.g., Low, Medium, and High W
Waiting Threshold for Message aiting Threshold for Message Batching). For more information Batching). For more information on the Asynchronouson the Asynchronous Message Pipeline, see "Receiving Messages" in
Message Pipeline, see "Receiving Messages" in Developing JMS Applications for OracleDeveloping JMS Applications for Oracle WebLogic Server
WebLogic Server..
13.
13.18 18 Cli Client ent-si -side Th de Threa read P d Pool oolss
With most java client side applications, the default client thread pool size of 5 threads With most java client side applications, the default client thread pool size of 5 threads is sufficient. If, however, the application has
is sufficient. If, however, the application has a large number of asynchronousa large number of asynchronous consumers, then it is often beneficial to allocate slightly more threads than consumers, then it is often beneficial to allocate slightly more threads than asynchronous consumers. This allows more asynchronous consumers to run asynchronous consumers. This allows more asynchronous consumers to run concurrently.
Table able 13–413–4 (Cont(Cont.).) MessaMessage ge PerPerformformance ance PrefePreferencrence Ve Valuealues s WebLogi
WebLogic c ServerServer Administration
Considerations for Oracle Data Guard Environments Considerations for Oracle Data Guard Environments
W
WebLogic client ebLogic client thread pools are thread pools are configured differently than WebLogic serverconfigured differently than WebLogic server thread-pools, and are not self
thread-pools, and are not self tuning. Wtuning. WebLogic clients have a ebLogic clients have a specific thread pool thatspecific thread pool that is used for handling
is used for handling incoming requests from the server, such as JMS MessageListenerincoming requests from the server, such as JMS MessageListener invocations. This pool can be configured via the command-line property:
invocations. This pool can be configured via the command-line property:
-Dweblogic.ThreadPoolSize=n -Dweblogic.ThreadPoolSize=n
where n is the number of threads where n is the number of threads Y
You can force a client-side ou can force a client-side thread dump to verify that thread dump to verify that this setting is this setting is taking effect.taking effect.
13.19
13.19 Best P Best Practi ractices f ces for JM or JMS .NE S .NET Clie T Client Appl nt Applicati ications ons
The following is a short list of performance related best practices to use when creating The following is a short list of performance related best practices to use when creating a JMS .NET client application:
a JMS .NET client application:
■
■ Always register a connection exception listener using an IConnection if theAlways register a connection exception listener using an IConnection if the application needs to take action when an idle connection fails.
application needs to take action when an idle connection fails.
■
■ Have multiple .NET client threads share a single context to ensure that they use aHave multiple .NET client threads share a single context to ensure that they use a single socket.
single socket.
■
■ Cache and reuse frequently accessed JMS resources, such as contexts, connections,Cache and reuse frequently accessed JMS resources, such as contexts, connections, sessions, producers, destinations, and connection factories. Creating and closing sessions, producers, destinations, and connection factories. Creating and closing these resources consumes significant CPU and network bandwidth.
these resources consumes significant CPU and network bandwidth.
■
■ Use DNS aliases or comma separated addresses for load balancing JMS .NETUse DNS aliases or comma separated addresses for load balancing JMS .NET clients across multiple JMS .NET client host servers in a cluster.
clients across multiple JMS .NET client host servers in a cluster.
For more information on best practices and other programming considerations for JMS For more information on best practices and other programming considerations for JMS .NET client applications, see "Programming Considerations" in Use the WebLogic JMS .NET client applications, see "Programming Considerations" in Use the WebLogic JMS Client for Microsoft .NET.
Client for Microsoft .NET.
13.20
13.20 Consi Considerat derations fo ions for Orac r Oracle Data Gua le Data Guard En rd Enviro vironments nments
The following sections p
The following sections provide configuration considerations for a rovide configuration considerations for a WWebLogic JMSebLogic JMS environment that includes Oracle Data
environment that includes Oracle Data Guard.Guard.
■
■ SectionSection13.20.1, "Pause Destinations 13.20.1, "Pause Destinations for Planned Down for Planned Down Time"Time"
■
■ SectionSection13.20.2, "Migrate JMS 13.20.2, "Migrate JMS Services for Unexpected Services for Unexpected Outages"Outages"
For more information on Oracle Data Guard, see For more information on Oracle Data Guard, see
http://www.oracle.com/us/products/database/options/active-data-guard/overvie http://www.oracle.com/us/products/database/options/active-data-guard/overvie w/index.html.
w/index.html.
13.20.
13.20.11 Pause Pause Destin Destinations f ations for Plan or Planned Do ned Down Time wn Time
For planned maintenance windows, pause the impacted JMS destinations before For planned maintenance windows, pause the impacted JMS destinations before initiating the switch from the production database instance to standby instance. When initiating the switch from the production database instance to standby instance. When the standby database has transitioned to production, resume the JMS destinations. See the standby database has transitioned to production, resume the JMS destinations. See
"Pause JMS server message operations at runtime" in
"Pause JMS server message operations at runtime" in Oracle WebLogic ServerOracle WebLogic Server Administrati
Administration Console Online on Console Online HelpHelp..
13.20.
13.20.22 Migrat Migrate JMS e JMS Services Services for for Unexp Unexpected ected Outages Outages
For unexpected service outages, implement JMS Service migration with the
For unexpected service outages, implement JMS Service migration with the Restart onRestart on Failure
Failure option. Should the amount of time required to switch from the production to option. Should the amount of time required to switch from the production to standby database exceed the value of the
standby database exceed the value of the StoreStoreIORetryDelaySecondsIORetryDelaySeconds attribute and the attribute and the JMS Services fails, the JMS service and associated store are restarted in-place. See JMS Services fails, the JMS service and associated store are restarted in-place. See
Considerations for Oracle Data Guard Environments
"In-Place Restarting of Failed Migratable Services" in Administering Clusters for Oracle WebLogic Server.