-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.13, 4.12, 4.11
-
None
-
None
-
CNF RAN Sprint 231
-
1
-
False
-
-
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
- is blocked by
-
OCPBUGS-5301 BMER app is not started after creating kubernetes secret with BMC info
- Closed
- is depended on by
-
OCPBUGS-4255 AMQ resource are not freedup up after multiple GetCurrentState Call
- Closed
- links to