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, "[email protected]" <[email protected]> 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! >> >> >
