- **status**: unassigned --> accepted
- **assigned_to**: Alex Jones
- **Comment**:
I was able to reproduce the problem. It is a race condition between async
failure in AMF on the upgraded SU and the commit being processed in smfd.
---
** [tickets:#2413] smf: coredump, suspend is issued at completed state**
**Status:** accepted
**Milestone:** 5.2.0
**Created:** Wed Apr 05, 2017 12:39 PM UTC by Rafael
**Last Updated:** Thu Apr 06, 2017 11:58 AM UTC
**Owner:** Alex Jones
**Attachments:**
-
[osafsmfd.9276.SC-2.core.txt](https://sourceforge.net/p/opensaf/tickets/2413/attachment/osafsmfd.9276.SC-2.core.txt)
(15.4 kB; text/plain)
ticket #2145 looks to be causing this issue.
coredump printout is attached.
Steps to reproduce: run a campaign and have AMF compenent fail at the campaign
completed state. This triggers a event in SMF which tries to suspend a
completed campaign.
Function handleAmfObjectStateChangeNotification will try to call asyncFailure()
which is the same as suspend() because the campaign is completed and commited
this is not a valid transition. The campaign state instance is most likely
deleted therefore we get a coredump.
For reference refer to figures 5, 6, 7 in SMF AIS. Starting from section 5.1.3
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
