Migrated from http://devel.opensaf.org/ticket/2877.
The issue is seen on SLES 64bit VMs.
Migrated from http://devel.opensaf.org/ticket/2877.
The component initially initializes with B.4.1. Another initialize is invoked with B.1.1 version. When callbacks arrived at the component, Response_4 is invoked with the handle obtained from B.4.1 initialization. Response_4 returned SA_AIS_ERR_VERSION.
Output from the component log:
Invoking the function <built-in function="" saAmfResponse_4=""> with the arguments (4289724417, 4271898630L, None, 1)
('Return Value of the function : <—', 1) ==> Response_4 invoked before doing Initialize with B.1.1 version
Invoking the function <built-in function="" saAmfInitialize="">
('Return Value of the function : <—', [1, 4290772994])
Invoking the function <built-in function="" saAmfResponse_4=""> with the arguments (4289724417, 4287627277L, None, 1)
('Return Value of the function : <—', 3) ===> same handle as used before but got ERR_VERSION now.
Traces can be shared if required.
As part of ticket cleanup, evaluated and decided to keep it as enhancement.
Diff:
Please find attached sample file, used in testing.
I tested on CS #8791. I didn't get any issue. Health check continued.
Jul 19 11:11:24 PM_SC-1 osafamfnd[30940]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State INSTANTIATING => INSTANTIATED
Jul 19 11:11:24 PM_SC-1 amf_demo[31113]: HC started with AMF 4
Jul 19 11:11:24 PM_SC-1 amf_demo[31113]: 1. saAmfComponentRegister FAILED, But Continueing 14
Jul 19 11:11:24 PM_SC-1 amf_demo[31113]: HC started with AMF for 1
Jul 19 11:11:24 PM_SC-1 amf_demo[31113]: Registered with AMF
Jul 19 11:11:24 PM_SC-1 amf_demo[31113]: Health check 1
Jul 19 11:11:34 PM_SC-1 amf_demo[31113]: Health check 2
Jul 19 11:11:44 PM_SC-1 amf_demo[31113]: Health check 3
Jul 19 11:11:54 PM_SC-1 amf_demo[31113]: Health check 4
The response was given to Amf 4.1 callback.
So, marking as invalid