Remote Invocable object is not constructed/initialized correctly

Question

Hi, I got a strange problem.
Basically, a node assignes a range of ids (for example 1-1000) to all nodes including itself via the InvocationService. Upon the receipt of Invocable, all the remote nodes do not have the Invocable information initialized correctly, ONLY the original node starts the InvocationService call get the Invocable initialized correctly. In my program, any node can start the InvocationService, and I tried all the different nodes and they all have the same problem.
I fake the code a little bit and when calling the InvocationService (query()) it always sends to itself. And all Invocable objects (when run() starts) are initialized correctly.
Can someone help provide some insight?
The following is some of code related to the problem.
The node call the InovactionService:query()
SearchInvocable oneRange = new SearchInvocable(CacheHelper.getLocalMember());
for (int j = 0; j < members.length; j++) {
oneRange.setMin(nextMinKey);
nextMaxKey = ((nextMinKey + rangeSize) < maxKey) ? (nextMinKey + rangeSize) : maxKey;
oneRange.setMax(nextMaxKey);
// Inform the member for the assigned key range via
// invocation service
// CHANGING TO targets.add(memebers[0]);
// WORKS FINE! SO STRANGE
targets.add(members[j]);
System.out.println("Range[" + j + "]: " + oneRange);
invokeService.query(oneRange, targets);
targets.clear();
nextMinKey = ((nextMaxKey + 1) < maxKey) ? (nextMaxKey + 1) : maxKey;
The Invocable object
public class SearchInvocable extends KeyRange implements Invocable {
SearchInvocable(Member sourceMember) {
super();
this.sourceMember = sourceMember;
public void run() {
System.out.println("SearchInvocable::run(): " + this);
Here is the output for remote nodes print out the Invocable (the Invocable is not initialized correctly).
SearchInvocable::run(): type:null min:0 max:0
Here is the output for local node print out the Invocable
SearchInvocable::run(): type:Accountl min:10001 max:99996
Thanks,
Jasper

Answer 1

Hi Robert,
That's it. It is the KeyRange not implements the Serializable. I missed it. I thought for the local node it goes through the same serialization as the remote nodes do so I overlook the problem. This shows Coherence does the optimization for local node without going through the serialization. Excellent!
Regards,
Jasper