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

Send Notificarion error to AM notificationservice logs from ssoadm

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 6.0.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.0.0.4, 6.0.0.5
    • Fix Version/s: None
    • Component/s: session, ssoadm
    • Labels:
      None

      Description

      Bug description

      When performing any ssoadm say list-servers, it is seen that the CoreSystems debug logs the following

      amComm:11/27/2018 01:23:55:396 PM UTC: Thread[amSession,5,main]: TransactionId[6ffd9ebc-6754-4822-8cb3-ef5e247788b4-13443]
      ERROR: Cannot send notification to http://openamexample.com:8080/openam/notificationservice
      com.iplanet.services.comm.server.SendNotificationException: Send notification failed.
              at com.iplanet.services.comm.server.NotificationSender.run(NotificationSender.java:103)
              at com.iplanet.services.comm.server.PLLServer.send(PLLServer.java:69)
              at com.iplanet.dpro.session.service.SessionNotificationSender$SessionNotificationSenderTask.handleSession(SessionNotificationSender.java:174)
              at com.iplanet.dpro.session.service.SessionNotificationSender$SessionNotificationSenderTask.run(SessionNotificationSender.java:156)
              at org.forgerock.openam.audit.context.AuditRequestContextPropagatingRunnable.run(AuditRequestContextPropagatingRunnable.java:34)
              at com.iplanet.am.util.ThreadPool$WorkerThread.run(ThreadPool.java:312)
      

       
      There is no functional impact other than this being logged.
       

      How to reproduce the issue

      Details steps outlining how to recreate the issue (remove this text)

      1. Install AM6.0.x
      2. Install ssoadm
      3. Do a ssoadm list-servers
      4. Check the AM debug logs
      Expected behaviour
      No exception for this where the notificationservice goes back to the AM (notice the URL)
      
      Current behaviour
      Exception happens when a session is destroyed (for SSOADM) when the session adds a NotificationURL to self (%AM/%DEPLOYURI/notificationservice)
      

      Work around

      Ignore. The SessionNotificationService implementation handler is no longer in 5.5.x and 6.x and hence the Session PLL response returns NOT_OK.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              chee-weng.chea C-Weng C
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: