Databases Reference
In-Depth Information
The statistics show the total number of received, committed,
and lost messages, based on the rule as follows:
Total Mes-
sages Received
=
Total Messages committed in ADC
+
Total Messages Lost
If
Total Messages Lost
is zero or unchanged since the previous test, testing is
successful; otherwise, testing fails, and JMS messages are lost. This means that
BAM received the message, but was unable to process it in the Data Object. A
reason for this could be that the message was in an invalid XML format.
Transaction and fault handling
EMS supports the JTA transaction. The Messaging Framework, which handles
JMS message consumption, does not propagate JTA transaction to EMS. Thus,
EMS always starts a new transaction after a JMS message is delivered to EMS.
Therefore, the transaction boundary in BAM is actually between the EMS and
the Active Data Cache, and not between the Messaging Framework and the Act-
ive Data Cache.
When there is a fault happening in the message flow from
EMS to Active Data Cache, the current transaction rolls back,
but only to the point where it is started in EMS. Since JMS
message consumption is not a part of this transaction, mes-
sages are discarded in the end. Thus, it is highly recommen-
ded to use the fault handling mechanism to keep track of the
error messages and payloads.
