{"action":"created","issue":{"url":"https://api.github.com/repos/aws/aws-iot-device-sdk-js/issues/48","repository_url":"https://api.github.com/repos/aws/aws-iot-device-sdk-js","labels_url":"https://api.github.com/repos/aws/aws-iot-device-sdk-js/issues/48/labels{/name}","comments_url":"https://api.github.com/repos/aws/aws-iot-device-sdk-js/issues/48/comments","events_url":"https://api.github.com/repos/aws/aws-iot-device-sdk-js/issues/48/events","html_url":"https://github.com/aws/aws-iot-device-sdk-js/issues/48","id":145823969,"number":48,"title":"Competition between thingShadows generated with same client id but different certificates","user":{"login":"wjy617","id":7648203,"avatar_url":"https://avatars.githubusercontent.com/u/7648203?v=3","gravatar_id":"","url":"https://api.github.com/users/wjy617","html_url":"https://github.com/wjy617","followers_url":"https://api.github.com/users/wjy617/followers","following_url":"https://api.github.com/users/wjy617/following{/other_user}","gists_url":"https://api.github.com/users/wjy617/gists{/gist_id}","starred_url":"https://api.github.com/users/wjy617/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wjy617/subscriptions","organizations_url":"https://api.github.com/users/wjy617/orgs","repos_url":"https://api.github.com/users/wjy617/repos","events_url":"https://api.github.com/users/wjy617/events{/privacy}","received_events_url":"https://api.github.com/users/wjy617/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":12,"created_at":"2016-04-04T22:41:05Z","updated_at":"2016-04-19T00:39:59Z","closed_at":null,"body":"I have created two different thingShadows with two different groups of keyPath, certPath, caPath and region (both generated from same AWS account), but with same clientId. Each one works well individually, but when they start at the same time, they will compete with each other and both show \"connection lost - will attempt reconnection\". Is this normal? If not, how can I fix this problem? \r\n\r\nThanks"},"comment":{"url":"https://api.github.com/repos/aws/aws-iot-device-sdk-js/issues/comments/211655107","html_url":"https://github.com/aws/aws-iot-device-sdk-js/issues/48#issuecomment-211655107","issue_url":"https://api.github.com/repos/aws/aws-iot-device-sdk-js/issues/48","id":211655107,"user":{"login":"gkwicker","id":14828980,"avatar_url":"https://avatars.githubusercontent.com/u/14828980?v=3","gravatar_id":"","url":"https://api.github.com/users/gkwicker","html_url":"https://github.com/gkwicker","followers_url":"https://api.github.com/users/gkwicker/followers","following_url":"https://api.github.com/users/gkwicker/following{/other_user}","gists_url":"https://api.github.com/users/gkwicker/gists{/gist_id}","starred_url":"https://api.github.com/users/gkwicker/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gkwicker/subscriptions","organizations_url":"https://api.github.com/users/gkwicker/orgs","repos_url":"https://api.github.com/users/gkwicker/repos","events_url":"https://api.github.com/users/gkwicker/events{/privacy}","received_events_url":"https://api.github.com/users/gkwicker/received_events","type":"User","site_admin":false},"created_at":"2016-04-19T00:39:59Z","updated_at":"2016-04-19T00:39:59Z","body":"Hi @wjy617, we are able to duplicate the issue you observed here.  The root cause is that shadow operations have a client token associated with them which is generated from the client ID and a running integer count.  The maximum length for this client token is 64 bytes.  So, to use the shadow APIs, you'll want to make sure that your client ID is considerably less than 64 bytes to allow for a large number of client token values.  This restriction on client ID length doesn't exist when using the MQTT publish/subscribe APIs.  We will look into workarounds for the shadow API client ID length limitation in a future release.  Thanks for letting us know about this, and thanks for using AWS IoT."}}