Thanks, I will take a try in  this way. Have a good day! :-)

Regards,
Jianfeng

-----Original Message-----
From: Zoran Milinkovic [mailto:zoran.milinko...@ericsson.com] 
Sent: Wednesday, March 22, 2017 12:04 AM
To: Jianfeng Dong <jd...@juniper.net>; opensaf-users@lists.sourceforge.net
Subject: RE: Question about ticket 1617

Hi,

That were steps to reproduce the problem in OpenSAF 4.5 without changing the 
code.

BR,
Zoran

-----Original Message-----
From: Jianfeng Dong [mailto:jd...@juniper.net] 
Sent: den 21 mars 2017 16:58
To: Zoran Milinkovic <zoran.milinko...@ericsson.com>; 
opensaf-users@lists.sourceforge.net
Subject: RE: Question about ticket 1617

Thank you Zoran, much appreciate for your so detailed description!

And, do you know any way to reproduce the issue without changing any OpenSAF 
code? I'm not familiar with OpenSAf's source code, and it will cost much 
time(probably more than one day) to build the modified OpenSAF in our build 
environment.

Thanks,
Jianfeng

-----Original Message-----
From: Zoran Milinkovic [mailto:zoran.milinko...@ericsson.com] 
Sent: Monday, March 20, 2017 11:15 PM
To: Jianfeng Dong <jd...@juniper.net>; opensaf-users@lists.sourceforge.net
Subject: RE: Question about ticket 1617

Hi Jianfeng,

Ticket #47 (https://sourceforge.net/p/opensaf/tickets/47/) has implemented 
search handle timeout on 10 minutes.
The ticket has been pushed to OpenSAF 4.5.

To produce the problem you describe below in OpenSAF 4.5, first, you need to 
call searchInitialize function, then change time forward for more than 10 
minutes, and after that start calling searchNext.
Be aware that searchNext request to IMMND can pull more search results at once 
and then searchNext works client locally. That's done for the performance 
issue. Because of that some searchNext calls will work after 10 minutes, until 
the next searchNext request is sent to IMMND.
If you change time just after searchInitialize, you will be able to see the 
timeout immediately.

Ticket #1617 (https://sourceforge.net/p/opensaf/tickets/1617/) has changed the 
use of system time with monotonic time, so that the case above cannot happen.

Thanks,
Zoran

-----Original Message-----
From: Jianfeng Dong [mailto:jd...@juniper.net] 
Sent: den 20 mars 2017 15:46
To: opensaf-users@lists.sourceforge.net
Subject: [users] Question about ticket 1617

Hi,



We have a bug seems related with ticket 1617( 
https://sourceforge.net/p/opensaf/tickets/1617/ ), now we just found OpenSAF 
5.0 has resolved the issue, but we don't know how to reproduce the issue in our 
release with OpenSAF 4.5.2, thus we can confirm it is caused by the ticket 1617 
indeed and it is gone in our new release with OpenSAF 5.0.



So, could you please kindly tell us how to reproduce the issue of ticket 1617 
in release 4.5.2 with an easy or stable way? Thanks in advance!





Here is the log when the issue happened, seems it was caused by the system time 
changing while OpenSAF is waiting for something....



2015-11-18T14:12:12.624742-05:00 pld0113 logger: Synced time with server 
100.100.0.1

2015-11-18T14:12:12.627585-05:00 pld0113 logger: Set hardware clock

2015-11-18T14:12:12.635408-05:00 pld0113 osafimmnd[3427]: NO Clear 1 search 
result(s) for OM handle 3500010d0f. Search timeout 600sec

2015-11-18T14:12:12.635563-05:00 pld0113 osafimmnd[3427]: ER Could not find 
search node for search-ID:54

2015-11-18T14:12:12.635853-05:00 pld0113 osafamfnd[3536]: saImmOmSearchNext 
FAILED, rc = 9

2015-11-18T14:12:12.649634-05:00 pld0113 osafimmnd[3427]: NO Implementer 
connected: 23 (MsgQueueService68879) <0, 10f0f>

2015-11-18T14:12:12.651858-05:00 pld0113 osafimmnd[3427]: NO Implementer 
disconnected 23 <0, 10f0f> (MsgQueueService68879)

2015-11-18T14:12:13.525888-05:00 pld0113 ntpd[3557]: ntpd 
4.2.6p5@1.2349-o<mailto:4.2.6p5@1.2349-o> Fri Nov  6 19:29:25 UTC 2015 (2)



2015-11-06T14:44:07.488664-05:00 pld0107 osafclmna[3531]: Started

2015-11-06T14:44:07.492894-05:00 pld0107 osafclmna[3531]: NO 
safNode=pld0107,safCluster=myClmCluster Joined cluster, nodeid=1070f

2015-11-06T14:44:07.523654-05:00 pld0107 osafamfnd[3540]: Started

2015-11-18T15:14:40.889384-05:00 pld0107 osafimmnd[3431]: NO Clear 1 search 
result(s) for OM handle d0001070f. Search timeout 600sec

2015-11-18T15:14:40.893124-05:00 pld0107 logger: Synced time with server 
100.100.0.1

2015-11-18T15:14:40.894797-05:00 pld0107 osafimmnd[3431]: ER Could not find 
search node for search-ID:14

2015-11-18T15:14:40.895280-05:00 pld0107 osafamfnd[3540]: saImmOmSearchNext 
FAILED, rc = 9

2015-11-18T15:14:40.896828-05:00 pld0107 logger: Set hardware clock

2015-11-18T15:14:40.915801-05:00 pld0107 osafimmnd[3431]: NO Implementer 
connected: 28 (MsgQueueService67343) <0, 10f0f>

2015-11-18T15:14:40.920772-05:00 pld0107 osafimmnd[3431]: NO Implementer 
disconnected 28 <0, 10f0f> (MsgQueueService67343)





Thanks,

Jianfeng


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most engaging tech 
sites, Slashdot.org! http://sdm.link/slashdot 
_______________________________________________
Opensaf-users mailing list
Opensaf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-users

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-users mailing list
Opensaf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-users

Reply via email to