web server - Borland Technical Publications

EJB Container-level Properties
Table 31.1
ejb.interop.marshal_handle_as_ior=true|
false
ejb.finder.no_custom_marshal=true|false
ejb.collect.stats_gather_frequency=
ejb.collect.display_statistics=true|
false
ejb.collect.statistics=true|false
ejb.collect.display_detail_statistics=
true|false
ejb.mdb.threadMaxIdle=
ejb.mdb.threadMax=
ejb.mdb.threadMin=
EJB container properties (continued)
Property Description Default
If set to true, each instance of
javax.ejb.Handle is marshaled as a
CORBA IOR. Otherwise, it is marshaled
as a CORBA abstract interface. See
CORBA IIOP spec for details.
When a multi-object finder returns a
collection of objects, by default the EJB
container does the following:
■ creates and returns a custom Vector
implementation to the caller.
■ creates IORs (from the primary keys)
lazily as the caller of the finder
browses/iterates over the Vector
returned.
■ compute IORs for the whole Vector,
when result is to leave the JVM
where it was created.
If this property is set to true, the EJB
container does not do any of the above.
The time interval in seconds between
printouts of container statistics. If set to
zero, this disables stats gathering and
no stats are displayed (since they are
not collected). This means that a zero
setting overrides whatever may be the
value of ejb.collect.display_statistics,
ejb.collect.statistics or
ejb.collect.display_detail_statistics
properties.
This flag turns on timer diagnostics,
which allow the user to see how the
Container is using the CPU.
Same as the
ejb.collect.display_statistics property,
except this property does not write the
timer value to the log.
This flag turns on the timer diagnostics,
as ejb.collect.display_statistics option
does. In addition, it prints out method
level timing information. This allows the
developer to see how different methods
of the bean are using CPU. Please note,
that the console output of this flag will
require you to widen your terminal to
avoid wrapping of long lines.
There is a VM wide thread pool
maintained by the EJB container for
message-driven bean execution. This
pool has the same configurability as the
ORB dispatcher pool for handling RMI
invocations. This particular property
controls the maximum duration in
seconds a thread can idle before being
reaped out.
Maximum number of threads allowed in
the MDB thread pool.
Minimum number of threads allowed in
the MDB thread pool.
false
false
5
false
false
false
300
0 (no
limit)
0
Chapter 31: EJB, JSS, and JTS Properties 335