|
Tags for creation of WebLogic specific resources
Used to specify various options for instance pooling.
Parameter |
Type |
Applicability |
Description |
Mandatory |
max-beans-in-free-pool |
int |
|
WebLogic EJB maintains a free pool of beans for every bean class.
This property decides the maximum size of the pool.
|
false |
initial-beans-in-free-pool |
int |
|
WebLogic EJB maintains a free pool of beans for every bean class.
This property decides the initial size of the pool.
|
false |
Used to specify various options for the caching.
Parameter |
Type |
Applicability |
Description |
Mandatory |
max-beans-in-cache |
int |
|
Maximum number of objects of this class that are allowed in memory.
Objects are kept in an LRU chain, and the ones dropped from the
end of the chain are passivated.
|
false |
idle-timeout-seconds |
int |
|
The cache (see "max-beans-in-cache" above) is scrubbed of
inactive objects after at least this many seconds. Objects
scrubbed are passivated.
|
false |
read-timeout-seconds |
int |
Entity beans |
The read-timeout-seconds is the number of seconds between ejbLoad calls on
a Read-Only entity bean. If read-timeout-seconds is 0,
ejbLoad will only be called when the bean is brought into the cache.
|
false |
concurrency-strategy |
int |
Entity beans |
The concurrency-strategy specifies how the container should manage concurrent
access to an entity bean.
The concurrent-strategy can be one of the following values:
- "Exclusive": The exclusive locking scheme used in WebLogic Server
versions 3.1 through 5.1
- "Database": A scheme where a separate Entity Bean instance is allocated
for each transaction and the locking and caching is handled by the
database.
- "ReadOnly" : For read-only entity beans
|
false |
cache-type |
int |
Stateless Session Beans (WLS 6.1) |
The cache-type can be one of "NRU" or "LRU". The default is "NRU".
Used in: stateful-session-cache
|
false |
The lifecycle element is used to specify various options for the management of
the lifecycle of stateful beans.
Parameter |
Type |
Applicability |
Description |
Mandatory |
passivation-strategy |
text |
|
The passivation-strategy can be either "default" or "transaction". With
the default setting the container will attempt to keep a working set
of beans in the cache. With the "transaction" setting, the container will
passivate the bean after every transaction (or method call for a
non-transactional invocation).
|
false |
Tags for creation of WebLogic specific resources
|