Session management problem

asked 2014-12-12 01:54:41 -0700

PierreR gravatar image

I've run into a problem with session management : I have a setup with several alljoyn nodes on different devices, which are all in the same multipoint session, hosted by a device called A. As the devices are mobile devices it can happens that one of the device loose is connection to the network. It that case I have the the follow behavior

  • device B loose it's network connection
  • B does not receives the sessionLost callback
  • when B connects backs, it tries to communicates on the session and it fails
  • as the session seems to be invalid, B tries to join again the session but get an ALLJOYN_JOINSESSION_REPLY_ALREADY_JOINED error code
  • then I try to leave the session but I also get an error : ALLJOYN_LEAVESESSION_REPLY_NO_SESSION

At that point, the device B is stuck : it cannot use the session, cannot leave it and cannot join it back either.

Any idea ? Maybe I have overlooked something ...

edit retag flag offensive close merge delete


It looks to me like you have run into a bug. If you can generate a simple way to reproduce this bug that would be helpful. I would report this to the https://jira.allseenalliance.org

georgen ( 2014-12-16 14:54:58 -0700 )edit

This sounds similar to https://jira.allseenalliance.org/browse/ASACORE-1005 .

msanu ( 2014-12-17 10:45:01 -0700 )edit

I would suggest downloading the AllJoyn 14.12 release and see if your problem has been fixed. Since ASACORE-1005 shows that the issue was fixed for the 14.12 release.

georgen ( 2014-12-18 10:34:13 -0700 )edit

I reproduced the same behavior with the 14.06. I've downloaded the 14.12, and the problem is fixed :)

eguiho ( 2014-12-19 04:58:24 -0700 )edit

Great news, thanks @eguiho :)

PierreR ( 2014-12-19 05:57:02 -0700 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2014-12-19 08:02:25 -0700

georgen gravatar image

updated 2014-12-19 08:03:03 -0700

This issue was reported to the AllSeen Jira ticket ASACORE-1005

The ticket was closed as fixed an the fix was released as part of the AllJoyn 14.12 release

@eguiho reported that he was seeing the same behavior with the 14.06 release and found the problem was fixed when he switched to the 14.12 release.

The solution for the issue is to move to the latest release.

edit flag offensive delete publish link more
Login/Signup to Answer

Question Tools



Asked: 2014-12-12 01:54:41 -0700

Seen: 2,335 times

Last updated: Dec 19 '14