| 失效链接处理 |
|
Oracle WebLogic 12c 官方文档 PDF 下载
本站整理下载：
相关截图：
主要内容：
2.3 Use Logging Last Resource Optimization
When using transactional database applications, consider using the JDBC data source
Logging Last Resource (LLR) transaction policy instead of XA. The LLR optimization
can significantly improve transaction performance by safely eliminating some of the
2PC XA overhead for database processing, especially for two-phase commit database
insert, update, and delete operations. For more information, see Tuning Data Sources.
2.4 Tune Connection Backlog Buffering
You can tune the number of connection requests that a WebLogic Server instance
accepts before refusing additional requests. This tunable applies primarily for Web
applications. See Tuning Connection Backlog Buffering.
2.5 Use Optimistic or Read-only Concurrency
Use optimistic concurrency with cache-between-transactions or read-only concurrency
with query-caching for CMP EJBs wherever possible. Both of these two options
leverage the Entity Bean cache provided by the EJB container.
• Optimistic-concurrency with cache-between-transactions work best with read-
mostly beans. Using verify-reads in combination with these provides high data
consistency guarantees with the performance gain of caching. See Tuning
WebLogic Server EJBs.
• Query-caching is a WebLogic Server 9.0 feature that allows the EJB container to
cache results for arbitrary non-primary-key finders defined on read-only EJBs. All
of these parameters can be set in the application/module deployment descriptors.
See Concurrency Strategy.
2.6 Use Local Interfaces
Use local-interfaces or use call-by-reference semantics to avoid the overhead of
serialization when one EJB calls another or an EJB is called by a servlet/JSP in the
same application. Note the following:
• In release prior to WebLogic Server 8.1, call-by-reference is turned on by default.
For releases of WebLogic Server 8.1 and higher, call-by-reference is turned off by
default. Older applications migrating to WebLogic Server 8.1 and higher that do
not explicitly turn on call-by-reference may experience a drop in performance.
• This optimization does not apply to calls across different applications.
2.7 Use eager-relationship-caching
Use eager-relationship-caching wherever possible. This feature allows the EJB
container to load related beans using a single SQL statement. It improves performance
by reducing the number of database calls to load related beans in transactions when a
bean and it's related beans are expected to be used in that transaction. See Tuning
WebLogic Server EJBs.
|
| Java1234官方群25： | 
|
| Java1234官方群25： | 838462530 |
苏公网安备 32061202001004号
