web server - Borland Technical Publications

Complete Index of EJB Properties
Table 31.3
Message Driven Bean properties (continued)
Property Type Description Default
ejb.mdb.unDeliverableQueueCon
nectionFactory
String
Should an MDB fail to
consume a message for
any reason, the message
will be re-delivered by the
JMS service. The message
will only be re-delivered five
times. After five attempts,
the message will be
delivered to a dead queue
(if one is configured). This
property looks up the JNDI
name for the connection
factory to create a
connection to the JMS
service. This property is
used in conjunction with
ejb.mdb.unDeliverableQueue.
ejb.mdb.unDeliverableQueue String Should an MDB fail to
consume a message for
any reason, the message
will be re-delivered by the
JMS service. The message
will only be re-delivered five
times. After five attempts,
the message will be
delivered to a dead queue
(if one is configured). This
property looks up the JNDI
name of the queue. This
property is used in
conjunction with
ejb.mdb.unDeliverableQueueCo
nnectionFactory.
ejb.transactionManagerInstanc
eName
String
This property is currently
supported only for MDBs
that have the “Required”
transaction attribute. Use
this property to specify by
name a particular
transaction manager for
driving the transaction
started for the onMessage()
call. This option is useful in
cases where you need 2PC
completion of this particular
transaction but desire to
avoid the RPC overhead of
using the 2PC transaction
manager for all other
transactions in the system
e.g. in entity beans. Please
refer to the MDB chapter for
more details.
None
None
None
344 BES Developer’s Guide