Inconsistence responses from the LCCS service

[ZeevH]

Greetings from the middle east ....

We are experiencing inconsistence responses from the LCCS service

The following problems happen SOMETIMES, once in every 10 minutes or so

1.

On the j2ee server:

when trying to :

https://na2.collaboration.adobelivecycle.com:443/.....?mode=xml&room=.........&template=.....&gak=.....

The create room returns: 

Server returned HTTP response code: 401 for URL: https://na2.collaboration.adobelivecycle.com:...

2.

In the AS application, when we try to connect to a room created by "createRoom"

flash response from LCCS:

INVALID_INSTANCE: Invalid Instance

   at com.adobe.rtc.session.managers::SessionManagerBase/receiveError()[E:\flashfarm\branches\connect\1106\SDKApp\payload\libs\flashOnly\player10\src\com\adobe\rtc\session\managers\SessionManagerBase.as:324]

   at com.adobe.rtc.session.managers::SessionManagerFMS/receiveError()[E:\flashfarm\branches\connect\1106\SDKApp\payload\libs\flashOnly\player10\src\com\adobe\rtc\session\managers\SessionManagerFMS.as:309]

   at com.adobe.rtc.session.managers::SessionManagerAdobeHostedServices/receiveError()[E:\flashfarm\branches\connect\1106\SDKApp\payload\libs\flashOnly\player10\src\com\adobe\rtc\session\managers\SessionManagerAdobeHostedServices.as:284]

   at com.adobe.rtc.session.managers::SessionManagerAdobeHostedServices/onMeetingError()[E:\flashfarm\branches\connect\1106\SDKApp\payload\libs\flashOnly\player10\src\com\adobe\rtc\session\managers\SessionManagerAdobeHostedServices.as:111]

   at flash.events::EventDispatcher/dispatchEventFunction()

   at flash.events::EventDispatcher/dispatchEvent()

   at com.adobe.rtc.session.sessionClasses::MeetingInfoService/onError()[E:\flashfarm\branches\connect\1106\SDKApp\payload\libs\flashOnly\player10\src\com\adobe\rtc\session\sessionClasses\MeetingInfoService.as:463]

   at flash.events::EventDispatcher/dispatchEventFunction()

   at flash.events::EventDispatcher/dispatchEvent()

   at flash.net::URLLoader/onComplete() 

Please advice,

Regards,

Zeev

[Raff_]

I can tell you that #1 happens every time after exactly 15 minutes of inactivity. Basically the developer authentication tokens are invalidated after 15 minutes of inactivity so if you are accessing our server via the AccountManager API more frequently than 15 minutes your tokens will stay "active". If you stop calling us the token will expire after 15 minutes of inactivity.

The two options here are to trap the 401 error and login again or to use the keepAlive method in AuthenticationManager by having a thread sleep for, for example, 10 minutes and then call keepAlive to "refresh" the token.

The error in #2 is more subtle and its hard to tell you what is happening without seeing the complete logs of your application (unless you are just passing a wrong URL / wrong room name to the service when connecting). Does this also happens quite frequently ? How frequently ? What does your application do ?