Hi Erich, As Hunje raised issue as below, Still problem in the master branch. Could you share the timeline to fix it? Our release preparation is dependent on this bug. ------------------------------------------------------------------------------------------------------------------- I encoutered another presence issue when testing in master branch, I created JIRA ticket for this issue, (https://jira.iotivity.org/browse/IOT-597), and report via mailing list. Please check below.
* Presence is not working in master branch : Server app. crashes when presence is requested from client side. * Clue : In the /resource/src/InProcClientWrapper.cpp Line 819, os << host << "/oc/presence"; is not changed yet. : As I know, current presence URI is "/oic/ad"; * When I change URI to "/oic/ad", it isn't crashed but "No resource" error is returned when server receives presence request. *Tested version : - Title : Fix memory leak in SSM Sensor Processor - Change ID : I3d2363ed0b2585ffcbc403417fd73f60e89f1a88 -----Original Message----- From: Keane, Erich [mailto:[email protected]] Sent: Wednesday, July 08, 2015 1:33 AM To: Lankswert, Patrick Cc: iotivity-dev at lists.iotivity.org; uzchoi at samsung.com; hunje.yeon at samsung.com Subject: Re: [dev] presence is not working I believe we had an effort to attempt to get the presence fixed, though i thought it went in. Uze, are you still seeing the presence issue with latest master? ------------------------------------------------------------------------------------------------------------------------------------------ On Tue, 2015-07-07 at 15:12 +0000, Lankswert, Patrick wrote: > Uze, > > There are issues running system tests on the build machines and should > not be done. Only unit tests can be run on the build machines. > > Pat > > > > From:???(Uze Choi) [mailto:uzchoi at samsung.com] > Sent: Monday, July 06, 2015 9:42 PM > To: Lankswert, Patrick; Keane, Erich > Cc: hunje.yeon at samsung.com; iotivity-dev at lists.iotivity.org > Subject: RE: [dev] presence is not working > > > > > Pat/Erich, > > Due to this problem, whole service modules cannot pass any test case > and we have been stopped to implement service logic. > Fixing this defect ASAP could make the this coming 0.9.2 release > possible. > Furthermore, If possible, could you add this test case of the presence > checking into Jenkins build verification? > > BR, Uze Choi > > From:iotivity-dev-bounces at lists.iotivity.org > [mailto:iotivity-dev-bounces at lists.iotivity.org] On Behalf Of ??? > Sent: Monday, July 06, 2015 11:36 PM > To: iotivity-dev at lists.iotivity.org > Subject: [dev] presence is not working > > > > > Hi All, > > > > I am encountered presence problem when testing with presence client > sample. > > (with Change-Id: I3d2363ed0b2585ffcbc403417fd73f60e89f1a88, 2nd July > version of master branch) > > I ran the presenceclient sample like below and it stops following > with wait message after 'send fails' > > Is there problems on sending presences in recent update? > > > > ./presenceclient -t 1 -c 0 > > DISCOVERED Resource: > URI of the resource: /a/light > Host address of the resource: coap://10.251.43.17:48996 List of > resource types: > core.light > List of resource interfaces: > oic.if.baseline > 54:43.029 INFO: OCStack: Entering OCDoResource > 54:43.029 DEBUG: CA: CAGenerateToken > 54:43.029 DEBUG: CA: IN > 54:43.029 DEBUG: CA: token len:8, token: > 54:43.033 DEBUG: CA: F4 3C EB 23 D3 82 EC B2 > 54:43.033 DEBUG: CA: OUT > 54:43.033 INFO: occlientcb: Callback Not found !! > 54:43.033 DEBUG: CA: CASendGetRequest > 54:43.033 DEBUG: CA: IN > 54:43.033 DEBUG: UQUEUE: Queue Count : 1 > 54:43.033 DEBUG: CA: OUT > Subscribed to unicast address: coap://10.251.43.17:48996 > 54:43.033 DEBUG: CA: wake up.. > 54:43.033 DEBUG: CA: IN > 54:43.033 DEBUG: CA: requestInfo is available.. > 54:43.033 DEBUG: CA: IN > 54:43.033 DEBUG: CA: IN > 54:43.033 DEBUG: CA: url : coap://[::]/ > 54:43.033 DEBUG: CA: OUT > 54:43.033 DEBUG: CA: IN > 54:43.033 DEBUG: CA: parse Head Opt: 0 > 54:43.033 DEBUG: CA: OUT > 54:43.033 DEBUG: CA: IN > 54:43.033 DEBUG: CA: msgID is 0 > 54:43.033 DEBUG: CA: gen msg id=5630 > 54:43.033 DEBUG: CA: messageId in pdu is 5630, 5630 > 54:43.033 DEBUG: CA: token info token length: 8, token : > 54:43.033 DEBUG: CA: F4 3C EB 23 D3 82 EC B2 > 54:43.033 DEBUG: CA: OUT > 54:43.033 DEBUG: CA: OUT > 54:43.033 DEBUG: CA: PDU Maker - payload : (null) > 54:43.033 DEBUG: CA: PDU Maker - type : 1 > 54:43.033 DEBUG: CA: PDU Maker - code : 1 > 54:43.033 DEBUG: CA: PDU Maker - id : 65045 > 54:43.033 DEBUG: CA: PDU Maker - token : > 54:43.033 DEBUG: CA: F4 3C EB 23 D3 82 EC B2 > 54:43.033 DEBUG: CA: Send unicast data to enabled interface.. > 54:43.033 DEBUG: CA: CA_TRANSPORT_TYPE_NUM is not 3 > 54:43.033 ERROR: CA: unknown transport type! > 54:43.033 ERROR: CA: send failed:1 > 54:43.033 DEBUG: CA: IN > 54:43.033 DEBUG: CA: OUT > 54:43.033 DEBUG: CA: wait.. > > > > > > Thanks in advance > > > > Hun-je > > > > > > =============================================== > > > > > > HUN-JE YEON (???) > > > > Senior Engineer, Advanced Convergence Lab > > Software R&D Center > > Samsung Electronics Co., Ltd. > > > > Tel] +82-10-9454-4650 > > E-mail]hunje.yeon at samsung.com > > > > =============================================== > > > > > > > > > > > > > > Samsung Electronics Co., Ltd. > > > > Tel] +82-10-9454-4650 > > E-mail] hunje.yeon at samsung.com > > > > =============================================== > > > > > > > > > > > > > > Tel] +82-10-9454-4650 > > E-mail] hunje.yeon at samsung.com > > > > =============================================== > > > > > > > > > >
