Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-14842

Misleading "CTS: Operation failed: Result Code: Connect Error" message when CTS store is still up and running

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.5.1, 6.0.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.0.0.4, 6.0.0.5, 6.0.0.6, 6.5.0, 6.5.0.1, 6.5.1, 6.5.0.2, 6.5.2, 6.0.0.7, 6.5.2.1, 6.5.2.2
    • Fix Version/s: 6.0.1, 6.5.3, 7.0.0, 5.5.2
    • Component/s: None
    • Labels:
    • Sprint:
      AM Sustaining Sprint 71, AM Sustaining Sprint 72
    • Story Points:
      2
    • Needs backport:
      Yes
    • Support Ticket IDs:
    • Needs QA verification:
      No
    • Functional tests:
      No
    • Are the reproduction steps defined?:
      Yes and I used the same an in the description, Yes but I used my own steps. (If so, please add them in a new comment)

      Description

       

      Setup an OOTB OpenAM 6.5 with an external configuration/user store and an external CTS store.

      Access OpenAM via the GUI interface and perform some updates.

      Temporary "hang" the configuration store by running kill -stop < pid of configuation store>

      The following messages will be observed 

      ERROR: Unable to start persistent search: 
      CTS: Operation failed:
      Result Code: Connect Error
      Diagnostic Message: No operational connection factories available
      Matched DN:

      Now these messages are misleading because CTS is still up and running

       The issue is probably due to the fact that the following debug_header is "generically" used in all ldap exception code.

        public static final String DEBUG_HEADER = "CTS: ";

       

       

       

       

        Attachments

          Activity

            People

            • Assignee:
              lawrence.yarham Lawrence Yarham
              Reporter:
              sam.phua Sam Phua
            • Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: