Unknown AMF type 46 when invoking multiple java methods

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a sample Project
2. create a Loop like
for(var i:int = 0; i < 100; i++)
{
   javaObject.method(dataObject);
}
(while dataObject is an Object with some key/value pairs, around 50 in my case)
3. run the loop

What is the expected output? What do you see instead?

I expect every method call to be executed one by one,
instead the next call seems to be executed while the first is still transfering 
data.
So i get:
Error: Error deserializing received AMF object: 
SIflex.messaging.messages.ErrorMessageheadersrootCause  bodycorrelationIdfa
ultDetailfaultStringclientIdtimeToLivedestinationtimestampextendedDatafau
ltCodemessageId




}flex.messaging.io.UnknownTypeException: Unknown AMF type '46'.-Unknown 
AMF type '46'.


What version of the product are you using? On what operating system?
Flerry 1.2.0, Flex4, Win 7

Please provide any additional information below.

Original issue reported on code.google.com by julak...@gmail.com on 29 Sep 2010 at 4:08

[GoogleCodeExporter]

Hello julakali, try putting the following lines after  out.write(byteArray) in 
NativeObject.sendMessage():

out.flush();
Thread.sleep(100);

this is just a workaround, but worked for me. As you can notice, the 
performance will be bad.  I'll try to get a definitive solution. The problem is 
that when sending from java multiple messages in a short period, they arrive in 
flex together as if they were only one. 

Original comment by khronnuz@gmail.com on 29 Nov 2010 at 9:37

• Changed state: Accepted

[GoogleCodeExporter]

Can we get the status of the NativeObject???...whether the object is currently 
running or not?...

Original comment by vichu.wi...@gmail.com on 19 Jan 2011 at 10:32

[GoogleCodeExporter]

Hello khronnuz, 

I've tried your workaround, but the error still occurs. Perhaps this is because 
my java methods took some time to complete. Are there other possible workaround?

Thanks

Original comment by pan....@gmail.com on 27 Jan 2011 at 2:39

[GoogleCodeExporter]

Issue 11 has been merged into this issue.

Original comment by khronnuz@gmail.com on 25 Jul 2011 at 5:37

[GoogleCodeExporter]

Problem is that there's only one data channel (standardOutput ) and an error 
channel(standardError). Both Java->Flex and Flex->Java calls goes through data 
channel; I think a solution to this problem could be use data channel only to 
Flex-java calls, make all those calls sync. Then use error channel for 
subscriptions ( Java-Flex)

I Will try that soon. 

Original comment by khronnuz@gmail.com on 25 Jul 2011 at 5:53

[GoogleCodeExporter]

Hi there,

I keep getting this error in flerry.

Error: Error deserializing received AMF object: 
SIflex.messaging.messages.ErrorMessageheadersrootCause  bodycorrelationIdfa
ultDetailfaultStringclientIdtimeToLivedestinationtimestampextendedDatafau
ltCodemessageId




}flex.messaging.io.UnknownTypeException: Unknown AMF type '99'.-Unknown 
AMF type '99'.


I have looked around but no solution. This problem happens when pushing data 
from Java to Flex. Hope there is a solution to this. Thanks

Original comment by ao.adew...@gmail.com on 3 Nov 2011 at 2:55

[GoogleCodeExporter]

I am having the same issue, I am basically splitting my work up on the client 
side and calling a method multiple times which sets up a thread for each batch 
but when I make the second call to start a second thread I immediately get the 
error above even though the first thread hasn't even started yet but I am using 
NativeObject.sendMessage to log a message back to the client.

Original comment by wjamma...@gmail.com on 3 Apr 2012 at 11:37

[GoogleCodeExporter]

I keep getting this error in flerry.

Error: Error deserializing received AMF object: 

Original comment by egosum...@gmail.com on 4 Apr 2013 at 7:17