[GLASSFISH-17310] Remote session bean call with entity - data problem/corba stream corruption when using IP address Created: 16/Sep/11 Updated: 25/Nov/11
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
When a session bean is called remotely and either its parameters or return value contain an entity bean there is a data transmission problem that seems to be caused by corba stream corruption when the InitialContext was created using an IP address.
The problem manifests as follows:
The problem can be reproduced in two ways:
Simple standalone client example that demonstrates the problem:
Let me know if there is any more information that I can provide. This is a critical issue for us.
|Comment by Cheng Fang [ 16/Sep/11 ]|
assign to orb for initial evaluation.
Are these entities serializable, or employ any custom serialization?
|Comment by sarnoth [ 16/Sep/11 ]|
The entities implement Serializable and have a serialVersionUID. There is no custom serialization and all the column types are simple (int, String, Long). Below is a test entity that I used to reproduce the problem.
|Comment by Cheng Fang [ 18/Nov/11 ]|
so the key points here are IPv4 IP address and the de-serialization of entity objects. Have you tried configuring or disabling eclipselink weaving? Not sure if that's related, just some wild guess.
|Comment by sarnoth [ 21/Nov/11 ]|
I tried disabling weaving and that did work around the problem.
|Comment by thomas.giger [ 25/Nov/11 ]|
We see exactly the same problem (except for the fact that the hostname does not work either)