Mama subscription state machine issue for subscription type basic and state ACTIVATING




I’m currently having an issue when creating a basic type mamaSubscription. I’m trying to create the subscription with a wildcard to cause the bridge to return an invalid argument status and afterwards the state of the subscription is activating. Since the state is activating not activated I cannot deactivate, destroy, recreate(create again) or deallocate.  As a result I leak the memory associated with the subscription. The openmama C dev guide does not show a transition for the subscription state machine for the ACTIVATING state for basic subscriptions according to figure 1 page 32, from's%20Guide%20C.pdf. What should be the expected behaviour for this error path?


Chris Morgan