{"action":"closed","issue":{"url":"https://api.github.com/repos/IRATI/stack/issues/829","repository_url":"https://api.github.com/repos/IRATI/stack","labels_url":"https://api.github.com/repos/IRATI/stack/issues/829/labels{/name}","comments_url":"https://api.github.com/repos/IRATI/stack/issues/829/comments","events_url":"https://api.github.com/repos/IRATI/stack/issues/829/events","html_url":"https://github.com/IRATI/stack/issues/829","id":123777894,"number":829,"title":"Pristine-1.4: Multiple instances of AE with the same name in the same node","user":{"login":"kewinrausch","id":8994703,"avatar_url":"https://avatars.githubusercontent.com/u/8994703?v=3","gravatar_id":"","url":"https://api.github.com/users/kewinrausch","html_url":"https://github.com/kewinrausch","followers_url":"https://api.github.com/users/kewinrausch/followers","following_url":"https://api.github.com/users/kewinrausch/following{/other_user}","gists_url":"https://api.github.com/users/kewinrausch/gists{/gist_id}","starred_url":"https://api.github.com/users/kewinrausch/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kewinrausch/subscriptions","organizations_url":"https://api.github.com/users/kewinrausch/orgs","repos_url":"https://api.github.com/users/kewinrausch/repos","events_url":"https://api.github.com/users/kewinrausch/events{/privacy}","received_events_url":"https://api.github.com/users/kewinrausch/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-12-24T09:00:01Z","updated_at":"2016-02-11T09:15:04Z","closed_at":"2016-02-11T09:15:04Z","body":"If I launch an AE with the **same name on the same node**, there should be the application instance left in order to differentiate the communication. But running multiple clients with the same name on the same machine does make it happens, and they share instance 1 (name-1). When a flow is then closed, all the flows with the same name(but they got different port id) are closed, even if they did not want this (see last log).\r\n\r\nThis issue is similar to https://github.com/IRATI/stack/issues/779, which was on different client machine but same destination server.\r\n\r\nClient side log of 1st instance on server 3:\r\nScript args, just as note, are: client.sh client_name server_name interval(0 = continuous) exp_time avg _bandwidth(0 = do not care)\r\n```\r\nkrausch@s3:~/scripts$ sh client.sh s3 s1 0 60 0\r\n21429(1450946304)#librina.logs (DBG): New log level: INFO\r\n21429(1450946304)#librina.nl-manager (INFO): Netlink socket connected to local port 21429\r\n21429(1450946304)#traffic-generator (INFO): starting test\r\nactivity_int: 0\r\n21429(1450946364)#traffic-generator (INFO): sent statistics:     45052 SDUs,     63072800 bytes in  60089112 us, 8.3972 Mb/s\r\n```\r\n\r\nClient side log of 1st instance on server 3:\r\n```\r\nkrausch@s3:~/scripts$ sh client.sh  s3 s1 0 60 0\r\n21461(1450946310)#librina.logs (DBG): New log level: INFO\r\n21461(1450946310)#librina.nl-manager (INFO): Netlink socket connected to local port 21461\r\n21461(1450946310)#traffic-generator (INFO): starting test\r\nactivity_int: 0\r\n21461(1450946370)#traffic-generator (INFO): sent statistics:     45058 SDUs,     63081200 bytes in  60091465 us, 8.3980 Mb/s\r\n```\r\n\r\nNOTE: You can distinguish the two only because one is launched 5 second later.\r\nServer side log are:\r\n```\r\nkrausch@s1:~/scripts$ sh server.sh s1 5000\r\n22852(1450946301)#librina.logs (DBG): New log level: INFO\r\n22852(1450946301)#librina.nl-manager (INFO): Netlink socket connected to local port 22852\r\n22852(1450946304)#traffic-generator (INFO): New flow allocated [port-id = 3]\r\nPort,SDUs,bytes,us,p/s,Mb/s\r\ns3-client-1, 3268, 4575200, 5.5002, 653.330078, 7.317297\r\n22852(1450946310)#traffic-generator (INFO): New flow allocated [port-id = 4]\r\nPort,SDUs,bytes,us,p/s,Mb/s\r\ns3-client-1, 3517, 4923800, 10.5180, 678.897461, 7.603652\r\ns3-client-1, 3406, 4768400, 5.5288, 644.047424, 7.213332\r\ns3-client-1, 3083, 4316200, 15.5070, 607.980530, 6.809382\r\ns3-client-1, 3536, 4950400, 10.5126, 689.694397, 7.724578\r\ns3-client-1, 3332, 4664800, 20.5006, 665.585999, 7.454563\r\ns3-client-1, 3889, 5444600, 15.5264, 738.692322, 8.273354\r\ns3-client-1, 3674, 5143600, 25.5438, 675.582947, 7.566529\r\ns3-client-1, 3474, 4863600, 20.5103, 680.757446, 7.624484\r\ns3-client-1, 3066, 4292400, 30.5143, 596.128174, 6.676636\r\ns3-client-1, 3832, 5364800, 25.5268, 727.362183, 8.146457\r\ns3-client-1, 3245, 4543000, 35.5122, 633.463013, 7.094786\r\ns3-client-1, 3525, 4935000, 30.5118, 688.741943, 7.713910\r\ns3-client-1, 3362, 4706800, 40.5235, 642.199097, 7.192629\r\ns3-client-1, 3819, 5346600, 35.5280, 723.181763, 8.099636\r\ns3-client-1, 3402, 4762800, 45.5507, 617.739929, 6.918687\r\ns3-client-1, 3547, 4965800, 40.5099, 695.567200, 7.790353\r\ns3-client-1, 3138, 4393200, 50.5006, 626.777039, 7.019903\r\ns3-client-1, 3891, 5447400, 45.5239, 742.641846, 8.317589\r\ns3-client-1, 3886, 5440400, 55.5215, 745.032532, 8.344364\r\ns3-client-1, 3550, 4970000, 50.5586, 635.496765, 7.117564\r\ns3-client-1, 3449, 4828600, 60.5307, 649.788147, 7.277627\r\n22852(1450946364)#traffic-generator (INFO): >>>> s3-client-1, 40422 SDUs, 56590800 bytes in 60307 ms, 7.507029 Mb/s\r\ns3-client-1, 3688, 5163200, 55.5236, 704.274841, 7.887878\r\n22852(1450946370)#traffic-generator (INFO): Flow torn down remotely [port-id = 3]\r\n22852(1450946370)#traffic-generator (INFO): Flow torn down remotely [port-id = 4]\r\ns3-client-1, 3763, 5268200, 60.5345, 703.958557, 7.884336\r\n22852(1450946370)#traffic-generator (INFO): >>>> s3-client-1, 43920 SDUs, 61488000 bytes in 60345 ms, 8.151529 Mb/s\r\n```\r\n\r\nLog of the ipcm on the server:\r\n```\r\n20518(1450946304)#ipcm.flow-alloc (INFO)[flow_allocation_requested_remote]: Arrived request for flow allocation between s1-server:1:: and s3-client:1::\r\n20518(1450946304)#ipcm.flow-alloc (INFO)[allocate_flow_response_event_handler]: : Informing IPC process s1.dc:1:: about flow allocation from application s1-server:1:: to application s3-client:1:: in DIF dc::: [success = 1, port-id = 3]\r\n20518(1450946310)#ipcm.flow-alloc (INFO)[flow_allocation_requested_remote]: Arrived request for flow allocation between s1-server:1:: and s3-client:1::\r\n20518(1450946310)#ipcm.flow-alloc (INFO)[allocate_flow_response_event_handler]: : Informing IPC process s1.dc:1:: about flow allocation from application s1-server:1:: to application s3-client:1:: in DIF dc::: [success = 1, port-id = 4]\r\n```\r\n\r\nLog of the ipcm on the client:\r\n```\r\n18954(1450946304)#ipcm.flow-alloc (INFO)[flow_allocation_requested_local]: IPC process s3.dc:1:: requested to allocate flow between s3-client:1:: and s1-server:1::\r\n18954(1450946304)#ipcm.flow-alloc (INFO)[ipcm_allocate_flow_request_result_handler]: Informing IPC process s3.dc:1:: about flow allocation from application s3-client:1:: to application s1-server:1:: in DIF dc::: [success = 1, port-id = 3]\r\n18954(1450946304)#ipcm.flow-alloc (INFO)[ipcm_allocate_flow_request_result_handler]: Applications s3-client:1:: and s1-server:1:: informed about flow allocation result\r\n18954(1450946310)#ipcm.flow-alloc (INFO)[flow_allocation_requested_local]: IPC process s3.dc:1:: requested to allocate flow between s3-client:1:: and s1-server:1::\r\n18954(1450946310)#ipcm.flow-alloc (INFO)[ipcm_allocate_flow_request_result_handler]: Informing IPC process s3.dc:1:: about flow allocation from application s3-client:1:: to application s1-server:1:: in DIF dc::: [success = 1, port-id = 4]\r\n18954(1450946310)#ipcm.flow-alloc (INFO)[ipcm_allocate_flow_request_result_handler]: Applications s3-client:1:: and s1-server:1:: informed about flow allocation result\r\n```\r\n\r\nOn even more concurrent flows it happens the follow:\r\n```\r\nterminate called after throwing an instance of 'rina::FlowNotAllocatedException'\r\n  what():  Invalid operation invoked when the flow is not allocated\r\nAborted\r\n```"}}