Dear Mr. Murshed, Many thanks for your response. It solved my problem. I wasn't aware that the MQ feature is covered by the OIC specification.
Regards, Martin R?sch Von: Md. Golam Sarwar [mailto:sarwar.mgm at samsung.com] Gesendet: Dienstag, 11. Juli 2017 11:09 An: Roesch Martin; 'iotivity-dev at lists.iotivity.org' Betreff: RE: [dev] MQ Publisher example: create topic error Hello Martin R?sch ?According to oic specification, you need to provide topic URI like this (oic/ps/topicName) Thanks & Regards Md. Golam Sarwar Murshed Sr. Software Engineer SWE Group Samsung R&D Institute Bangladesh Mobile: +880-1723755957 Email: sarwar.mgm at samsung.com ? ? --------- Original Message --------- Sender : Martin Roesch?<Martin.Roesch at kistler.com> Date : 2017-07-10 19:51 (GMT+6) Title : [dev] MQ Publisher example: create topic error To : null<iotivity-dev at lists.iotivity.org> ? Hi everybody, I'm having problems getting the MQ Publisher example working: Create topic fails with code 134 (INTERNAL_SERVER_ERROR) ./mq_publisher 127.0.0.1:5683 easydev 1 Auth response received code: 4 accesstoken: 26492ff9-1ff0-4042-80d4-4735fb4a053c certificate: (null) expiresin: -1 redirecturi: coap+tcp://127.0.0.1:5683 refreshtoken: 26492ff9-1ff0-4042-80d4-4735fb4a053c sid: 2a6085d1-815d-4277-baba-4e4e4df91308 tokentype: bearer uid: abf6d0ac-5e9f-4176-9084-986730f7b23f Auth response received code: 4 expiresin: -1 ===Message Queue publisher sample=== PUT 0 to discover all topics PUT 1 to discover type based topics PUT 2 to select topic index for publishing data PUT 3 to publish data to selected topic PUT 4 to create topic PUT 5 to create type based topic 4 Put topic uri to create: /testtopic Create topic response received, code: 134 Topic creation failed : /testtopic The relevant log from the cloud interface server: 2017-07-10 13:40:40:235 [V] 00000013-9985b1dc2afc443f-f50fbf6e 89797c31260652e8 PUT /testtopic CT:APPLICATION_CBOR SZ:2 P:{} 2017-07-10 13:40:40:237 [V] 00000013-9985b1dc2afc443f-f50fbf6e 89797c31260652e8 5.00 Internal Server Error 2017-07-10 13:40:40:241 [V] 00000013-9985b1dc2afc443f-f50fbf6e INTERNAL_SERVER_ERROR, Unsupport URI Does anybody have a clue what the problem with the URI coud be? FYI: I'm using IoTivity 1.3.0 (scons WITH_TCP=yes RELEASE=yes WITH_CLOUD=yes WITH_MQ=PUB,SUB SECURED=0) and the Cloud in docker containers on localhost with a custom OAuth provider 'easydev'. Regards, Martin R?sch _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
