STOP RIB Container is throwing an issue

Hi,

We have a client with multiple custom RIB containers handling various integrations across systems. We are encountering a specific issue where, when OPMN attempts to stop one particular container, the shutdown process is aborted. The container does not shut down gracefully within the configured 120-second timeout and is subsequently force-killed, even though there is no data pending in the hospital or queues. All other custom containers shut down as expected without any issues.

Note: We attempted to increase the OPMN shutdown timeout to 5–10 minutes; however, the issue persists.

Upon reviewing the container logs, we identified the error mentioned below. We would appreciate your guidance or recommendations to help resolve this issue.