Application hangs on afcs reconnect

[Ali_Hasan]

I am testing my air application, that uses afcs, i guess air uses IE proxy settings on windows machine. For testing I unchcked proxy settings of IE to see afcs reconnect behavior, I run the application and found that it hangs when afcs try to reconnect.To narrow it down further I made a separate sample, blow is the sample code and its log.

<?xml version="1.0" encoding="utf-8"?>
<mx:WindowedApplication xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute" xmlns:authentication="com.adobe.rtc.authentication.*" xmlns:session="com.adobe.rtc.session.*" xmlns:util="com.adobe.rtc.util.*">
     <authentication:AdobeHSAuthenticator id="auth" userName="xxxxxxxxxxxxxxxxxxxxxx" password="xxxxxxxxx"/>
     <session:ConnectSessionContainer id="cSession" authenticator="{auth}"
         roomURL="http://connectnow.acrobat.com/xxxxxxxxxx/xxxxxxxxxxxx">
         <mx:Canvas width="100%" height="100%">
         </mx:Canvas>
     </session:ConnectSessionContainer>
</mx:WindowedApplication>

log:

AFCS Beta Build # : 1.01
requestInfo http://connectnow.acrobat.com/xxxxxxx/xxxxxxx?mode=xml&glt=g:&x=0.5786033966578543
authentication status: 200
authentication request complete
requestInfo http://connectnow.acrobat.com/xxxxxxx/xxxxxxx?gak=cmVuZ2EqbmExcioxMjVkYWRkNWRkNioyOVozMFNZMUhIMk1EQT...
Getting FMS at https://na2.connectnow.acrobat.com/fms?ticket=n18xrwf854hz, attempt #1/3
result: <fms>
  <origin>fms2.acrobat.com</origin>
  <proto_ports>rtmps:443</proto_ports>
  <retry_attempts>2</retry_attempts>
</fms>
#FMSConnector# Tue Dec 29 19:35:02 GMT+0500 2009 protocols: [object ProtocolPortPair]
#FMSConnector# Tue Dec 29 19:35:02 GMT+0500 2009 [attempt 1 of 2] Connecting to 0/0: rtmps://fms2.acrobat.com/cocomo/na2-03256801-79cc-423c-9287-dd99b747b35c/xxxxxxx#startProtosConnect#
#FMSConnector# Tue Dec 29 19:35:10 GMT+0500 2009 onTimeOutTimerComplete
#FMSConnector# Tue Dec 29 19:35:10 GMT+0500 2009 [attempt 1 of 2] Trying fallback tunneling connection rtmps://fms2.acrobat.com/cocomo/na2-03256801-79cc-423c-9287-dd99b747b35c/xxxxxxx#onTimeOutTimerComplete#
#FMSConnector# Tue Dec 29 19:35:18 GMT+0500 2009 onTimeOutTimerComplete
#FMSConnector# Tue Dec 29 19:35:18 GMT+0500 2009     incOriginsIndex: _originsIndex now:0 (origin:fms2.acrobat.com)
#FMSConnector# Tue Dec 29 19:37:18 GMT+0500 2009 [attempt 2 of 2] Connecting to 0/0: rtmps://fms2.acrobat.com/cocomo/na2-03256801-79cc-423c-9287-dd99b747b35c/xxxxxxx#startProtosConnect#
#FMSConnector# Tue Dec 29 19:37:25 GMT+0500 2009 onTimeOutTimerComplete
#FMSConnector# Tue Dec 29 19:37:25 GMT+0500 2009 [attempt 2 of 2] Trying fallback tunneling connection rtmps://fms2.acrobat.com/cocomo/na2-03256801-79cc-423c-9287-dd99b747b35c/xxxxxxx#onTimeOutTimerComplete#
#FMSConnector# Tue Dec 29 19:37:34 GMT+0500 2009 onTimeOutTimerComplete
#FMSConnector# Tue Dec 29 19:37:34 GMT+0500 2009     incOriginsIndex: _originsIndex now:0 (origin:fms2.acrobat.com)
#FMSConnector# Tue Dec 29 19:39:27 GMT+0500 2009 startProtosConnect calling onDoneRetryingTimerComplete
Getting FMS at https://na2.connectnow.acrobat.com/fms?ticket=n18xrwf854hz&connect-error=true&origin=fms2.acrobat.co..., attempt #2/3
result: <fms>
  <origin>fms4.acrobat.com</origin>
  <proto_ports>rtmps:443</proto_ports>
  <retry_attempts>2</retry_attempts>
</fms>
#FMSConnector# Tue Dec 29 19:39:28 GMT+0500 2009 protocols: [object ProtocolPortPair]
#FMSConnector# Tue Dec 29 19:39:28 GMT+0500 2009 [attempt 1 of 2] Connecting to 0/0: rtmps://fms4.acrobat.com/cocomo/na2-03256801-79cc-423c-9287-dd99b747b35c/xxxxxxx#startProtosConnect#
#FMSConnector# Tue Dec 29 19:39:36 GMT+0500 2009 onTimeOutTimerComplete
#FMSConnector# Tue Dec 29 19:39:36 GMT+0500 2009 [attempt 1 of 2] Trying fallback tunneling connection rtmps://fms4.acrobat.com/cocomo/na2-03256801-79cc-423c-9287-dd99b747b35c/xxxxxxx#onTimeOutTimerComplete#
#FMSConnector# Tue Dec 29 19:39:44 GMT+0500 2009 onTimeOutTimerComplete
#FMSConnector# Tue Dec 29 19:39:44 GMT+0500 2009     incOriginsIndex: _originsIndex now:0 (origin:fms4.acrobat.com)
#FMSConnector# Tue Dec 29 19:41:19 GMT+0500 2009 [attempt 2 of 2] Connecting to 0/0: rtmps://fms4.acrobat.com/cocomo/na2-03256801-79cc-423c-9287-dd99b747b35c/xxxxxxx#startProtosConnect#
#FMSConnector# Tue Dec 29 19:41:27 GMT+0500 2009 onTimeOutTimerComplete
#FMSConnector# Tue Dec 29 19:41:27 GMT+0500 2009 [attempt 2 of 2] Trying fallback tunneling connection rtmps://fms4.acrobat.com/cocomo/na2-03256801-79cc-423c-9287-dd99b747b35c/xxxxxxx#onTimeOutTimerComplete#
#FMSConnector# Tue Dec 29 19:41:35 GMT+0500 2009 onTimeOutTimerComplete
#FMSConnector# Tue Dec 29 19:41:35 GMT+0500 2009    incOriginsIndex: _originsIndex now:0 (origin:fms4.acrobat.com)

At this stage application becomes unresponsive, when I try to resize it just hangs, it spcifically hags at the bold lines in log.

[ithinking]

@afcs dev team , please reply.

[Raff_]

Is this still a problem ?

Looking at the logs the room never managed to succesfully connect to our server, so it could be something at the network level (a firewall that doesn't let rtmps traffic go through ?)

It could also be a problem with the particular room in question (but we do try to connect to the room before returning the connection URL) but I can't really verify that since the information in the log has been obfuscated.

[Ali_Hasan]

This is a test case for the senario where clients computers proxy setting are not correct. In that case cocomo(lccs) should simply raise error after certain number of tries. I guess there might be an infinite loop bug in reconnect code that makes the app unresponsive.

[Ali_Hasan]

We have noticed that

          1)  Cocomo started disconnecting frequently, even when internet is working fine.

          2)  When it is about to disconnect it hangs the app for sometime and then get disconnected.

          3)  During startup(at login time) and reconnect(after getting disconnected) it again hangs the app.

          4)  Application always connects at rtmps:443 even when network is not behind a firewall, should'nt it connect at rtmp:1935?

Please advise

[Former Community Member]

Hi Ali,

It seems as though you have some kind of network issue - specifically for

1), ConnectNow is based on Cocomo, and we use it all the time for web

conferencing, without the issue you mention here.

2)-3) As for hanging the app, I haven't seen this either - what else is

occurring in the app that might be doing intense processing?

4) We always connect with rtmps, which uses 443 (and uses SSL encryption)

just as https does. Why should it connect on 1935?

Are you behind a firewall with packet sniffing enabled to disallow non-http

traffic?

nigel

[Former Community Member]

Hi Ali,

Just to follow up, I ran some tests on our side that refuse connections

based on rtmps, and eventually I got a "TOOMANYATTEMPTS" Session Error. No

hanging though - I was able to resize the app the whole time.

nigel