Skip to content

Big problems with flex-side message receiver #12

Open
@GoogleCodeExporter

Description

@GoogleCodeExporter
What steps will reproduce the problem?
1. Send a lot of (big) messages from Java to Air


What is the expected output? 
We should get every message sent from java-side

What do you see instead?

Some,initial bunch of messages is beeing processed; rest (due to 
DESERIALIZATION error) is dropped.
In my opinion error is caused by wrong assumption that every Java message 
could be processed before arrival of another one. And that's not true (as 
you can easy reproduce with my CrashTest example)


I've rewriten (and refactored for readability) a bit of merapi's core, to 
be more error-proof in that use case. Hovewer there is still one issue - 
memory leak caused by AMF3Reader. When we do a lot of bridge 
communication, great ammount of messages is beeing created, and i cannot 
figure out how to force them to vanish :/

Attached file contains sample CrashTest Flex+Java projects, along with my 
version of merapi's library, and patches

Original issue reported on code.google.com by [email protected] on 20 Feb 2010 at 5:51

Attachments:

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions