A very very strange issue on BlazeDS Deserializing

Question

Hi all,
I run into a very very strange issue on BlazeDS Deserializing. Is there any hint or idea?  Thanks a lot!
Scenario 1:
Both the browser(firefox or IE) and the midtier (BlazeDS ,java) are on the same machine.
Actual result:
Everything works fine.  All the properties in the Flex Object could be mapped to the Java Class
Scenario 2:
The browser(firefox or IE) and the midtier (BlazeDS ,java) are on the different machine.
Actual result:
Sometimes it works fine.
And most of the time it does not work fine. Only the data in List is mapped correctly. All the values of simple data type such as int are mapped to 0 .
Let me simplify the problem.
The objects of Class B is always stored in the ArrayCollection  assocItems of Class A
Flex side:
public class A {
public var id: int;
public var  name: String;
public var assocItems: ArrayCollection=new ArrayCollection();
public class B {
public var id: int;
public var  assocItems : ArrayCollection=new ArrayCollection();
The id , name in Flex Class A and assocItems in Class B could be  deserialize to correct value .  But the id of Class B is always mapped to 0. This is not correct.
The log level of BlazeDS is configured to Debug. From the log I can see that  each value is passed from Flex side to Java server side correctly.
[BlazeDS][INFO] Channel endpoint my-amf received request.
[BlazeDS][DEBUG] Deserializing AMF/HTTP request
Version: 3
(Message #0 targetURI=null, responseURI=/18)
(Array #0)
[0] = (Typed Object #0 'flex.messaging.messages.RemotingMessage')
However, the Java object does not get the correct value of B.id.
In conclusion,
1. It’s an issue with only default types
2. It does not occur every time
3. It does not occur when the browser(firefox or IE) and the midtier (BlazeDS ,java) are on the same machine
Have you ever run into the similar problems? And what’s your solution?

Answer 1

I checked, when I hard-code the constant in linq, the generated sql is like this:
SELECT "Extent1"."AA" AS "AA"
FROM (SELECT "TBL"."AA" AS "AA"
FROM "USERNAME"."TBL" "TBL") "Extent1"
WHERE ('1062303212007000121' = "Extent1"."AA")
if I pass a variable to the query with same value, the sql is like this:
SELECT "Extent1"."AA" AS "AA"
FROM (SELECT "TBL"."AA" AS "AA"
FROM "USERNAME"."TBL" "TBL") "Extent1"
WHERE ("Extent1"."AA" = '1062303212007000121' /* @p__linq__0 */) (@p__linq__0 is passed as parameter)
The only difference is a paramter. I can't figure out why there is such a impact on performance.