Symantec IGA

Expand all | Collapse all

CA Identity Manager Endpoint stopped working with error java.lang.Exception: get current stack

Jump to Best Answer
  • 1.  CA Identity Manager Endpoint stopped working with error java.lang.Exception: get current stack

    Posted 12-14-2017 09:19 AM

    Hi,

     

    We have CA Identity Manager version 12.6.5 which is running successfully. We have developed a custom connector by using connector Xpress to connecto to an ldap application which is working fine till dec 8. From then the provisioning to the applications is failing with error as 

     

    2017-12-13 16:40:22,773 18862523 [ApacheDS Worker-thread-139] (com.ca.jcs.core:com.ca.jcs.cfg.GenericObjectPoolConnectionManager:217) DEBUG - ConnectionPool [JNDIConnectionFactory [ldap://hostname:port]: 1/-1 idle, 0/20 active]: returned connection: ldap://hostname:port(0 active)
    java.lang.Exception: get current stack
    at com.ca.jcs.cfg.GenericObjectPoolConnectionManager.logEvent(GenericObjectPoolConnectionManager.java:213)[131:com.ca.jcs.core:1.1.0.20131127]
    at com.ca.jcs.cfg.GenericObjectPoolConnectionManager.returnConnection(GenericObjectPoolConnectionManager.java:131)[131:com.ca.jcs.core:1.1.0.20131127]

     

    Could you please help me as we couldnt able to find docs related to the issue. The other connectors are working fine and user are getting provisioned successfully.


    Thanks,

    Rajesh



  • 2.  Re: CA Identity Manager Endpoint stopped working with error java.lang.Exception: get current stack

    Posted 12-14-2017 10:08 AM

    Hello Rajesh, 

     

    What is the etatrans log error you see when attempting to provision to this endpoint? 

     

    Thank you, 

    Jennifer



  • 3.  Re: CA Identity Manager Endpoint stopped working with error java.lang.Exception: get current stack
    Best Answer

    Posted 12-18-2017 12:47 PM

    Hello Rajesh,

     

    As noted from the duplicate thread, a note was made, "

    "java.lang.Exception: get current stack" is not an error. The message is generated as part of logging stack information.

    Can you post the full connector log?"

     

    Regards,

    Andrew Nguyen