user manual

390 BES Developer’s Guide
EJB Customization Properties: Deployment Descriptor level
EJB Customization Properties: Deployment Descriptor level
These properties customize the behavior of a particular EJB. Some of them
are applicable only to a particular type of EJB (such as session or entity),
others are applicable to any kind of bean. There are several places where
these properties can be set. Below are these places in the order of
precedence:
1 Property element defined on the EJB level in the ejb-borland.xml
deployment descriptor of a JAR file. This setting affects this particular EJB
only. For example, the following XML sets the ejb.maxBeansInPool property to
99 for the EJB named data:
<ejb-jar>
. . .
<enterprise-beans>
<entity>
<ejb-name>data</ejb-name>
<bean-home-name>data</bean-home-name>
<property>
<prop-name>ejb.maxBeansInPool</prop-name>
<prop-type>Integer</prop-type>
<prop-value>99</prop-value>
ejb.collect.statistics=true|
false
Same as the
ejb.collect.display_statistics property,
except this property does not write the
timer value to the log.
false
ejb.collect.display_detail_sta
tistics=true|false
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.
false
ejb.mdb.threadMaxIdle=<num> 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.
300
ejb.mdb.threadMax=<num> Maximum number of threads allowed in
the MDB thread pool.
no limit
ejb.mdb.threadMin=<num> Minimum number of threads allowed in
the MDB thread pool.
0
Property Description Default