- **Milestone**: 4.5.2 --> 4.6.2
---
** [tickets:#916] lock-in of payload middleware su times-out and remains in
ENABLED state**
**Status:** unassigned
**Milestone:** 4.6.2
**Created:** Tue May 20, 2014 07:08 AM UTC by surender khetavath
**Last Updated:** Wed Jul 15, 2015 01:25 PM UTC
- **Milestone**: future -- 4.5.2
---
** [tickets:#916] lock-in of payload middleware su times-out and remains in
ENABLED state**
**Status:** unassigned
**Milestone:** 4.5.2
**Created:** Tue May 20, 2014 07:08 AM UTC by surender khetavath
**Last Updated:** Sat Aug 23, 2014 06:19 PM UTC
Hi Bj,
Immnd was terminated because of lock-in on mw su.
When immnd was terminated, it should notify users(in this case admin user) to
come out of sync call. User shouldn't be in waiting state till timeout.
-Nagu
---
** [tickets:#916] lock-in of payload middleware su times-out and remains in
---
** [tickets:#916] lock-in of payload middleware su times-out and remains in
ENABLED state**
**Status:** unassigned
**Milestone:** future
**Created:** Tue May 20, 2014 07:08 AM UTC by surender khetavath
**Last Updated:** Tue May 20, 2014 07:08 AM UTC
**Owner:** nobody
changeset : 5270
i checked my setup. libraries are properly linked.
---
** [tickets:#916] lock-in of payload middleware su times-out and remains in
ENABLED state**
**Status:** unassigned
**Milestone:** future
**Created:** Tue May 20, 2014 07:08 AM UTC by surender khetavath
**Last Updated:** Tue May 20, 2014
Analysis:
1. The command was issued from payload PL-4 for lock-in the
safSu=PL-4,safSg=NoRed,safApp=OpenSAF.
2. Amfnd on PL-4 terminates the immnd and sends response to Amfd(on SC-1) and
Amfd(on SC-1) responds to immnd(on SC-1).
May 20 12:19:59.855987 osafamfd [3515:avd_ndproc.c:0323]
- **Component**: amf -- imm
---
** [tickets:#916] lock-in of payload middleware su times-out and remains in
ENABLED state**
**Status:** unassigned
**Milestone:** future
**Created:** Tue May 20, 2014 07:08 AM UTC by surender khetavath
**Last Updated:** Wed May 21, 2014 03:02 AM UTC
**Owner:**
My interpretation is that the payload where the admin-op request is issued,
can not be communicated with when the reply for the admin-op is to be sent.
The analysis above says that the IMMND is terminated and that would then
be an explanation. The only question would be why is the IMMND terminated
- **Component**: imm -- unknown
- **Comment**:
The IMMND at PL_4 receives a terminate callback from the AMF.
---
** [tickets:#916] lock-in of payload middleware su times-out and remains in
ENABLED state**
**Status:** unassigned
**Milestone:** future
**Created:** Tue May 20, 2014 07:08 AM
