Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-4961

AMQ resource are not freedup up after multiple GetCurrentState Call

XMLWordPrintable

    • None
    • CNF RAN Sprint 231
    • 1
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Running container for longer time  generates many amq resource which are not freedup.
      AMQ should be closed after using  temp AmQ  connections
      {"level":"warn","ts":1669767264.6086981,"logger":"fallback","caller":"client/client.go:248","msg":"Error while receiving a message: *Error{Condition: amqp:resource-limit-exceeded, Description: local-idle-timeout expired, Info: map[]}"}
      {"level":"warn","ts":1669767264.6088223,"logger":"fallback","caller":"client/client.go:248","msg":"Error while receiving a message: *Error{Condition: amqp:resource-limit-exceeded, Description: local-idle-timeout expired, Info: map[]}"}
      
      

      4:12

      
      

      Keep consumer running for few hours.,the consumer pools for currentState every few secs which will end up with resource limit exceeded error

              jacding@redhat.com Jack Ding
              aputtur@redhat.com Aneesh Puttur
              Ofer Bochan Ofer Bochan
              Red Hat Employee
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: