[tickets] [opensaf:tickets] #1739 Logsv is providing same active handle value for different api calls
- **status**: unassigned --> accepted - **assigned_to**: Vu Minh Nguyen - **Milestone**: 4.6.2 --> 5.0.RC2 --- ** [tickets:#1739] Logsv is providing same active handle value for different api calls** **Status:** accepted **Milestone:** 5.0.RC2 **Created:** Thu Apr 07, 2016 11:48 AM UTC by Ritu Raj **Last Updated:** Mon Apr 11, 2016 11:51 AM UTC **Owner:** Vu Minh Nguyen Setup: Changeset- 7436 Version - opensaf 5.0 Issue : Logsv is issuing same active handle value for different api calls Steps: -> The logsv application stores the global system stream handle and for couple of scenarios , initialization and finalization has been done. -> At the startup of the application, system stream handle (4288675841) is obtained. -> After couple of flows, the initialization api saLogInitialize() obtained same handle ( 4288675841) and was finalized. -> So when saLogWriteLogAsync() api is invoked with the earlier obtained system stream handle, it is returning SA_AIS_ERR_BAD_HANDLE. Note that the init handle associated with the system stream handle 4288675841 is not finalized. 100|0|Invoking saLogInitialize() 100|0| Return value : <-- SA_AIS_OK 100|0| Handle obtained is 4290772993 100|0|Invoking saLogStreamOpen_2() 100|0|Handle used is 4290772993 100|0| Return value : <-- SA_AIS_OK 100|0| Handle obtained is 4288675841 100|0|Invoking saLogStreamOpen_2() 100|0|Handle used is 4290772993 100|0| Return value : <-- SA_AIS_OK 100|0| Handle obtained is 4287627265 100|0|Invoking saLogStreamOpen_2() 100|0|Handle used is 4290772993 100|0| Return value : <-- SA_AIS_OK 100|0| Handle obtained is 4286578689 100|0|system stream handle 4288675841 ... 100|0|Invoking saLogInitialize() 100|0| Return value : <-- SA_AIS_OK 100|0| Handle obtained is 4288675841 100|0|Invoking saLogFinalize() 100|0| Handle used is 4288675841 100|0| Return value : <-- SA_AIS_OK 100|0|Invoking saLogSelectionObjectGet() 100|0| Return value : <-- SA_AIS_ERR_BAD_HANDLE 100|0|Invoking saLogWriteLogAsync() 100|0|Handle used is 4288675841 100|0| Return value : <-- SA_AIS_ERR_BAD_HANDLE 100|0|saLogWriteLogAsync return values did not match Actual_Value :9 Expected_Value :1 This application used to work with 4.7 --- 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.-- Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1739 Logsv is providing same active handle value for different api calls
The above sequence was done in one process osaflogd trace and Agent log file attached. Please, note that even same handle is also obtained in saLogInitialize() Attachments: - [logsv.trace](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/e863d596/d2cd/attachment/logsv.trace) (49.8 kB; application/octet-stream) - [osaflogd](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/e863d596/d2cd/attachment/osaflogd) (973.1 kB; application/octet-stream) --- ** [tickets:#1739] Logsv is providing same active handle value for different api calls** **Status:** unassigned **Milestone:** 4.6.2 **Created:** Thu Apr 07, 2016 11:48 AM UTC by Ritu Raj **Last Updated:** Fri Apr 08, 2016 07:30 AM UTC **Owner:** nobody Setup: Changeset- 7436 Version - opensaf 5.0 Issue : Logsv is issuing same active handle value for different api calls Steps: -> The logsv application stores the global system stream handle and for couple of scenarios , initialization and finalization has been done. -> At the startup of the application, system stream handle (4288675841) is obtained. -> After couple of flows, the initialization api saLogInitialize() obtained same handle ( 4288675841) and was finalized. -> So when saLogWriteLogAsync() api is invoked with the earlier obtained system stream handle, it is returning SA_AIS_ERR_BAD_HANDLE. Note that the init handle associated with the system stream handle 4288675841 is not finalized. 100|0|Invoking saLogInitialize() 100|0| Return value : <-- SA_AIS_OK 100|0| Handle obtained is 4290772993 100|0|Invoking saLogStreamOpen_2() 100|0|Handle used is 4290772993 100|0| Return value : <-- SA_AIS_OK 100|0| Handle obtained is 4288675841 100|0|Invoking saLogStreamOpen_2() 100|0|Handle used is 4290772993 100|0| Return value : <-- SA_AIS_OK 100|0| Handle obtained is 4287627265 100|0|Invoking saLogStreamOpen_2() 100|0|Handle used is 4290772993 100|0| Return value : <-- SA_AIS_OK 100|0| Handle obtained is 4286578689 100|0|system stream handle 4288675841 ... 100|0|Invoking saLogInitialize() 100|0| Return value : <-- SA_AIS_OK 100|0| Handle obtained is 4288675841 100|0|Invoking saLogFinalize() 100|0| Handle used is 4288675841 100|0| Return value : <-- SA_AIS_OK 100|0|Invoking saLogSelectionObjectGet() 100|0| Return value : <-- SA_AIS_ERR_BAD_HANDLE 100|0|Invoking saLogWriteLogAsync() 100|0|Handle used is 4288675841 100|0| Return value : <-- SA_AIS_ERR_BAD_HANDLE 100|0|saLogWriteLogAsync return values did not match Actual_Value :9 Expected_Value :1 This application used to work with 4.7 --- 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.-- Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/ gampad/clk?id=1444514301=/ca-pub-7940484522588532___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1739 Logsv is providing same active handle value for different api calls
The above sequence was done in one process or in two? 1) On one process This could be an strange point! The question should come to Handle Mananger (`ncshm_create_hdl`), out of logsv scope, how it comes to have one handle ID for 2 times calling to `ncshm_create_hdl`. If this is the case, I will re-check the code and ask person in charge of handle manager. 2) On two processes I tried but not be able to reproduce the same phenomenon as yours. Can you help to collect the Agent/service trace log? --- ** [tickets:#1739] Logsv is providing same active handle value for different api calls** **Status:** unassigned **Milestone:** 4.6.2 **Created:** Thu Apr 07, 2016 11:48 AM UTC by Ritu Raj **Last Updated:** Thu Apr 07, 2016 11:48 AM UTC **Owner:** nobody Setup: Changeset- 7436 Version - opensaf 5.0 Issue : Logsv is issuing same active handle value for different api calls Steps: -> The logsv application stores the global system stream handle and for couple of scenarios , initialization and finalization has been done. -> At the startup of the application, system stream handle (4288675841) is obtained. -> After couple of flows, the initialization api saLogInitialize() obtained same handle ( 4288675841) and was finalized. -> So when saLogWriteLogAsync() api is invoked with the earlier obtained system stream handle, it is returning SA_AIS_ERR_BAD_HANDLE. Note that the init handle associated with the system stream handle 4288675841 is not finalized. 100|0|Invoking saLogInitialize() 100|0| Return value : <-- SA_AIS_OK 100|0| Handle obtained is 4290772993 100|0|Invoking saLogStreamOpen_2() 100|0|Handle used is 4290772993 100|0| Return value : <-- SA_AIS_OK 100|0| Handle obtained is 4288675841 100|0|Invoking saLogStreamOpen_2() 100|0|Handle used is 4290772993 100|0| Return value : <-- SA_AIS_OK 100|0| Handle obtained is 4287627265 100|0|Invoking saLogStreamOpen_2() 100|0|Handle used is 4290772993 100|0| Return value : <-- SA_AIS_OK 100|0| Handle obtained is 4286578689 100|0|system stream handle 4288675841 ... 100|0|Invoking saLogInitialize() 100|0| Return value : <-- SA_AIS_OK 100|0| Handle obtained is 4288675841 100|0|Invoking saLogFinalize() 100|0| Handle used is 4288675841 100|0| Return value : <-- SA_AIS_OK 100|0|Invoking saLogSelectionObjectGet() 100|0| Return value : <-- SA_AIS_ERR_BAD_HANDLE 100|0|Invoking saLogWriteLogAsync() 100|0|Handle used is 4288675841 100|0| Return value : <-- SA_AIS_ERR_BAD_HANDLE 100|0|saLogWriteLogAsync return values did not match Actual_Value :9 Expected_Value :1 This application used to work with 4.7 --- 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.-- ___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1739 Logsv is providing same active handle value for different api calls
--- ** [tickets:#1739] Logsv is providing same active handle value for different api calls** **Status:** unassigned **Milestone:** 4.6.2 **Created:** Thu Apr 07, 2016 11:48 AM UTC by Ritu Raj **Last Updated:** Thu Apr 07, 2016 11:48 AM UTC **Owner:** nobody Setup: Changeset- 7436 Version - opensaf 5.0 Issue : Logsv is issuing same active handle value for different api calls Steps: -> The logsv application stores the global system stream handle and for couple of scenarios , initialization and finalization has been done. -> At the startup of the application, system stream handle (4288675841) is obtained. -> After couple of flows, the initialization api saLogInitialize() obtained same handle ( 4288675841) and was finalized. -> So when saLogWriteLogAsync() api is invoked with the earlier obtained system stream handle, it is returning SA_AIS_ERR_BAD_HANDLE. Note that the init handle associated with the system stream handle 4288675841 is not finalized. 100|0|Invoking saLogInitialize() 100|0| Return value : <-- SA_AIS_OK 100|0| Handle obtained is 4290772993 100|0|Invoking saLogStreamOpen_2() 100|0|Handle used is 4290772993 100|0| Return value : <-- SA_AIS_OK 100|0| Handle obtained is 4288675841 100|0|Invoking saLogStreamOpen_2() 100|0|Handle used is 4290772993 100|0| Return value : <-- SA_AIS_OK 100|0| Handle obtained is 4287627265 100|0|Invoking saLogStreamOpen_2() 100|0|Handle used is 4290772993 100|0| Return value : <-- SA_AIS_OK 100|0| Handle obtained is 4286578689 100|0|system stream handle 4288675841 ... 100|0|Invoking saLogInitialize() 100|0| Return value : <-- SA_AIS_OK 100|0| Handle obtained is 4288675841 100|0|Invoking saLogFinalize() 100|0| Handle used is 4288675841 100|0| Return value : <-- SA_AIS_OK 100|0|Invoking saLogSelectionObjectGet() 100|0| Return value : <-- SA_AIS_ERR_BAD_HANDLE 100|0|Invoking saLogWriteLogAsync() 100|0|Handle used is 4288675841 100|0| Return value : <-- SA_AIS_ERR_BAD_HANDLE 100|0|saLogWriteLogAsync return values did not match Actual_Value :9 Expected_Value :1 This application used to work with 4.7 --- 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.-- ___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
