Question on DM Front End/Back End Connection Management
(Doc ID 1578854.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 7.4.0 to 7.5.0]
Information in this document applies to any platform.
On all versions of Oracle Communications Billing and Revenue Management (BRM), how is it possible for PIN_FLD_DM_FE_STATE to have a State of 0 and PIN_FLD_DM_BE_STATE to have a State of 3?
Shouldn't the Back End (BE) connection be released from the transaction automatically when Front End (FE) becomes idle?
Here is the snippet of dm_status that is confusing:
1 PIN_FLD_PID INT  8685
1 PIN_FLD_FLAGS INT  4096
1 PIN_FLD_TATTLE_TALE INT  8
1 PIN_FLD_CONNECTS INT  10
1 PIN_FLD_HIWAT INT  13
1 PIN_FLD_OPS_DONE INT  5591989
1 PIN_FLD_TRANS_DONE INT  114958
1 PIN_FLD_DM_FE_CONNECT ARRAY  allocated 20, used 11
2 PIN_FLD_FLAGS INT  16777233
2 PIN_FLD_DM_FE_STATE INT  0
2 PIN_FLD_DM_BE_STATE INT  3
2 PIN_FLD_DM_BE_IDX INT  29
2 PIN_FLD_OPCODE INT  4
2 PIN_FLD_OPS_DONE INT  25
2 PIN_FLD_TRANS_DONE INT  2
2 PIN_FLD_DM_USED INT  16384
2 PIN_FLD_DM_LOW INT  24
2 PIN_FLD_DM_HIGH INT  8104
2 PIN_FLD_DM_BIG INT  16
It is suspected that custom BRM code that caused Connection Manager (CM) to crash. When the CM children die, the FE and BE involved in the transaction end up in this state pair (FE 0, BE 3).
The possible values for PIN_FLD_DM_FE_STATE and PIN_FLD_DM_BE_STATE make sense when looking at them individually. That does not necessarily say that the combination of 0 and 3 is valid. In other words, when the BE is busy and locked in a transaction but FE is idle (ie. NOT in state "2") then the net state between FE and BE becomes inconsistent. BE will wait forever (and it does) and front-end is never going to send an abort or commit to the back-end.
The question is that why is the FE not sending an abort command to the BE when the FE loses its consumer, the CM child?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document