CA Service Management

 View Only
  • 1.  Unable to find DomSession

    Posted Jun 17, 2020 04:39 PM
    Edited by Christopher Hackett Jun 17, 2020 04:40 PM
    Buenas tardes, 

    Al intentar consultar un documento de la KDB, luego de 15 segundos me devuelve un Delayed Server Response, al consultar lo logs encuentro este error: 
    SEVERE_ERROR srel_attr.c 3568 SRef_Holder_Monitor[KD:410345; oeJPCA Fac(KD.id) Key(410345,) Dob(peJPCA,) Dset() Stat(0) Src(FAC)]: error 1 in factory_ret: Unable to obtain DomSession.

    Solo ocurre con el nodo secundario, el principal responde sin problema a la consulta.

    Atento a sus comentarios.

    English:
    When trying to consult a document from the KDB, after 15 seconds it returns a Delayed Server Response, when consulting logs I find this error:
    SEVERE_ERROR srel_attr.c 3568 SRef_Holder_Monitor [KD: 410345; oeJPCA Fac (KD.id) Key (410345,) Dob (peJPCA,) Dset () Stat (0) Src (FAC)]: error 1 in factory_ret: Unable to obtain DomSession.
    
    It only happens with the secondary node, the main one responds without problem to the query.
    
    Attentive to your comments.


    ------------------------------
    Neimar.
    ------------------------------


  • 2.  RE: Unable to find DomSession
    Best Answer

    Broadcom Employee
    Posted Jun 18, 2020 02:41 AM
    Hi Neimar,

    What are the SDM version and patch level?

    Usually, this issue points to an underlying performance issue. So you may want to start reviewing the below document...

    https://knowledge.broadcom.com/external/article?articleId=96803


    ------------------------------
    Kind Regards,
    Brian
    ------------------------------



  • 3.  RE: Unable to find DomSession

    Posted Jun 18, 2020 10:48 AM
    Buenos días Brian,

    Se tiene instalada la versión 17.2; probé las opciones del documento y persiste la falla.

    Atento a comentarios.