You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@flex.apache.org by ma...@crispico.com on 2013/07/03 21:48:18 UTC
Error #2032 on mobile devices
Hello,
We have started testing our mobile application from our devices (Android
smartphone/tablet) and we are able to connect to our server through a
BlazeDS streaming channel; however, we get Error #2023 at seemingly random
moments. What we've noticed: the error always occurs after displaying some
text in a TextArea, however it may happen at any moment, for no apparent
reason.
We are able to use the app just fine from a desktop web browser and from
the AIR mobile simulator using the streaming channel, this problem only
happens with a mobile device, and only with the streaming channel.
Any suggestions are greatly appreciated!
Re: Error #2032 on mobile devices
Posted by Mariana Gheorghe <ma...@crispico.com>.
Sorry for taking long to update on our issue. We haven't been able to find
the reason we are getting the error, however we've discovered it is in
fact not random at all: the error occurs every 40 seconds, in which time
the communication works fine. These are our settings for the streaming
channel:
<channel-definition id="blazedsStreamingAMFChannel"
class="mx.messaging.channels.StreamingAMFChannel">
<endpoint
url="http://{server.name}:{server.port}/{context.root}/messagebroker/streamingamf"
class="org.flowerplatform.blazeds.endpoint.FlowerWebSecureStreamingAMFEndpoint"/>
<properties>
<!--
Number of milliseconds to wait to write an empty message to the client.
In current context it does not really help us.
<server-to-client-heartbeat-millis>10000</server-to-client-heartbeat-millis>
If nothing is sent to the client, the server will disconnect the client.
This does not invalidate the flex client on server side.
In current context it does not really help us.
<idle-timeout-minutes>1</idle-timeout-minutes>
-->
<serialization>
<log-property-errors>true</log-property-errors>
</serialization>
<user-agent-settings>
<!-- MSIE 8 limit is 6. -->
<user-agent match-on="MSIE" max-persistent-connections-per-session="5"
kickstart-bytes="2048"/>
<!-- Firefox 3 limit is 6. -->
<user-agent match-on="Firefox"
max-persistent-connections-per-session="5"/>
<!-- Safari 3, 4 limit is 4. -->
<user-agent match-on="Safari" max-persistent-connections-per-session="3"/>
<!-- Chrome 0, 1, 2 limit is 6. -->
<user-agent match-on="Chrome" max-persistent-connections-per-session="5"/>
<user-agent match-on="*" max-persistent-connections-per-session="3"/>
</user-agent-settings>
</properties>
</channel-definition>
Again, our app works fine from a desktop browser and even from the AIR
simulator, this issue only occurs on an Android device. What can cause a
streaming error every 40 seconds in this case?
> I apologize for the confusion, the problem we are facing is indeed
>
>> Error #2032: Stream Error. URL:
> http://188.27.183.186:8080/org.flowerplatform.web.app/messagebroker/streamingamf?command=open&version=1
>
> The URL is fine, but for some reason the message does not get through to
> the server. Is it possible that the communication drops if the application
> freezes for a moment? For example, if we're displaying a large text in a
> TextArea, the app will hang a bit on a mobile device. May this be a
> reason? Even though, as I mentioned, the error seems to happen randomly,
> without this being the case.
>
> And another thing, the app is able to reconnect to the server and
> communicate normally afterwards, until of course we get that streaming
> error again, and the cycle repeats itself.
>
>> Hello,
>>
>> We have started testing our mobile application from our devices (Android
>> smartphone/tablet) and we are able to connect to our server through a
>> BlazeDS streaming channel; however, we get Error #2023 at seemingly
>> random
>> moments. What we've noticed: the error always occurs after displaying
>> some
>> text in a TextArea, however it may happen at any moment, for no apparent
>> reason.
>>
>> We are able to use the app just fine from a desktop web browser and from
>> the AIR mobile simulator using the streaming channel, this problem only
>> happens with a mobile device, and only with the streaming channel.
>>
>> Any suggestions are greatly appreciated!
>>
>>
>
>
Re: Error #2032 on mobile devices
Posted by Carl Kelvin <ca...@yahoo.com>.
HiĀ
Try to re-install and install your adobe air. Don't forget clear cache. For some reason maybe you have slow connection when you try to send the message it makes the apps hangs up. Error #2032 is a stream-error.
________________________________
From: Alex Harui <ah...@adobe.com>
To: "users@flex.apache.org" <us...@flex.apache.org>
Sent: Saturday, July 6, 2013 10:31 PM
Subject: Re: Error #2032 on mobile devices
Flexcapacitor's blog contains a great article on error #2032
http://www.judahfrangipane.com/blog/2007/02/15/error-2032-stream-error/
Try getting the HTTP_RESPONSE_STATUS event as suggested in the post and
see if that additional information provides useful clues.
-Alex
On 7/6/13 12:39 AM, "mariana.gheorghe@crispico.com"
<ma...@crispico.com> wrote:
>I apologize for the confusion, the problem we are facing is indeed
>
>> Error #2032: Stream Error. URL:
>http://188.27.183.186:8080/org.flowerplatform.web.app/messagebroker/stream
>ingamf?command=open&version=1
>
>The URL is fine, but for some reason the message does not get through to
>the server. Is it possible that the communication drops if the application
>freezes for a moment? For example, if we're displaying a large text in a
>TextArea, the app will hang a bit on a mobile device. May this be a
>reason? Even though, as I mentioned, the error seems to happen randomly,
>without this being the case.
>
>And another thing, the app is able to reconnect to the server and
>communicate normally afterwards, until of course we get that streaming
>error again, and the cycle repeats itself.
>
>> Hello,
>>
>> We have started testing our mobile application from our devices (Android
>> smartphone/tablet) and we are able to connect to our server through a
>> BlazeDS streaming channel; however, we get Error #2023 at seemingly
>>random
>> moments. What we've noticed: the error always occurs after displaying
>>some
>> text in a TextArea, however it may happen at any moment, for no apparent
>> reason.
>>
>> We are able to use the app just fine from a desktop web browser and from
>> the AIR mobile simulator using the streaming channel, this problem only
>> happens with a mobile device, and only with the streaming channel.
>>
>> Any suggestions are greatly appreciated!
>>
>>
>
Re: Error #2032 on mobile devices
Posted by Alex Harui <ah...@adobe.com>.
Flexcapacitor's blog contains a great article on error #2032
http://www.judahfrangipane.com/blog/2007/02/15/error-2032-stream-error/
Try getting the HTTP_RESPONSE_STATUS event as suggested in the post and
see if that additional information provides useful clues.
-Alex
On 7/6/13 12:39 AM, "mariana.gheorghe@crispico.com"
<ma...@crispico.com> wrote:
>I apologize for the confusion, the problem we are facing is indeed
>
>> Error #2032: Stream Error. URL:
>http://188.27.183.186:8080/org.flowerplatform.web.app/messagebroker/stream
>ingamf?command=open&version=1
>
>The URL is fine, but for some reason the message does not get through to
>the server. Is it possible that the communication drops if the application
>freezes for a moment? For example, if we're displaying a large text in a
>TextArea, the app will hang a bit on a mobile device. May this be a
>reason? Even though, as I mentioned, the error seems to happen randomly,
>without this being the case.
>
>And another thing, the app is able to reconnect to the server and
>communicate normally afterwards, until of course we get that streaming
>error again, and the cycle repeats itself.
>
>> Hello,
>>
>> We have started testing our mobile application from our devices (Android
>> smartphone/tablet) and we are able to connect to our server through a
>> BlazeDS streaming channel; however, we get Error #2023 at seemingly
>>random
>> moments. What we've noticed: the error always occurs after displaying
>>some
>> text in a TextArea, however it may happen at any moment, for no apparent
>> reason.
>>
>> We are able to use the app just fine from a desktop web browser and from
>> the AIR mobile simulator using the streaming channel, this problem only
>> happens with a mobile device, and only with the streaming channel.
>>
>> Any suggestions are greatly appreciated!
>>
>>
>
Re: Error #2032 on mobile devices
Posted by ma...@crispico.com.
I apologize for the confusion, the problem we are facing is indeed
> Error #2032: Stream Error. URL:
http://188.27.183.186:8080/org.flowerplatform.web.app/messagebroker/streamingamf?command=open&version=1
The URL is fine, but for some reason the message does not get through to
the server. Is it possible that the communication drops if the application
freezes for a moment? For example, if we're displaying a large text in a
TextArea, the app will hang a bit on a mobile device. May this be a
reason? Even though, as I mentioned, the error seems to happen randomly,
without this being the case.
And another thing, the app is able to reconnect to the server and
communicate normally afterwards, until of course we get that streaming
error again, and the cycle repeats itself.
> Hello,
>
> We have started testing our mobile application from our devices (Android
> smartphone/tablet) and we are able to connect to our server through a
> BlazeDS streaming channel; however, we get Error #2023 at seemingly random
> moments. What we've noticed: the error always occurs after displaying some
> text in a TextArea, however it may happen at any moment, for no apparent
> reason.
>
> We are able to use the app just fine from a desktop web browser and from
> the AIR mobile simulator using the streaming channel, this problem only
> happens with a mobile device, and only with the streaming channel.
>
> Any suggestions are greatly appreciated!
>
>
RE: Error #2032 on mobile devices
Posted by Kessler CTR Mark J <ma...@usmc.mil>.
I only get 2032 errors with HTTP styled communication failures. So if you have a server call running in the background and the connection to the server drops it might give you that error.
-Mark
-----Original Message-----
From: mariana.gheorghe@crispico.com [mailto:mariana.gheorghe@crispico.com]
Sent: Wednesday, July 03, 2013 3:48 PM
To: users@flex.apache.org
Subject: Error #2032 on mobile devices
Hello,
We have started testing our mobile application from our devices (Android
smartphone/tablet) and we are able to connect to our server through a
BlazeDS streaming channel; however, we get Error #2023 at seemingly random
moments. What we've noticed: the error always occurs after displaying some
text in a TextArea, however it may happen at any moment, for no apparent
reason.
We are able to use the app just fine from a desktop web browser and from
the AIR mobile simulator using the streaming channel, this problem only
happens with a mobile device, and only with the streaming channel.
Any suggestions are greatly appreciated!
Re: Error #2032 on mobile devices
Posted by jude <fl...@gmail.com>.
Is the error 2023 or 2032? Is the connection slower through the mobile
device? It could be a timeout. It could be images on another server.
On Wednesday, July 3, 2013, wrote:
> Hello,
>
> We have started testing our mobile application from our devices (Android
> smartphone/tablet) and we are able to connect to our server through a
> BlazeDS streaming channel; however, we get Error #2023 at seemingly random
> moments. What we've noticed: the error always occurs after displaying some
> text in a TextArea, however it may happen at any moment, for no apparent
> reason.
>
> We are able to use the app just fine from a desktop web browser and from
> the AIR mobile simulator using the streaming channel, this problem only
> happens with a mobile device, and only with the streaming channel.
>
> Any suggestions are greatly appreciated!
>
>
Re: Error #2032 on mobile devices
Posted by Carlos Monteiro <cm...@wavesolutions.pt>.
That error can also happen with desktop browsers.
In diferent client machines while testing between chrome and IE it can
happen on one of them or in worst case on both.
Os Melhores Cumprimentos,
[image: anexo de assinatura email_youtube_96dpi
-02]<http://www.youtube.com/user/wavesolutions>
****
**
[image: Inline images 1]
cmonteiro@wavesolutions.pt | www.wavesolutions.pt | 253 824 293
On 3 July 2013 21:28, Lee Burrows <su...@leeburrows.com> wrote:
> Ignore my suggestion - i was looking at "#2023" in the body, not "#2032"
> in the title; 2023 is a display list error - hence my StageText suspicion.
>
>
> On 03/07/2013 21:01, Lee Burrows wrote:
>
>> I've never had that RTE, but as you suspect TextArea and its a mobile
>> app, try setting the TextArea skin to spark.skins.mobile.**TextAreaSkin
>> (rather than the default spark.skins.mobile.**StageTextAreaSkin).
>>
>> StageText does tend to cause issues that arent apparent when testing in
>> simulator
>>
>> On 03/07/2013 20:48, mariana.gheorghe@crispico.com wrote:
>>
>>> Hello,
>>>
>>> We have started testing our mobile application from our devices (Android
>>> smartphone/tablet) and we are able to connect to our server through a
>>> BlazeDS streaming channel; however, we get Error #2023 at seemingly
>>> random
>>> moments. What we've noticed: the error always occurs after displaying
>>> some
>>> text in a TextArea, however it may happen at any moment, for no apparent
>>> reason.
>>>
>>> We are able to use the app just fine from a desktop web browser and from
>>> the AIR mobile simulator using the streaming channel, this problem only
>>> happens with a mobile device, and only with the streaming channel.
>>>
>>> Any suggestions are greatly appreciated!
>>>
>>>
>>>
>>
>>
>
> --
> Lee Burrows
> ActionScripter
>
>
Re: Error #2032 on mobile devices
Posted by Prem Radhakrishnan <go...@gmail.com>.
My 2c . If its 2032 I have also seen it when a moduleloader is trying to
load an unavailable module. I dont think this could be the case here but
anyway
Perfection is achieved, not when there is nothing more to add, but when
there is nothing left to take away.
- Antoine de Saint-Exupery
On Wed, Jul 3, 2013 at 4:28 PM, Lee Burrows <su...@leeburrows.com>wrote:
> Ignore my suggestion - i was looking at "#2023" in the body, not "#2032"
> in the title; 2023 is a display list error - hence my StageText suspicion.
>
>
> On 03/07/2013 21:01, Lee Burrows wrote:
>
>> I've never had that RTE, but as you suspect TextArea and its a mobile
>> app, try setting the TextArea skin to spark.skins.mobile.**TextAreaSkin
>> (rather than the default spark.skins.mobile.**StageTextAreaSkin).
>>
>> StageText does tend to cause issues that arent apparent when testing in
>> simulator
>>
>> On 03/07/2013 20:48, mariana.gheorghe@crispico.com wrote:
>>
>>> Hello,
>>>
>>> We have started testing our mobile application from our devices (Android
>>> smartphone/tablet) and we are able to connect to our server through a
>>> BlazeDS streaming channel; however, we get Error #2023 at seemingly
>>> random
>>> moments. What we've noticed: the error always occurs after displaying
>>> some
>>> text in a TextArea, however it may happen at any moment, for no apparent
>>> reason.
>>>
>>> We are able to use the app just fine from a desktop web browser and from
>>> the AIR mobile simulator using the streaming channel, this problem only
>>> happens with a mobile device, and only with the streaming channel.
>>>
>>> Any suggestions are greatly appreciated!
>>>
>>>
>>>
>>
>>
>
> --
> Lee Burrows
> ActionScripter
>
>
Re: Error #2032 on mobile devices
Posted by Lee Burrows <su...@leeburrows.com>.
Ignore my suggestion - i was looking at "#2023" in the body, not "#2032"
in the title; 2023 is a display list error - hence my StageText suspicion.
On 03/07/2013 21:01, Lee Burrows wrote:
> I've never had that RTE, but as you suspect TextArea and its a mobile
> app, try setting the TextArea skin to spark.skins.mobile.TextAreaSkin
> (rather than the default spark.skins.mobile.StageTextAreaSkin).
>
> StageText does tend to cause issues that arent apparent when testing
> in simulator
>
> On 03/07/2013 20:48, mariana.gheorghe@crispico.com wrote:
>> Hello,
>>
>> We have started testing our mobile application from our devices (Android
>> smartphone/tablet) and we are able to connect to our server through a
>> BlazeDS streaming channel; however, we get Error #2023 at seemingly
>> random
>> moments. What we've noticed: the error always occurs after displaying
>> some
>> text in a TextArea, however it may happen at any moment, for no apparent
>> reason.
>>
>> We are able to use the app just fine from a desktop web browser and from
>> the AIR mobile simulator using the streaming channel, this problem only
>> happens with a mobile device, and only with the streaming channel.
>>
>> Any suggestions are greatly appreciated!
>>
>>
>
>
--
Lee Burrows
ActionScripter
Re: Error #2032 on mobile devices
Posted by Lee Burrows <su...@leeburrows.com>.
I've never had that RTE, but as you suspect TextArea and its a mobile
app, try setting the TextArea skin to spark.skins.mobile.TextAreaSkin
(rather than the default spark.skins.mobile.StageTextAreaSkin).
StageText does tend to cause issues that arent apparent when testing in
simulator
On 03/07/2013 20:48, mariana.gheorghe@crispico.com wrote:
> Hello,
>
> We have started testing our mobile application from our devices (Android
> smartphone/tablet) and we are able to connect to our server through a
> BlazeDS streaming channel; however, we get Error #2023 at seemingly random
> moments. What we've noticed: the error always occurs after displaying some
> text in a TextArea, however it may happen at any moment, for no apparent
> reason.
>
> We are able to use the app just fine from a desktop web browser and from
> the AIR mobile simulator using the streaming channel, this problem only
> happens with a mobile device, and only with the streaming channel.
>
> Any suggestions are greatly appreciated!
>
>
--
Lee Burrows
ActionScripter
Re: Error #2032 on mobile devices
Posted by Alex Harui <ah...@adobe.com>.
You mention #2032 in the subject, and #2023 in the body. Which is it?
Please post the exact text including the full message and any stack trace.
On 7/3/13 12:48 PM, "mariana.gheorghe@crispico.com"
<ma...@crispico.com> wrote:
>Hello,
>
>We have started testing our mobile application from our devices (Android
>smartphone/tablet) and we are able to connect to our server through a
>BlazeDS streaming channel; however, we get Error #2023 at seemingly random
>moments. What we've noticed: the error always occurs after displaying some
>text in a TextArea, however it may happen at any moment, for no apparent
>reason.
>
>We are able to use the app just fine from a desktop web browser and from
>the AIR mobile simulator using the streaming channel, this problem only
>happens with a mobile device, and only with the streaming channel.
>
>Any suggestions are greatly appreciated!
>