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

Unncessary 'Unable to parse packet received from RADIUS client' log entries in log file

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.5.1, 6.5.1
    • Fix Version/s: 6.5.2, 7.0.0
    • Component/s: RADIUS
    • Labels:
    • Sprint:
      AM Sustaining Sprint 63
    • Story Points:
      1
    • Needs backport:
      No
    • 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

      Description

      Bug description

      The AM RADIUS server is deployed in an environment where a monitoring process sends a UDP packet to the server every minute to check for availability.  This leads to the following exception being logged for each request which generates unnecessary entries in the log files:

      ERROR: Unable to parse packet received from RADIUS client 'client_name'. Dropping.
      java.nio.BufferUnderflowException
             at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:151)
             at java.nio.ByteBuffer.get(ByteBuffer.java:715)
             at org.forgerock.openam.radius.common.PacketFactory.toPacket(PacketFactory.java:95)
             at org.forgerock.openam.radius.server.RadiusRequestHandler.getValidPacket(RadiusRequestHandler.java:240)
             at org.forgerock.openam.radius.server.RadiusRequestHandler.run(RadiusRequestHandler.java:120)
             at 
      org.forgerock.openam.audit.context.AuditRequestContextPropagatingRunnable.run(AuditRequestContextPropagatingRunnable.java:34)
             at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
             at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
             at java.lang.Thread.run(Thread.java:748)

      How to reproduce the issue

      1. Configure AM as a RADIUS server
      2. Send a UDP packet to the server
      3. Observe exception
      Expected behaviour
      Packets that could not be parsed such as this shouldn't necessarily generate a log entry at Error level (and/or stack trace).
      
      Current behaviour
      A log file entry with stack trace at Error level.

        Attachments

          Activity

            People

            • Assignee:
              joe.starling Joe Starling
              Reporter:
              andy.itter Andy Itter
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: