Thanks for the suggestion, but I doubt that's the case since these same
calls work 95% of the time.  The NetworkError only intermittently occurs.
I still think it relates to our available connection pool getting filled
up, but I've tried monkeying with the configuration of Apache and Tomcat to
no apparent effect.  For example, Apache is set to not keep connections
alive by default, and in the Tomcat server.xml file I tried adding
maxThreads="400" and keepAliveTimeout="2" to every uncommented Connector.
However, I could go to my website from my browser and simultaneously use "
netstat --tcp | grep (myIPAddress)" to watch my browser's connection stay
alive for 60 seconds no matter what I placed in keepAliveTimeout.

On Fri, Nov 29, 2013 at 11:06 PM, Alan Holden <[email protected]> wrote:

>  Your Network Error could be a permissions/security issue. AJAX calls can
> not be made to a server on "another domain" without that server's cross
> domain permission. I think that violation throws the code 19 you describe.
>
> For example, you're calling your ajax by local/partial URL, calling by
> host name when the browser loaded the page by IP, calling with an
> unexpected protocol; or truly calling across domains. Things have to match
> up pretty much to the letter. Many folks have switched from classic AJAX to
> JSONP to bypass this sandbox restriction.
>
> Al
>
>

-- 
-- 
online documentation: http://openbd.org/manual/
 http://groups.google.com/group/openbd?hl=en

--- 
You received this message because you are subscribed to the Google Groups "Open 
BlueDragon" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to