Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Three potential solutions for you:</p> <ol> <li><p>I found once that if I hit a remote object before setting up a messaging channel then the CientID would get screwed up. Try to establish an initial messaging channel once the application loads, and before any remote object calls are made.</p></li> <li><p>Flash Builder's network monitoring tool can cause some problems with BlazeDS. I set up a configuration option on application load that checks to see if I'm in the dev environment (it is called just before setting up my channel from #1). If I'm in dev, I assign a UID manually. For some reason this doesn't take well outside the dev environment... been awhile since I set it all up so I can't remember the finer points as to why:</p> <pre><code>if (!(AppSettingsModel.getInstance().dev)) FlexClient.getInstance().id = UIDUtil.createUID(); </code></pre></li> <li><p>BlazeDS by default only allows for a single HTTP session to be setup per client/browser. In my streaming channel definitions I added the following to allow for additional sessions per browser:</p> <pre><code>&lt;channel-definition id="my-secure-amf-stream" class="mx.messaging.channels.SecureStreamingAMFChannel"&gt; &lt;endpoint url="https://{server.name}:{server.port}/FlexClient/messagebroker/securestreamingamf" class="flex.messaging.endpoints.SecureStreamingAMFEndpoint"/&gt; &lt;properties&gt; &lt;add-no-cache-headers&gt;false&lt;/add-no-cache-headers&gt; &lt;idle-timeout-minutes&gt;0&lt;/idle-timeout-minutes&gt; &lt;max-streaming-clients&gt;10&lt;/max-streaming-clients&gt; &lt;server-to-client-heartbeat-millis&gt;5000&lt;/server-to-client-heartbeat-millis&gt; &lt;user-agent-settings&gt; &lt;user-agent match-on="MSIE" kickstart-bytes="2048" max-streaming-connections-per-session="3" /&gt; &lt;user-agent match-on="Firefox" kickstart-bytes="2048" max-streaming-connections-per-session="3" /&gt; &lt;/user-agent-settings&gt; &lt;/properties&gt; </code></pre></li> </ol>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload