[Red5] triggering the dreaded "long connection" error
dsgirard at gmail.com
Wed Nov 5 17:09:13 PST 2008
thanks for the response dan!
this error occurs for me on every request... I am only connecting
manually; this is not a performance test. I'm not able to connect to
my app at all under the conditions I described.
On Wed, Nov 5, 2008 at 5:01 PM, Daniel Rossi <electroteque at gmail.com> wrote:
> I'm experiencing this when im hitting the server but delay the interval of
> the requests the longer the delay I will get the handshake error.
> On 06/11/2008, at 11:36 AM, devon girard wrote:
>> I know I am not alone here, and through a ground-up custom-app
>> implementation I've isolated my issue to a single line in my appJoin
>> IConnection current = Red5.getConnectionLocal();
>> without this line my bare-bones app works fine; add it in, and it is
>> invisible... and starts provoking the "long handshake" error.
>> my theory is the static call to Red5 causes the
>> org.red5.server.api.Red5 class to be imported....and as others have
>> mentioned, duplicate library imports seem to conflict in 0.8.
>> My question, what to do??
>> Red5 mailing list
>> Red5 at osflash.org
> Red5 mailing list
> Red5 at osflash.org
More information about the Red5